I think you're letting your imagination run away. There's a time and place for that, but I think the Hacker News analogy is inappropriate here.
I think you're missing on the big value of Hacker News: It's excellent moderators and community. This can only happen because it is centralized.
Hacker News already has an API. You can write a clone of Hacker News that is API compatible, open source it, and put a big "host on xxx" button on your GitHub repo; but you won't have the community, and you won't have the awesome moderation from Deng.
Even when we look at successful decentralized products like BitTorrent, they tend to build on tiny centralized parts: The Pirate Bay, where the trackers are. The fact that BitTorrent handwaves around some seed nodes...
Getting back to "letting your imagine run away." I think you need to drop the Hacker News analogy and describe what you're trying to build in non-technical terms: Who is it for, what does it do, why does it do it, where do people use it, and why do they use it?
Otherwise, without starting with some kind of use cases, you're just describing typical design patterns and features of a backend that would apply to any social network or blogging platform.
This reads like ChatGPT, unfortunately. 80% of what is described is a stock web app, and the decentralised part is mostly hand-waving with no clear explanation of what the boundaries are between a API and courier server. Any existing ActivityPub implementation already matches whatever is described.
[+] [-] gwbas1c|2 years ago|reply
I think you're missing on the big value of Hacker News: It's excellent moderators and community. This can only happen because it is centralized.
Hacker News already has an API. You can write a clone of Hacker News that is API compatible, open source it, and put a big "host on xxx" button on your GitHub repo; but you won't have the community, and you won't have the awesome moderation from Deng.
Even when we look at successful decentralized products like BitTorrent, they tend to build on tiny centralized parts: The Pirate Bay, where the trackers are. The fact that BitTorrent handwaves around some seed nodes...
Getting back to "letting your imagine run away." I think you need to drop the Hacker News analogy and describe what you're trying to build in non-technical terms: Who is it for, what does it do, why does it do it, where do people use it, and why do they use it?
Otherwise, without starting with some kind of use cases, you're just describing typical design patterns and features of a backend that would apply to any social network or blogging platform.
[+] [-] infotainment|2 years ago|reply
[+] [-] Enindu|2 years ago|reply
[+] [-] Black616Angel|2 years ago|reply
[+] [-] kolinko|2 years ago|reply
[+] [-] captn3m0|2 years ago|reply
[+] [-] quadhome|2 years ago|reply
[+] [-] Doubtme|2 years ago|reply
[deleted]