• 1 Post
  • 302 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle




  • We need federated identity or else ux will continue to lag

    What I am saying is that the ActivityPub protocol is inherently built towards a server-centric system, where identities are owned by the server. Go read the spec: even the “Client-to-Server” specification assumes that the server owns the keys and dictates that the client (i.e, users) must do everything through the API provided by the server (i.e, the client’s outbox).

    Anything that is built with a design where the client owns the keys may even be able to interoperate with ActivityPub, but is not ActivityPub.

    Activity Pods is cool bit not implemented on mastodon.

    It’s the other way around. We shouldn’t be looking for “Mastodon on ActivityPods”, but “ActivityPods applications that can talk with Mastodon servers”, and those do exist.



  • And they are either in for one of the following:

    • a $30 Million lesson where they learn that they will have to reinvent ActivityPub in order to be “properly” decentralized
    • a rug pull where they come up with a second relay like Bluesky but fork to give exclusive access for large institutions and the enterprise.





  • rglullis@communick.newstoFediverse@lemmy.worldM stands for money
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    7 days ago

    It’s not interesting. It’s anecdotal at best and a bad coping strategy at worst.

    Instead of calling sour grapes, just face reality: this ecosystem is doomed to failure and stunted growth unless people start showing up with real cash to support it.

    We can not have both ways. If we hate VCs and we don’t want ad-infested, Surveillance Capitalism, we must ourselves pay what developers are worth. Otherwise they will just be playing around here, but collecting their nice paychecks from Big Tech.




  • Ok, final message because I’m tired of this:

    • you are openly admitting that you are going to piss on the well by adding a bot that pretends to be a human.
    • you are openly admitting that you are going to do this without providing any form of mitigation.
    • you are going to do this while pushing data to the whole network. No prior testing in a test instance, not even using your own instance for it.
    • you think that is fine to leave the onus of “detecting” the bot to the others.

    You are a complete idiot.