Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
This is similar to Jami. Jami has http name servers for lookup, and (optional) http DHT proxy servers for NAT traversal. Beyond that, it's peer-to-peer DHT. The DHT isn't global, it's shared between connected clients. DHT are also key-value stores, and Jami's issues are not with the name server, they're with message synchronization between clients.
Actually, I have to qualify that I don't know what causes Jami's delivery issues, but it's probably not the name servers or proxies, because you can (and I have) hit them directly with a web browser or curl. From what I can tell, the Jami developers don't acknowledge issues or are incapable of or unwilling to track them down, but the point is that it's very likely the P2P part that is giving them trouble.
P2P is Ia hard problem to solve when the peers come and go online; peers may not be online at the same times and there's no central mailbox to query for missed Messages; peers are mobile devices that change IPs frequently; or peers are behind a NAT.
You may be right about the design; I scanned the design summary, and easily could have misunderstood it. I don't think it affects the difficulty of building robust, reliable P2P applications.
A global DHT unfortuantely is extremely resource intensive, and part of our design requirements is full p2p capabilities for both mobile and web browsers. This cannot be achieve with a DHT, although if a DHT design emerges with support for both, we will consider using it.
Next update for plebbit-js will have full p2p capabilities including gossipsub using libp2p/helia in browser/mobile! We're excited to ship that.