tapping the sign:
bluesky is a public network. do not make posts which can be interpreted as a physical threat against a living political figure. do not fly close to the sun.
just that period reminder that content posted to Bluesky is public to *anybody*. if you don't want to see it used in a court of law, don't post it here.
and DMs here are not E2EE, they can be subpoened. a great use for bsky DMs is to share secure comms and move the conversation there.
if you want to chat about something sensitive, you can use Bluesky DMs to exchange contact info, but I would recommend moving the conversation to Signal.
Bluesky DMs are private, but they are not (yet) E2EE. Signal is hardened, focused, and does privacy/security best.
as a reminder: bluesky (the app) has a broad set of user interactions controls.
beyond blocking and block lists, we have features to control who can reply, mention, and quote-post accounts
I have made decisions, and made mistakes.
those have caused harm to real people, including Black folks, including really great+knowledgeable Black folks who supported Bluesky.
I'm sorry. feel pretty bad about it. it sucks.
re/earning their trust, and everybody else's trust, will be hard.
excited to share that we are following through on our earlier commitments and putting together an independent+neutral organization to house the DID PLC system, includes the directory service
こんにちは日本🇯🇵
投稿(まだプロフィールではない)内の日本語テキストを検索するためにいくつかの変更を加えました。 あなたがどう思うか興味があります!
[この投稿は機械翻訳を使用しました]
have said it before and will say it again:
Bluesky Chat/DMs are not E2EE. don't put anything sensitive in there you wouldn't want rando law enforcement to pore over.
use it to exchange Signal contact info. consider "disappearing messages". do it by habit, get your friends+fam to also.
as control of Twitter has become more openly partisan, now is a great time to encourage municipal and regional govt and civic comms teams to move, or at least provide alternatives!
public transit, parks, libraries, museums, highway, utilities, weather, emergency, schools, etc
wrote up a reply to @dustyweb.bsky.social's "How decentralized is Bluesky really" blog post
really glad @stf.jus.br set up a domain handle!
encourage other government agencies and officials to do the same. both as verification+trust signal, and for autonomy+control.
👩💻 ¡atproto devs! 🧑💻
just in time for the weekend: our protocol roadmap for the first half of 2025.
we got auth scopes, we got merkle tree inversions, we got deprecations, we got balmy spring weather and long walks in the forest. check it out!
devs! want to build something on #atproto but not sure where to start?
check out this "Call for Projects" with a bunch of ideas, ranging from protocol frameworks, to entire apps, to bots
hello new and returning bsky users!
one of the things we have been working on recently is making it easier to build and log in to other apps, clients, and toys. here are a few examples 🧵
"Car Talk" but for servers or web services that have been running for 10+ years
"ah! Django 0.96 pre-magic-removal, Python 2.6. what a great era of computing!"
We got a blog post out summarizing our launch of OAuth for AT Protocol, and what work remains. This has been a huge project led by @matthieu.bsky.team with input from a bunch of standards folks and devs.
Big milestone for building all sorts of clients, apps, and integrations on atproto.
network activity is way up today, presumably driven by ICE shooting Alex Pretti in Minneapolis.
this hasn't been showing up in Bluesky Trending Topics. that is not intentional, and we are still trying to debug why it hasn't.
a couple new hidden search tricks (UI and docs for these forthcoming):
mentions: @handle.example.com
time range: until:2023-06-01 or since:2023-06-01
URLs as just the full URL
URL domains: domain:en.wikipedia.org
language (depends on poster config): lang:ja
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
social media is the last greyhound bus of the night from Las Vegas back to Los Angeles
to sincere post a bit:
the ability to receive important timely updates like this one, from regional govt and institutions like this over an open protocol (vs closed/proprietary platforms) is a huge part of why I work on AT
devs! have a high-level roadmap for OAuth roll-out.
will impact client apps, SDKs, and PDS implementations... open to hearing feedback and concerns from all those folks
#atproto devs and firehose consumers!
we have changes coming soon with our relay service, which will result in a sequence number reset/update.
all that and more inside...
this is a cool project!
in addition to automating offsite repo+blob backups, it has a web UI for registering PLC recovery keys (which you keep in a p/w manager, not remote service), and doing the adversarial PLC recovery process (eg, if your "old" PDS is unavailable)
solid step for own-your-data