Indeed.

That lives here BTW:

Welcome! Hope you enjoy your stay!

*bats away the weather*

Do you know if this was a regression? Because I'm almost certain there was spam labelling for silent facet tagging in the past.

To compare with another ecosystem:

Most cryptocurrencies have no privacy because their transaction graph is public. Wallet clustering analyses are similar to what For You is doing!

Zcash's privacy arises from the fact that the transaction graph within each Zcash shielded pool is explicitly hidden.

Centralised social networks emulate privacy by gating access to data. The graph is there, but you aren't allowed to access all of it (though data breaches do happen).

Bluesky intentionally defends against gating with its design, in order to be "billionaire-proof", but that has privacy implications.

The mechanism and spring both sit around the nib/inkwell tube. Without that, I imagine you could shrink down the OD, and/or have the spring be in the middle instead of pushing against the edges.

You could also get tighter braille dots by staggering the mechanisms with longer/shorter adjacent stems.

Or what if each dot used the same click-to-toggle mechanism as a ball-point pen: press to raise, press again to flatten? Would be a question of whether the mechanical design can be miniaturised while retaining strength.

Update: the claimed bugfix is refuted!

If you squint, "different apps" in Bluesky is close to "individual islands" in Mastodon from the front. The "without everything" is the key part: the data and app are decoupled here, so "choose your app" can be an easier and more rapid / fluid process than "choose your instance" is in the Fediverse.

*sighs in shielded note trial-decryption and commitment tree updates*

PSA: foo+bar@example.com is always an alias for foo@example.com but usually treated as a distinct email address by websites.

Bean there, done that

Huh okay, I thought the extra logic (like injecting posts from other feeds) was applied on top of a base Following feed.

For clarity, your Content Languages setting apply client-side to every feed that you view with your client. The BlueSky-provided defaults (Following, Discover) are themselves feeds, and are filtered the same way. So if you are viewing posts at all in the client, you are using feeds.

I tested your feed locally and it works exactly as documented in the client's language settings. I can see this post in your feed if I either have Spanish included in my selection, or nothing selected. (So with both English and Spanish selected, I see everything.)

No one expects the Spanish Inquisition

Or "hat tip" in the UK

Guess which dev board I was referring to