My technical know-how falls short by a long way and I'm having a little trouble figuring out whether I get what I want from the Fediverse. By my limited understanding AT Protocol allows for a 'nomadic' id/datastore (PDS) but with ActivityPub, the nearest we get to that is by having your own instance of an app of your choice and plugging it in/out of other peoples, but your data can only really live in *your instance of *that app??
#Fediverse #atproto #ActivityPub #Data #Identity #PotteringAbout
This entry was edited (19 hours ago)
abeorch
in reply to Gary • •From what i understand ( and Im no expert) the theory of #ap is good, the practicality of it in the real world is hightly centralised. #activitypub is not perfect but self hosting a server for you, your family and friends is relatively simple. If you ever feel the need to change friends/family - yournactivitypub server will be the least of your issues.
Id like to see a #activitypub server (amd other self hosted apps running on most home internet connections in my lifetime.
like this
🫧 socialcoding.., @reiver ⊼ (Charles) :batman: and Gary like this.
🫧 socialcoding.. reshared this.
🫧 socialcoding..
in reply to abeorch • • •There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..
The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.
social.coop/@smallcircles/1163…
PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..
social.coop/@smallcircles/1164…
Together we can
#BoostFediForwards and #cocreate a better #future.
#SX #SocialCoding #SocialWeb
🫧 socialcoding..
2026-04-10 07:10:32
🫧 socialcoding.. reshared this.
abeorch
in reply to 🫧 socialcoding.. • •Standards are impprtant but also efforts to make tools that regular people can use. An example is the difference between #openrt and #yunohost - both great projects but for non technical people openwrt is difficult to engage with but amazingly powerful while yunohost focuses on usability while.accpeting some fundamental limitations.
Id love to see something that brings the two together (or perhaps.something modular that work together) to deliver a guided setup of router and selfhosted opensource apps for a non technical user.
🫧 socialcoding.. likes this.
🫧 socialcoding.. reshared this.
🫧 socialcoding..
in reply to abeorch • • •@abeorch
Totally. I am myself as technical person stuck in Yunohost because of all kinds of upgrade issues. The "bring together" on a holistic basis is exactly what I do applied research on with Social experience design i.e. #SX.
In the case of #FOSS that means transitioning (or rather evolving) towards #SOSS. And considering the entire #FSDL, which either stands for #FreeSoftware development lifecycle. Or for #Fediverse solution delivery lifecycle.
Under SX software development involves service development, delivery, and exchange. Within commons based ecosystems and across them, to the broader public.
In SOSS + FSDL it is natural that you try to attract a #UX designer if you need one and not just sighed "If only a UX designer became a contributor", which I've often seen people do.
coding.social/blog/reimagine-s…
How We Reimagine the Social Web
Social coding commons🫧 socialcoding.. reshared this.