Post #3241142
2023-03-18 22:48 UTC
Replies (3)
-
@j3j5@hachyderm.io 2023-03-18 22:57
@mike@flipboard.social @davew@mastodon.social Ironically (in my mind anyway) this is solved by not using the official site for your instance and using a client (web or mobile). The more I think about it the more I'm convinced that the future is a headless mastodon (or whatever fediverse sw you want to use) and a client that handles all of this for you.
-
@davew@mastodon.social 2023-03-19 14:47
@mike@flipboard.social we already have a really good federated identity system. https://en.wikipedia.org/wiki/Domain_Name_System why shouldn't we build on that, every user with their own identity provided by DNS. i asked the folks at Tucows to do this a few years ago. i wanted to use DNS for documents. they would have started a business selling sub-domains. and there's no reason every new experiment requires an identity system. and it should also come with storage, that the user pays for.
-
@kidehen@mastodon.social 2023-03-19 16:24
@davew@mastodon.social @mike@flipboard.social, There’s a vulnerability in plain sight right now, based on @Mastodon@mastodon.social not supporting the Client-Server aspect of #ActivityPub. Net is effect: Clients are Mastodon-specific rather than ActivityPub based (what the #Fediverse is supposed to be about). As you know, this is how the beginning of the end starts, since there’s no longterm protection from open standard compliance.