Mama told me not to come.

She said, that ain’t the way to have fun.

  • 6 Posts
  • 6.61K Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle



  • Exactly, and this is my main complaint about Lemmy and Mastodon, they’ve prioritized resiliency of the network but not resiliency of user data. If an instance goes down, all communities hosted there are frozen in time, so I’m not getting updates from other community members from different instances. The platform is decentralized, but the data isn’t.

    Plebbit looks to be similar, but at the community level instead of an entire instance. I don’t know what happens if a community owner disappears, but I imagine it’s similar to Lemmy.

    They day they’re not using DHT

    I thought they’re using IPFS, which I believe uses a DHT under the hood.

    I’m working on my own P2P reddit alternative, and I’m using a DHT. If they’re using something else, that’s potentially concerning. I haven’t looked into Plebbit a ton though, I’ve just seen it mentioned a few times, but then I’m a bit of an outlier since I’m playing in the same space.








  • Competition naturally degrades over time as companies go out of business and consolidate.

    And it naturally improves over time as companies challenge established players and “distupt” the market. As long as the barrier to entry remains sufficiently low, there’s no reason for a net degradation in competition.

    Large companies tend to become less efficient. Yes, they have economies of scale, but they tend to scare away innovators, so they switch to lobbying to maintain their edge.

    The correct approach IMO is to counter the lobbying efforts of large orgs, and that means stripping governments of a lot of their power. Regulations tend to result in more monopolies, requiring antitrust to fix, and as you noted, that’s extremely rare.

    Do you think a more direct “medical patient union” would work? Skipping a government intermediary?

    Yeah, that can work. I’m thinking of having your primary care orovider offer your “insurance” policy, and they’d be on the hook to fund any procedures you need. So they have an incentive to keep you healthy, and that agreement could be a legal obligation that the doctor is doing their best to keep you healthy.

    I do think we should socialize emergency services though. If a paramedic determines you need an ambulance ride, that should be free.

    I’d prefer socialized healthcare over single payer

    I prefer privatized care with transparency in pricing across the board, shortened patent durations, and some government assistance for the poor. But failing that, socialized care is probably the next best. Anything in the middle just breeds corruption.


  • There’s no real / true decentralization

    That’s not exactly true.

    That said, you do need some form of centralized service to connect peers, but you can federate those. It’s only job would be to connect peers, and a STUN server w/ TURN fallback is usually the approach here. These instances don’t need to store any data long term, they just need to connect peers, and the client is free to choose any instance they want, or host their own.

    That’s how Tor works (entry nodes), and most decentralized systems use a similar system.

    One of the best parts here is that offline often just works, and you can sneakernet around firewalls (e.g. if you visit China or something), and all you need to do is connect to a local relay to find local peers.

    Blockchain

    My understanding is it’s only used for name resolution, so the number of data points here should be in the thousands, not millions or billions, so the resource usage should be minimal.

    Basically, the blockchain is functioning as DNS here.


  • Lemmy is not decentralized; it’s federated. “Decentralized” and “federated” are not synonyms,

    This isn’t quite accurate. Lemmy is decentralized, but it’s not distributed. It’s decentralized because the source of truth for a community isn’t your instance, but your instance caches content for that community locally.

    They’re not synonyms, true, but federated systems are typically (always?) decentralized, and rarely (never?) distributed.

    Plebbit seems to be a weird mix of both. Communities are centrally managed, but the data seems to be distributed, at least upon creation (everything probably makes its way back to the creator for moderation).

    DHTs and distributed ledgers are notoriously difficult to design well, often suffering from syncing lags and block delivery failures

    I haven’t looked into it too closely either, but it seems the blockchain is only used for name resolution (seems to be used for community names), so updates should be fairly infrequent.

    I assume they’re using a DHT for data though, probably a separate one for each community, but maybe not. Those can be updated asynchronously, so if data is cached locally, latency shouldn’t be an issue.


  • I really don’t think that would scale at all. A reasonably popular community could have tons of simultaneous posts, and if everyone needs to sync before posting, that would suck. You could probably avoid the worst of it by having posts use uuids, but you’re going to have IO issues at scale. Also, would you need the full repo cloned? That can get big, and you generally only care about recent posts.

    Also, if you’re doing the UUID thing, you’d have sort everything every time locally. That’s fine if you only have a few thousand posts, but if you get into millions or billions, it’ll get bad, especially if you’re dealing with files.

    Databases solve these problems really well. Even a simple SQLite dB would be much better than a filesystem, like orders of magnitude better.