There are a bunch of issues around txt records that have come up in discussions for other protocols, main of which being the size of the each txt record itself. Right now the did plc is a cut down hash of the did document.

This means there needs to be a registry from which to get the document itself as well as which providers the identity is using etc.

All that is way too much for a txt record and thus nostr, matrix, and others ended up using well known http endpoints for server or user identity.

Oh right, but the DID document record is separate from the DNS mapping to DID right? If I'm reading

But from there, yeah, a different registry could handle the DID document store

I mean the examples under:

• Example: Hosting service
• Example: Hosting service w/separate domain name
• Example: Self-hosted

Block and Mute are worth being two distinct concepts.

Block is public, Mute should not let the muted know

I did notice in the

I'm a bit confused by this though, since earlier in this thread today, someone said that the DNS lookup is a fallback. But the code doesn't look like it does anything else. Not familiar with the whole code stack or when this code is actually called though

there is little hope you won't make it in before it goes public in general

Not sure what this is based on. Everyone invited gets invites every week, at some point a friend of a friend will get an invite, and soon after that you'll get one too.

alr, let me try to understand this:

are all .

The hosting service: https://alice.com

mmm that's nice

I feel these two are a bit different concepts. to the best I can quickly explain this:
did is just a way to identify a user/service/whatever
oauth2 is a way to request/provide authorization

you can use dids for identity and still use oauth2 for authz

I mean this seems like a moderation problem, rather than a platform problem. We need mods to ban people like 1@10allday:matrix.org and those asking for invites who just turn the room into garbage.

I prefer matrix as a protocol too. If all the people actually involved in bsky leave, this room will truly have little reason to exist :/

I'm an OSS contributor myself to the Helix text editor, and the other day we got a complaint about a user with "Groyper" in their name. And the maintainers just collectively sighed. We just want to work on our text editor, we did not sign up to be chat room moderators.

But I think one of the consequences of success is that it comes with a whole bunch of stuff you never wanted to do. So I get it

So this came up a couple of times over the last few days, and I did a bit more research and learned that

I just

Currently, it is fetched from a central directory: https://plc.directory

There's regular discussions here to replace this "placeholder"

Is the resolution done using WebFinger?

I tried, and it doesn't seem to work:

https://plc.directory/.well-known/webfinger?resource=did:plc:m2jwplpernhxkzbo4ev5ljwj

I get this error:

"Cannot GET /.well-known/webfinger"

Did I do something wrong?

I have been thinking a lot lately about a Human Readable UI name space utilizing DIDs that broad casts through a multicast session in a scatter attempt to connect beyond traditional DNS

https://docs.google.com/presentation/d/1-N-qZs4eEup70ZcGsxPf-SY6BbL0qn-UebWNMuCi5MU/

There are also some interesting concepts around low latency networks utilizing Erasure Coding one being Liquid Data Networking an interesting concept for rural networks that could bind to a mesh network of iot devices

https://youtu.be/DSlL2MuF97E

Well depends on what you mean by "username take downs".
If I control

That said if I am following you the follow is defined by DID and not by handle so when they get the domain name and re-assign @

https://bsky.social/xrpc/com.atproto.sync.getRepo?did=<did>&earliest=<cid>&latest=<cid>

did: did.toString(),
earliest: commit.toString(),
latest: commit.toString(),

when you sync the repo for indexing give is the last commit you pulled so it will give you only the new blocks since then

Because if there isn't - what's the point? Sounds a bit drastic, but instead of relying on twitter or Facebook or whatever, one relies on the

I really hope I'm missing something here

In reply to

Kjartan

Because if there isn't - what's the point? Sounds a bit drastic, but instead of relying on twitter or Facebook or whatever, one relies on the

plc.directory

instead (maybe even with the downside to take care of hosting the pictures).

I really hope I'm missing something here

interesting q! a couple points:

1. none of us here work at bluesky. a few of them are here infrequently, but not often
2. my sense is, it's way too early for them to build those kinds of tools. they've been working hard on basic admin moderation tools and user features like blocking, they're nowhere near corporate brand mgmt stuff

One question, I was reading the blog post on Bluesky and convinced by the idea of account portability using DID.

But if dns becomes an handle of your id, won’t it be no longer ‘portable’ since dns can only be acquired through centralized registrar?

I’m a newbie so I may be asking a stupid question, but please help me :)

Aba, thanks for the info! I wonder eventually it will be on the Bitcoin network, (sth like Microsoft ION?)

Also, if anyone has a remaining invite code, it would be so thankful if you can share me one via DM. Dying to use bluesky😇

Someone "took over" the "

If I understand what he did accurately —

He made the S3 URL:

https://s3.amazonaws.com/xrpc/com.atproto.identity.resolveHandle​

Return:

{"did":"did:plc:imkvi5glxfcpaqcinktnbpwt"}

.