Paul Rohr
@pevohr.bsky.social
550 followers 560 following 2K posts
Dad, startup guy. Ideas matter. Design matters. It's about we, not me. hachyderm.io/@pevohr
Posts Media Videos Starter Packs
pevohr.bsky.social
Nice simplification!

What's the use case where the final toggle is needed as an explicit option?

Wouldn't it be even simpler to just omit that + always default the other settings to whatever you used the previous time? (It's an easily learnable behavior)
pevohr.bsky.social
Papal infallibility is only an article of faith within a single religious tradition

You can fervently believe in the importance of Constitutional law without having to treat SCOTUS with undue reverence. If something's gone terribly awry there, then we find proportionate ways to fix it
pevohr.bsky.social
On legitimacy:

"That to secure these rights, Governments are instituted among Men, deriving their just powers from the consent of the governed"

Nobody's claiming the entire federal judiciary is illegitimate. Just this particular collection of 9 fallible robed humans
Reposted by Paul Rohr
gracekind.net
You can slice a cube in half and get a hexagon ??
pevohr.bsky.social
How do you envision this mechanism working if downstream labelers aren't just emitting a noisy subset (or superset) of upstream label records under a new namespace?

Does adding DAGs somehow become a clever namespace aliasing hack which makes partial join results more cacheable within AppViews?
pevohr.bsky.social
Effectively, the AppView winds up locally doing a logical JOIN across its copy of three kinds of data:

- raw content records
- matching label records
- user moderation config records

... with the last category acting as a namespace filter to only include records from specific labelers
pevohr.bsky.social
IIRC, in the current architecture, labeler processes independently emit label records for specific pieces of content

A copy of that dataflow from each labeler, aggregated via relays, is then used by AppViews when hydrating subsequent requests for content
pevohr.bsky.social
Interesting idea

Any clues where/how that might reduce workloads within the system? Would the DAGs be:

- directly expressing set algebra,
- just emitting exceptions, +/or
- doing something else entirely?
Reposted by Paul Rohr
pevohr.bsky.social
Rudy's book publishing metaphor really pays off here, because previously only protocol weenies understood the tradeoffs required for @whey.party's workaround app to function

( Read the whole 🧵 for an outstanding example of taking the time to communicate calmly about complex technical solutions )
rude1.blacksky.team
As you can see in this screenshot, not only are AJ Link's post and profile still available elsewhere, he is still posting (though seemingly less happily) freedom of speech unimpeded
This app Red Dwarf by @whey.party skips the bookstore and goes straight to the author. blacksky.community doesn't 5/11
avatar
Festive Łink. 🎅🏿 🎄 🎁 @spacelawshitpost.me
· 19h
A lot of people talking big shit now because they think I won’t see. Fucking cowards. Bootlicking losers.
0
0
1
avatar
Festive Łink. 🎅🏿 🎄 🎁 @spacelawshitpost.me
· 19h
It’s so weird being able to see people have whole discourses about me without being able to visibly respond. lol
0
0
3
avatar
Festive Łink. 🎅🏿 🎄 🎁 @spacelawshitpost.me
· 1d
Hi @jazzpomegranate.blacksky.app. Make everyone change their profile pics to Free Link.
Free Link Black Panther button like Free Huey.
1
0
1
Reposted by Paul Rohr
miniver.bsky.social
A society which rewards boldness reïnforces privilege
Reposted by Paul Rohr
chaosgreml.in
Do what @rude1.blacksky.team and @blackskyweb.xyz are doing. Do what @bad-example.com is doing. Do what @essentialrandom.bsky.social is doing. Do what @prosocialdesign.bsky.social is doing! Build new societal and communal structures that promote equity and participation and sustainable engagement.
Reposted by Paul Rohr
chaosgreml.in
Been thinking a lot about the #waffles discourse and how it’s frustrated me in a lot of different directions.

