who’s at #39C3 and also interested in #atproto #didplc related meetups and workshops?
(or knows someone who might be?)
@atproto.science
@eurosky.social
@atprotocol.dev
@tgoerke.bsky.social
@wake.st
@renderg.host
@bmann.ca
@bnewbold.net
(or knows someone who might be?)
@atproto.science
@eurosky.social
@atprotocol.dev
@tgoerke.bsky.social
@wake.st
@renderg.host
@bmann.ca
@bnewbold.net
December 26, 2025 at 3:00 PM
who’s at #39C3 and also interested in #atproto #didplc related meetups and workshops?
(or knows someone who might be?)
@atproto.science
@eurosky.social
@atprotocol.dev
@tgoerke.bsky.social
@wake.st
@renderg.host
@bmann.ca
@bnewbold.net
(or knows someone who might be?)
@atproto.science
@eurosky.social
@atprotocol.dev
@tgoerke.bsky.social
@wake.st
@renderg.host
@bmann.ca
@bnewbold.net
and yeah, didplc becoming the standard would be incredibly funny
December 16, 2025 at 10:16 AM
and yeah, didplc becoming the standard would be incredibly funny
this doesnt feel great either but i guess it works
November 2, 2025 at 11:53 PM
this doesnt feel great either but i guess it works
didplc doesn't use the controller property but maybe it should for people ok with their alts being obviously controlled by a main acct 😅
November 1, 2025 at 6:41 PM
didplc doesn't use the controller property but maybe it should for people ok with their alts being obviously controlled by a main acct 😅
I'm not aware of any production users currently, although it has been tested for go-didplc. Hoping to see some in the future!
October 8, 2025 at 8:03 PM
I'm not aware of any production users currently, although it has been tested for go-didplc. Hoping to see some in the future!
If you work with ATproto in Go, now's a great time to try out this library. It was just tested for use in go-didplc and worked well 😁
September 29, 2025 at 3:31 PM
If you work with ATproto in Go, now's a great time to try out this library. It was just tested for use in go-didplc and worked well 😁
I need somebody smarter than me to explain this.
afaict #atproto is built on this central database thingy "dldplc" that I know they plan to outsource to a non profit. better but still a problem imo cause non profits can be evil (or just plain dumb) too.
so how does #ActivityPub avoid a […]
afaict #atproto is built on this central database thingy "dldplc" that I know they plan to outsource to a non profit. better but still a problem imo cause non profits can be evil (or just plain dumb) too.
so how does #ActivityPub avoid a […]
Original post on liberal.city
liberal.city
September 23, 2025 at 5:03 PM
I need somebody smarter than me to explain this.
afaict #atproto is built on this central database thingy "dldplc" that I know they plan to outsource to a non profit. better but still a problem imo cause non profits can be evil (or just plain dumb) too.
so how does #ActivityPub avoid a […]
afaict #atproto is built on this central database thingy "dldplc" that I know they plan to outsource to a non profit. better but still a problem imo cause non profits can be evil (or just plain dumb) too.
so how does #ActivityPub avoid a […]
this post is brought to you by i fucking broke didplc resolution w my shit lmfao
September 6, 2025 at 8:43 PM
this post is brought to you by i fucking broke didplc resolution w my shit lmfao
how do you migrate from didplc to didweb btw? (no promises lmao)
like surely you just make a new did document for did web, point it at ur pds and then just change whatever you need to to make it treat ur didweb as the "official" did and make didplc like a secondary alias (so refs dont break)
like surely you just make a new did document for did web, point it at ur pds and then just change whatever you need to to make it treat ur didweb as the "official" did and make didplc like a secondary alias (so refs dont break)
September 5, 2025 at 7:07 AM
how do you migrate from didplc to didweb btw? (no promises lmao)
like surely you just make a new did document for did web, point it at ur pds and then just change whatever you need to to make it treat ur didweb as the "official" did and make didplc like a secondary alias (so refs dont break)
like surely you just make a new did document for did web, point it at ur pds and then just change whatever you need to to make it treat ur didweb as the "official" did and make didplc like a secondary alias (so refs dont break)
リカバリーキーってdidplcの概念だっけ？
didwebなら単にdid.json書き換えるだけで引っ越せる？
didwebなら単にdid.json書き換えるだけで引っ越せる？
September 3, 2025 at 5:51 AM
リカバリーキーってdidplcの概念だっけ？
didwebなら単にdid.json書き換えるだけで引っ越せる？
didwebなら単にdid.json書き換えるだけで引っ越せる？
知らん間にPLCサーバーのGo実装が独立してた。元々は仕様を練るために別実装作ってるという話だったけど、何か他の目的もあるのだろうか。 https://github.com/did-method-plc/go-didplc
July 30, 2025 at 2:20 PM
知らん間にPLCサーバーのGo実装が独立してた。元々は仕様を練るために別実装作ってるという話だったけど、何か他の目的もあるのだろうか。 https://github.com/did-method-plc/go-didplc
afaiu, you will need to update the pds url in your did doc, which is technically pretty much the same as migration if you're on didplc
April 17, 2025 at 12:21 AM
afaiu, you will need to update the pds url in your did doc, which is technically pretty much the same as migration if you're on didplc
in Julien's onchain usecase, tho, we have two problems, one more easily solved than the other: the contracts needs to be able to call an onchain registry/mirror of DIDPLC accessible (perhaps limited to users who self-enroll/consent within BS, to bring prices down?), & each did needs a uniq pub key
January 19, 2025 at 1:51 PM
in Julien's onchain usecase, tho, we have two problems, one more easily solved than the other: the contracts needs to be able to call an onchain registry/mirror of DIDPLC accessible (perhaps limited to users who self-enroll/consent within BS, to bring prices down?), & each did needs a uniq pub key
NGINX aliasing can run a PHP script for DID's on bsky and ppl can use their subdomain here. If you have them save their did:plc to your server that alias in NGINX can point to the /.well-known/didplc of the https://username.* and link bsky to that custom subdomain on your site.👍🏻
November 25, 2024 at 7:27 PM
NGINX aliasing can run a PHP script for DID's on bsky and ppl can use their subdomain here. If you have them save their did:plc to your server that alias in NGINX can point to the /.well-known/didplc of the https://username.* and link bsky to that custom subdomain on your site.👍🏻
you can migrate to didweb from a didplc the platform gave you but you can't spin up a PDS server and populate it with 10K didweb users and pump 10K users' content onto the platform. and that's a good thing, Moscow would already be doing it if they could. it's a platform run by one company, is his pt
November 2, 2024 at 9:08 PM
you can migrate to didweb from a didplc the platform gave you but you can't spin up a PDS server and populate it with 10K didweb users and pump 10K users' content onto the platform. and that's a good thing, Moscow would already be doing it if they could. it's a platform run by one company, is his pt
hm might be tough if they do any kind of sharding in front of it that we don't know about. but maybe didplc data isn't big enough that they've needed to do that
April 21, 2024 at 12:47 AM
hm might be tough if they do any kind of sharding in front of it that we don't know about. but maybe didplc data isn't big enough that they've needed to do that
Official rust ipld dagcbor didn’t properly serialize structs so had to do struct-> json->indexmap->dagcbor
dagcbor still had a flaw in sorting keys for the nested objects so had to add ‘preserve_order’ feature
Was hard to spot and needed to put the didplc bytes and my codes bytes in a diff checker
dagcbor still had a flaw in sorting keys for the nested objects so had to add ‘preserve_order’ feature
Was hard to spot and needed to put the didplc bytes and my codes bytes in a diff checker
February 18, 2024 at 1:40 AM
Official rust ipld dagcbor didn’t properly serialize structs so had to do struct-> json->indexmap->dagcbor
dagcbor still had a flaw in sorting keys for the nested objects so had to add ‘preserve_order’ feature
Was hard to spot and needed to put the didplc bytes and my codes bytes in a diff checker
dagcbor still had a flaw in sorting keys for the nested objects so had to add ‘preserve_order’ feature
Was hard to spot and needed to put the didplc bytes and my codes bytes in a diff checker
Fine, I could make a DNS resolver that maps "[blah].didplc" to resource records based on the did:plc `service` field.
January 23, 2024 at 6:58 AM
Fine, I could make a DNS resolver that maps "[blah].didplc" to resource records based on the did:plc `service` field.
i think a repo is your full account, collections are individual data types
so your repo could be represented by your didplc and your collections would each be like
app.bsky.feed.like
app.bsky.feed.post
etc
(sorry, bsky web is convertng them to links)
so your repo could be represented by your didplc and your collections would each be like
app.bsky.feed.like
app.bsky.feed.post
etc
(sorry, bsky web is convertng them to links)
May 18, 2023 at 4:01 PM
i think a repo is your full account, collections are individual data types
so your repo could be represented by your didplc and your collections would each be like
app.bsky.feed.like
app.bsky.feed.post
etc
(sorry, bsky web is convertng them to links)
so your repo could be represented by your didplc and your collections would each be like
app.bsky.feed.like
app.bsky.feed.post
etc
(sorry, bsky web is convertng them to links)
