smallcircles (@smallcircles@social.coop)
@tiotasram interesting ideation topic.
Not sure if I have time to respond today, but just wanted to note that this aligns with the general interest and focus of Social experiences (SX) at https://coding.social which I elaborate on as a hobby, and perhaps one day my job.
The disadvantage of microblogging is how ephemeral it is, but the advantage is reach. Should you be interested you are welcome to share results on the social coding forum, which serves as a note-taking tool: https://discuss.coding.social
Also there's the fediverse-ideas repository on codeberg at: https://codeberg.org/fediverse/fediverse-ideas/issues
#SX #SocialCoding #SocialWeb #ActivityPub
Show Original Post
Floppy (@Floppy@mastodon.me.uk)
MWOOHAHAHAHA comments are federating into @manyfold, amazing!
Thanks @amcewen for being unwittingly first in đ
Show Original Post
tiotasram (@tiotasram@kolektiva.social)
In the interests of starting a more productive dialogue than yesterday's main character was interested in, let's make a #brainstorm thread about design changes to ActivityPub and/or client UI that could actually help address drive-by (often racist) harassment on the fediverse.
Feel free to discuss pros/cons but don't feel an idea needs to be perfect to suggest it. Also since this is a brainstorm don't worry about complexity/implementation cost. If you have a great-but-hard-to-implement idea someone else may think of a way to simplify it.
Note that the underlying problem *is* a social one, do there won't be a technological fix! But tech changes can make social remedies easier/harder.
I've got some to start:
1. Have a "protected mode" that users can voluntarily turn on. Some servers might turn it on by default. In protected mode, users whose accounts are less than D days old and/or who have fewer than F followers can't reply to or DM you. F and D could have different values for same-sever vs. different-server accounts, and could be customized by each user. Obviously a dedicated harasser can get around this, but it ups the activation energy for block evasion and pile-ons a bit. Would be interesting to review moderation records to estimate how helpful this might or might not be. Could also have a setting to require "follows-from-my-server" although that might be too limiting on private servers. Restriction would be turned off for people you mention within that thread and could be set to unlimit anyone you've ever mentioned. Would this lock new users out of engagement entirely? If everyone had it on via a default, you'd have you post your own stuff until someone followed you (assuming F=1). One could add "R non-moderated replies" and/or "F favorites" options to soften things; those experiencing more harassment could set higher limits. When muting/blocking/reporting someone who replied to your post, protected mode could be suggested with settings that would have filtered the post you're reporting.
2. Enable some form of public moderation info to be displayed when both moderator and local server opt-in. Obviously each server would be able to ignore federated public tags. I'm imagining "banned from X server for R reason (optional link to evidence)" appearing on someone's profile & an icon on their PFP in each post viewed by someone on server Y *if* the mods of server X decide it's appropriate *and* server Y opts in to displaying such tags from server X specifically. Alliances of servers with similar moderation preferences could then have moderation action on one server result in clear warning propagation to others without the other mods needing to decide whether to also take action immediately. In some cases different moderation preferences would mean you wouldn't take action yourself but would keep the notice up for your users to consider. Obviously the "Scarlet Letter" vibe ain't great, but in some cases it's deserved, and when there's disagreement between servers about that, mods on server Y could either disable a specific tag or disable federation of mod tags from that server in general. Even better shared moderation tools are of course possible.
3. Different people/groups have different norms around boosting. Currently we only have a locked/public binary. Without any big protocol changes, adding a "prefers boosts/doesn't" setting which would warn in the UI before a viewer chooses to boost if the preference is "doesn't" could help. This could be set per-post, but could also have defaults and could have different values for same-server or not, or for particular servers. For example, I could say "default to prefer boosts from users on my server but not from users on other servers" or "default to prefer boosting on all servers except mastodon.social." Last option might be harder to implement I guess.
#ActivityPub #Meta #Harassment
Show Original Post
ElenaMusk (@ElenaMusk@tuiter.rocks)
En TuiterRocks tenemos relay pĂșblico para instancias pequeñas y medianas del Fediverso que quieran ampliar su federado y descubrir mĂĄs contenido. Lo compartimos con @descentraliza para darle mĂĄs visibilidad.
Si administras una instancia y te apetece probarlo, aquĂ estĂĄ:
No prometemos magia, pero sĂ otra puerta abierta al caos organizado del Fedi 
â ïž La aprobaciĂłn es manual â avisad cuando lo añadĂĄis.
#Fediverso #Mastodon #ActivityPub #Relay #TuiterRocks
Show Original Post
reeeen (@reeeen@norden.social)
Kleiner Reminder fĂŒr Algorithmus-MĂŒde: Im Fediverse entscheidest du, wem du folgst â nicht irgendein undurchsichtiger Engagement-Optimierer. Deine Timeline gehört dir. Klingt banal, ist aber eigentlich ziemlich revolutionĂ€r. đâš
#Fediverse #Mastodon #Dezentralisierung #SocialMedia #ActivityPub
Show Original Post
objects (@objects@social.retroedge.tech)
Are they leaving the #fediverse completely? Or just using other #ActivityPub servers?
I was on a #mastodon instance for a while, hosted by a tech Youtuber. When that instance shut down, I moved to another independently hosted mastodon instance, then decided to self-host a Pleroma (alternative to mastodon) server and have been on that ever since (a couple years).
#selfhost
Show Original Post
omi_geek (@omi_geek@mstdn.jp)
Iâm building a new website partly as a photography project, and Iâm planning to install the #activitypub plugin so it can integrate with Fedivers
Show Original Post
dnkrupinski (@dnkrupinski@hannover.town)
Wenn 2026 #Barrierefreiheit nicht zum persönlichen Wissensschatz zÀhlen sollte, sollte man dringend seinen persönlichen Wissenshorizont erweitern.
Jeder Person, die ein auf #ActivityPub basierendes System nutzt, steht es frei, andere Personen stumm zu schalten oder zu blockieren.
Auch dir ein langes und erfĂŒlltes Leben! đ
Show Original Post
user (@user@nokoto.org)
Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?
The last time I checked, Lemmy, GoToSocial, Friendica, and the âkeys to name a few did not handle it. Mastodon didnât if you included requiring ed25519. But I havenât checked the code bases or my logs in a month or two, @julian. At that time there wasnât much progress on peertube/http-signatures or superseriousbusiness/httpsig.
I should probably check again...
Show Original Post
julian (@julian@fietkau.social)
RE: https://mastodon.social/@bagder/116359048796181736
Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.
On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify, or at least scripts/aliases.
Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?
#ActivityPub #FediDev #RFC9421
Show Original Post
brasiliana (@brasiliana@social.museus.gov.br)
"Many governmental organizations and politicians to this day seem to prefer #BigTech platforms (X, Facebook, Instagram) and Bluesky for their communications.
In this essay I will explain why I believe #Mastodon / #theFediverse are a far superior fit for public institutions, essential services and politicians; I see three key advantages for this open network based on the #ActivityPub protocol: #openness, #agency and #reach."
@_elena
https://blog.elenarossini.com/openness-transparency-and-reach-three-reasons-why-public-institutions-should-embrace-the-fediverse/
Show Original Post
post (@post@lemmy.ml)
Fediverse & Social Web track at COSCUP 2026: call for participation
https://lemmy.ml/post/45555239
Show Original Post