One of the main reasons, I think, is that it remains so individualist. Too many of you are blaming individuals instead of the structural forces that reify oppression & abuse on all sides.
Reposted by Paul Rohr
pevohr.bsky.social
Thus, I'm really looking forward to deep thoughts from @bnewbold.net, @rahaeli.bsky.social, et al on account-level moderation in the atproto ecosystem

Specifically ways that communities might be able to scalably access these kinds of tools to proactively improve their collective experience
pevohr.bsky.social
Even if upcoming features like "zen mode" (whatever that is) can do a better job of separating folks before they devolve into angrily chasing each other off ...

... they're unlikely to be as proactively effective as the community-wide shunning that some are so urgently seeking
pevohr.bsky.social
The bsky team has successfully delivered conflict-reduction features like:

- the apocablock
- quote detachment
- hide reply for all

... each of which helps individuals curate their own experience + reduce the blast radius for others -- but only after the fact
pevohr.bsky.social
What's still needed is an equally thoughtful discussion about how, why, + where *accounts* can/should be moderated

Those mod actions are far more socially contentious + norms vary widely between communities, but the net effect is to proactively ban an entire account based on prior offenses
pevohr.bsky.social
Lots of useful distinctions + vocabulary here. However, they're most relevant for understanding where + how interventions can or should be done to moderate:

- specific pieces of content
- volumes of spam

whether proactively or in response to reports
bnewbold.net
for atproto devs and protocol watchers, I published an overview of the network moderation architecture.

it tries to cover all the mod actions possible for each service type. this design has been around a while, but not well documented.

this doc is not very polished, but could clarify some details
AT Moderation Architecture | bryan newbold
The AT network is becoming more heterogeneous in practice, with independent PDS hosts, apps, and alternative bsky AppViews establishing themselves. This means that more complex inter-service moderatio...
whtwnd.com
Reposted by Paul Rohr
miniver.bsky.social
The President believes that this situation requires intervention by the 82nd Airborne
Reposted by Paul Rohr
bnewbold.net
a bunch of folks are wondering about how mod comms work for other PDS instances. this is also a problem for, eg, labelers trying to reply to appeals.

the plan is this proposal, which we have been making slow progress towards (it has been a very very busy 12 months for mod eng team)
pevohr.bsky.social
Instead, I'd recommend recoloring the graph slightly so the AppView box on the left is green instead of blue

That'd make it much clearer that the distinctive UX for each app has its own green + orange flows, reusing the generic blue mechanisms shareable by all atproto apps
pevohr.bsky.social
You meant diamond = relay, square = AppView, correct?
pevohr.bsky.social
The only problem is that all the blue boxes on the atproto diagram are labelled as "servers" without differentiating their roles, potentially leading to confusion
pevohr.bsky.social
☝️ This. Reading it as a unidirectional dataflow diagram explains how an atproto app's UX is hydrated from a single user's perspective

Each user's client writes to their own PDS, which forwards writes via a relay to the AppView their client connects to for a full view of the world
pevohr.bsky.social
Kudos to fiatjaf for such a tidy diagram of the dataflow in atproto apps
tree.fail
"Visual depiction of the architecture of 3 different decentralized social networking protocols [Fediverse, Nostr, ATProto]" ⎯ fiatjaf (author of Nostr)

njump.me/naddr1qvzqqq...
Fediverse

First of all we have Mastodon (I often call it by this name because Mastodon is the de facto controller of the protocol), but a better name would be the Fediverse, which is ugly, but still better than ActivityPub, since "Activity" depicts a much broader protocol, conceived by the minds of unreasonable academics, unimplementable in nature, which was only partly adopted by Mastodon.

Anyway, it is very straightforward: clients talk to a single server, that server talks to other servers. Nostr

Well, Nostr has been described elsewhere many other times, but its core new idea is that clients can talk to multiple servers, which gives us a very chaotic ecosystem of signed messages. ATProto

Finally we have Bluesky, or, if we go by the name of the overall protocol, ATProto. Its core new idea is that the basic functions of a social networking server can be broken up in mainly 3 different kinds of servers, which then talk to each other in a pipeline.