@reiver

The only thing that I would bring in regarding emoji use in display names is #a11y issues if there are a lot of them. I'd say recommended practice should be to have 1 and max. 2 emoji in the name, so #screenreaders don't have read a long shebang you sometimes see on 'funny' display names.

But perhaps someone better versed in #accessibility issues for the visually impaired can chime in on this #ActivityPub #FEP (and perhaps other FEP's too), if this is a real issue. A "fediverse accessibility best-practices" may exist as well (somewhere).

#SX #SocialCoding #AskFedi

@nicol

> if the challenge of knowing what Fediverse Apps implement which bit of the spec is a blocker, is there a standard way to declare which bits of the spec an app is conformant in?

The #ActivityPub #FEP process keeps a list of implementations, in each of its documents. The FEDERATION.md was once introduced as "something to start with before going more complex wrt introspection", a temporary bandaid to bring improvement. Its adoption and use, and later its description as a recommended practice are going very slow though. Still, a very useful practice, compared to lacking such doc and perusing foreign codebases for the info.

> does the Fediverse need a democratic membership org that funds core maintenance of FEP and pays for some of the core community maintainers to keep looking after the ecosystem.

That might be a good solution. For part of a much bigger problem. No #funding bakes bread yet.

I addressed this with @nlnet in the past, and intend to bring it up again next week.

@abeorch @gary

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.

https://social.coop/@smallcircles/116379158584600016

PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..

https://social.coop/@smallcircles/116402592862958767

Together we can  #BoostFediForwards and #cocreate a better #future.

#SX #SocialCoding #SocialWeb

cc @evan relating to earlier #TagsPub discussion we had on the matter.

This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.

Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.

More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.

#NoBots #nobot #fedi22 #NoTagsPub #Botiquette

@aslakr @leanderlindahl

🤔 Off-topic reformulation of the procedure in general terms.. In areas where PeerTube isn't post-facto interop leader itself, it should hope a reasonably broadly adopted #FEP consensus exists, or follow the post-facto leader in that particular application area and accept the upstream dependency to that part of the #ActivityPub specs the leader owns (and hopefully cares for, beyond their own needs, with good design and documentation).

I know there is some ongoing work, eg. https://socialhub.activitypub.rocks/t/fep-07d7-a-custom-url-scheme-and-web-based-protocol-handlers-for-linking-to-activitypub-resources/3588.

Some people will argue against this, but the Atmosphere is (slowly) decentralizing (https://stefanbohacek.online/@stefan/116126040489956521) and it will soon run into the same issues we're dealing with, like being asked to log in when you click a link to a post that's not on your server/AppView/what have you.

I'm sure they will figure this out, with their deep crypto VC money pockets, but if we can figure this out first, it could really give us a major advantage.

#fediverse #mastodon #FediDevs #MastoDevs #FEP #standards