@mayel (You can tell me to, like, look into it myself rather than asking you to explain every detail and stuff. I'm not in a situation where me having that info is relevant to my safety or supporting anyone where it is relevant to theirs. I'm just asking hopefully-useful questions, so while I like learning about how this works from this angle and am enjoying it, if my repeatedly-asking-details is not particularly enjoyable/useful to you/the project, like.)
(I'm not getting thst impression from you, but just in case/to be explicit about my conversational position rather than try to rely on tonal nuances.)

@mayel (After a certain level of depth to this conversation I hit the wall of being a Fake Geek Girl™ who hasn't actually read @sarahjamielewis 's Queer Privacy or more than a chapter or two of @sarahjeong 's Internet Of Garbage or looked deeply into the work and critiques that @evacide has done over the years or ... .)

@mayel Oh wow! I didn't even look at the specifics yet (another reason this was dashed-off and non-specific), that's great that you've already been thinking along those same lines!

The actual specific thing with Bonfire set me off on this line of thinking was:

"""
E.g. you can share a post with several circles but only allow replies from a specific circle, or make a post public but invisible to specific people.
"""

"Make this invisible to X, Y, Z" strikes me as something that can requires very nuanced and situation specific careful stepping around disclosure/visibility and trust. (Ranging from "none", e.g. planning a birthday party, to much higher stakes.)

A bit of a longer post to hopefully come (but I AM bad at Task, and currently behind on many things) but I think there's a widespread antipattern in UI presentation of calling a functionality (especially safety functionality) what the user WANTS rather than what it DOES.

I think this is especially... not "dangerous" exactly, but more impactful -- in federated/distributed networks, where there isn't a Single Platform/Owner able to play god with the single database (and with a stronger ability to pretend to play god with every user's endpoint).

Iike, "Delete Message", e.g. I think should be called "REQUEST Delete" -- it relies fundamentally on a basic minimal level of politeness from instances (federated) or individual endpoints (E2E chat).
A lot of these are "request"s, but it gets more obviously complicated when you add it in explicitly.
Like, "block user" -> "request block user".
Who are we Requesting things of? That is, who are we trusting? And who hears of this request?

Ma quanto è bello l'Ex Asilo Filangieri a Napoli? Sono innamorato.

Alle 7 facciamo un talk e dopo cena festa (suono anch'io!).

Am I the only one out of the loop on what @Bonfire is? Am I correct on that it's a collection of software (some of it in Elixir?) to do different federated things? Bonfire Social seems to be a Mastodon alternative? https://bonfirenetworks.org talks in very lofty terms about a network but a network of what? There seems to be a website builder (Mosaic) that also has some ActivityPub support?

#Bonfire

@tchambers@strypey

Indeed, we have FEPs that either directly address the UX issues mentioned in your post, or could be parts of final solutions:

The Sin of Overwhelming Complexity: Instance Selection Paralysis

- https://codeberg.org/fediverse/fep/src/branch/main/fep/61cf/fep-61cf.md
- https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md

The Sin of Remote Interaction Purgatory: Federation Gymnastics

- https://codeberg.org/fediverse/fep/src/branch/main/fep/07d7/fep-07d7.md (withdrawn; https://fedilinks.org is a similar proposal)
- https://codeberg.org/fediverse/fep/src/branch/main/fep/3b86/fep-3b86.md

The Sin of DM Disasters Waiting to Happen

Some FEPs talk about limited visibility posts and private groups:

- https://codeberg.org/fediverse/fep/src/branch/main/fep/171b/fep-171b.md
- https://codeberg.org/fediverse/fep/src/branch/main/fep/db0e/fep-db0e.md

The Sin of Ghost Conversations and Phantom Follower Counts

Synced conversations:

- https://codeberg.org/fediverse/fep/src/branch/main/fep/1b12/fep-1b12.md
- https://codeberg.org/fediverse/fep/src/branch/main/fep/171b/fep-171b.md
- https://codeberg.org/fediverse/fep/src/branch/main/fep/76ea/fep-76ea.md
- https://codeberg.org/fediverse/fep/src/branch/main/fep/f228/fep-f228.md

The Sin of Invisible Discovery: The Content Mirage
The Sin of User Discovery Hell

I think ActivityPub relays could be used to solve those problems:

- https://codeberg.org/fediverse/fep/src/branch/main/fep/ae0c/fep-ae0c.md

Has anybody built a UI for browsing longform writing over #ActivityPub?

@mayel
Your Markdown post came through really well. Is there a switch to choose between publishing all of a post, or just the headline or an excerpt?
@Bonfire

@mayel@Bonfire Hey, the content of your post is null.

Looking for some fedi account to include in a list focused on #fitness and #health, any suggestion ?

cc @dajb@social.coop