Post #2315632
2026-04-20 04:07 UTC
Replies (2)
-
@strypey@mastodon.nzoss.nz 2026-04-20 04:13
@benpate@mastodon.social > "Likes", "Boosts", and "Replies" are all separate things that are hard (but perhaps not impossible) to combine into a single unit Wouldn't it just be a matter of having all 3 triggered by one button? What you'd name that button is an intriguing question though ... @deutrino@mstdn.io @bengo@mastodon.social @smallcircles@social.coop @EUCommission@ec.social-network.europa.eu @nlnet@social.nlnet.nl
-
@smallcircles@social.coop 2026-04-20 07:08
@benpate@mastodon.social @deutrino@mstdn.io @bengo@mastodon.social @strypey@mastodon.nzoss.nz @EUCommission@ec.social-network.europa.eu @nlnet@social.nlnet.nl Link for background: https://coding.social/blog/grassroots-evolution > We are limited (to a degree) by some design choices made in ActivityPub I mention not addressing "Misconceptions" early as most costly mistake of AP ecosystem development. Your sentence above will be interpreted differently by different people based on their Perspective what fediverse means to them. W3C ActivityPub spec is powerful, based on granular message exchange between addressable actors on the social graph. "Likes", "Boosts", "Replies" are underspecified, mechanisms are fedi-specific, follow interpretation of AP that has become common on fedi. A big misconception imho is that its unclear what is 'core protocol' and what is extension with solutions on top of it. Like a "Microblogging" application domain, or "Software development" business domain. A Like is but an ActivityStreams social primitive, a building block. The other 2 are domain-specific. Leaked abstractions, now.