Post AW1ZVM2pd7hoN6F8O8 by Silv@fosstodon.org
 (DIR) More posts by Silv@fosstodon.org
 (DIR) Post #AW1ZVM2pd7hoN6F8O8 by Silv@fosstodon.org
       2023-05-25T17:29:19Z
       
       1 likes, 0 repeats
       
       1)The fediverse has incredible potential for facilitating person-to-person, person-to-private-group, person-to-public group, and public broadcast communications. ActivityPub allows so much variety in how an `actor` can be used, yet it seems to be rarely utilized by actor types other than users. Group implementations are rudimentary, and some fediverse software are implementing groups/channels outside of activitypub, i.e no wider fediverse integration. This is the direction of walled gardens.
       
 (DIR) Post #AW1ZVNrYrzsY0izA6C by Silv@fosstodon.org
       2023-05-25T17:33:42Z
       
       0 likes, 0 repeats
       
       2)Groups can, should, and (hopefully if I make a working prototype) will be a feature of ActivityPub rather than a creation of separate fediverse software apis.Think about the misskey, pleroma, and mastodon. These are the truck codebases that many popular fediverse software are forked from. Each of three giants of the fediverse use their own apis to implement features, causing fragmentation and damage interoperability between various fediverse software.
       
 (DIR) Post #AW1ZVPjptgt5pLO1Kq by Silv@fosstodon.org
       2023-05-25T17:38:32Z
       
       0 likes, 0 repeats
       
       3) Heck, even forks of the big three, such as Akkoma and Calckey are implementing their own APIs now.Most fedi software is compatible with the mastodon API, but Mastodon is incompatible with other fedi software's APIs. This is problematic, because Mastodon is still a massive percentage of the fediverse, and their development moves at a snail's pace with highly opinionated decisions and development goals. Users are losing out, and interoperability, a core tenant of ActivityPub, is dying.
       
 (DIR) Post #AW1ZVRiqWLHfyqwG4O by Silv@fosstodon.org
       2023-05-25T17:45:04Z
       
       0 likes, 0 repeats
       
       4)Where possible, features should be implemented in a manner that is able to be made easily compatible with all fediverse software. An example of this would be quote posts, which had an ad hoc adoption across various fediverse software and was eventually implemented into Mastodon itself. It is a fairly simple feature. It works by detecting the link at the bottom of a post and the user's client will replace the link with the content of the linked post, but it worked! A new compatible feature.
       
 (DIR) Post #AW1ZVTYzfwajgsLPzU by Silv@fosstodon.org
       2023-05-25T17:57:51Z
       
       0 likes, 0 repeats
       
       5) Groups need to operate at the ActivityPub level, using interoperable tools that already exist. Groups will devolve into a fractured mess if implemented using custom APIs rather than the known interoperable standard(s).