• 0 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle



  • As far as I’m aware, there’s nothing preventing a PluralKit equivalent from being made for other platforms. In fact, a quick search turned up a WIP Matrix port on github.

    So no, I don’t think this is true. Lack of PluralKit isn’t what’s preventing people from switching en masse. It’s the opposite—lack of people switching means there’s a lack of demand for a PluralKit port in the first place, so even though there is a port people don’t know it exists and thus it doesn’t get as much dev attention.

    It comes down to network effects, ultimately, and just plain inertia. If you’re already on Discord, and all your friends are on Discord, it’s hard to convince you to switch. And being more familiar with the Discord bot ecosystem (like PluralKit) is just one more thing that adds to the inertia.


  • Like other people have said, this is very similar to how the Internet already works. All you need to do to connect to the Internet is connect to a single router that’s a part of it, at least in theory. The Internet is already decentralized on the backend, it’s just that only big players get to be a part of it for the most part.

    A fundamental problem with your decentralization idea is that on a mesh network, you become reliant on your upstream(s) for your connection. You think Comcast is annoying, or your connection is slow? Imagine trying to troubleshoot your Internet connection and having to go deal with your neighbor instead, but he’s at work so you have to wait for him, but oh he’s too tired so he’ll help you tomorrow…

    Not to mention that this severely limits speeds. No longer can your connection go from your house, to the street, to the backbone, and then straight to Google’s servers, now it has to go bounce around between a number of potentially unreliable consumer connections, run by non-professionals.

    In a system like this, inevitably local organizations or companies will pop up to take the burden off individuals, which would provide massive QoL improvements, and we’d end up with ISPs again.

    That said, there’s a lot of people doing hobby network stuff out there. I know some hackerspaces have their own local hobbynets, that then connect to each other over the open Internet using VPN tunnels. This solves some of the reliability problem, plus it’s just a hobby thing so it isn’t a problem that it’s slow and kinda bad. Then there are even individuals who get their own routers (or VPSes) and plop them in datacenters to participate in the internet alongside big companies and ISPs. Neither of these require new protocols, everything can be done with TCP/IP and BGP. (Plus a splash of VPN protocols here and there.)






  • What incentive would a bank have to release their apps as FOSS?

    You probably could create an open source banking app and use it to run a bank on a primarily open source software stack. But banks are not software companies, and they have no reason to engage with the FOSS world. We could think up lots of potential reasons for why a bank might not want to release their apps as FOSS, but the simplest answer is “why would they?”

    I’d love to live in a world where free software is the norm, but we’re not in that world. So if the bank has no incentive to do it other than the comparatively niche interests of the FOSS community, they just won’t do it.








  • It kind of doesn’t matter, but the moderation policies, local timeline, server uptime/admin skill, blocked instances, and the theoretical longevity of instances can vary widely between instances.

    The plethora of “Baby’s First Selfhost” servers don’t make for good Lemmy instances for example, because they are likely to be mismanaged and there’s a good chance they will disappear unexpectedly once the hype dies down in a couple months.

    Or another example, you have servers that are essentially unmoderated and full of hate speech and illegal content, or heavily moderated servers that ban dissent and defed liberally, and everything in-between.