• 132 Posts
  • 2.14K Comments
Joined 3 年前
cake
Cake day: 2023年6月9日

help-circle


  • No, far from me saying that the clients (apps?) need to look the same. What I am saying is that the differentiation should be happening at the client, not the server.

    It’s the thing with Communick. I wish I didn’t have to offer separate instances for each of the services (Mastodon, Lemmy, Funkwhale) but that every member could get one account which then could use as their main fediverse actor, regardless of “frontend” suited them best. The shell should adapt to the user, instead of the user being forced to adapt to the application.













  • Wouldn’t you agree that hardcoding one specific community to provide a feature to “try it and see it causes any problems” is yolo’ing?

    I’ll code something to spread communities to other instances using an API but that seems like a lot more work.

    In my view, the “proper” solution to this (and that would fit right into ActivityPub) would be simply to let the actor that represents the server to post “as:Create” for any new communities that are created and then let the other software follow these if they are interested.

    It certainly would be a lot more work and it would still require others to write code on their end to look for this information, but seems like the only implementation that would seem like just another ad-hoc hack.




  • It’s funny to see these contrasting approaches between PieFed and Lemmy development.

    Rimu just treats this is a hobby and goes ahead yolo’ing a bunch of these features that abuse the underlying protocol and could bring serious systemic risks if other admins start deploying it, but because the current userbase is small then there is little scrutiny and they all think it’s good to go.

    The Lemmy devs are trying for years to get enough support to make a living of their work and therefore a lot more “professional” about what they do, so they would never introduce a feature that could cause Lemmy to be a “bad participant” in the network. But by not taking a more “customer-focused” approach to product development, it takes a long time to bring any functionality that makes it attractive.

    PieFed is definitely taking a “Worse is Better” approach and I don’t know what to make of it. It seems to be poised to make it most popular software among the current fediverse users, but at the same time it makes so idiosyncratic decisions that it makes it hard to believe it will be usable if more people started joining in.