[flagged]
How to self-host all of Bluesky except the AppView (for now)
11–20 of 83 posts
Re: How to self-host all of Bluesky except the AppView (for now)
#12author here, should you have questions!
How are Direct Messages implemented in Bluesky if anyone can access a firehose of all network activity?
Re: How to self-host all of Bluesky except the AppView (for now)
#13How do I ask the mods to swap out the link to the actual post instead of my blog's front page? (...also, the title, as the original has the caveat)
It's likely the correct page was submitted. The correct page includes a canonical link in the HTML: HN will replace submission links with the canonical link if it's found.
oh. time to look at the code of my blog...
Re: How to self-host all of Bluesky except the AppView (for now)
#14[flagged]
didn't say it was cheap!
Re: How to self-host all of Bluesky except the AppView (for now)
#15Re: How to self-host all of Bluesky except the AppView (for now)
#16Earlier quoted context omitted.
@dang a better URL would be https://alice.bsky.sh/post/3laega7icmi2q (I can't tell if Dan has an alert set up on his handle or whether he just sees everything, but hopefully that works :))
dang doesn't have an alert and he doesn't see everything. https://news.ycombinator.com/item?id=41317232 The official way to contact the mods is in the footer, i.e. email hn@ycombinator.com
Ah thanks, good to know. I guess I've just been lucky with it and developed a superstition that it works.
Re: How to self-host all of Bluesky except the AppView (for now)
#17Earlier quoted context omitted.
Thanks for making yourself available to answer questions! Hopefully this is not a dumb question. Is plc.directory a single point of failure for BlueSky users who want to take advantage of the benefits of a did:plc? And if so, is that a permanent thing or down the road will there be multiple interoperating did:plc directories?
yes it's a SPOF. not sure about the second question, but i do know there are plans to transfer its ownership to an independent foundation
Transferring to an independent org is what we're talking about now, yes.
The backstory to PLC is that we picked up the DID standard and looked for an existing registry-method that would satisfy requirements¹. None of them really did. We then surveyed mechanisms for decentralized operation: DHTs, open blockchains, permissioned blockchains, and federated databases. Of them, the two blockchain variants seemed perhaps promising, but still premature since (as of 2022) you there's cost variability due to load and in some cases bad transaction latency (eg 10 minutes).
We decided the best decision was to create PLC, which matches all of the requirements except for longterm meta governance. The way we designed it was to make the registry mechanics transferrable to a different protocol in the future, so that if for instance we decided (say) a DHT was suitable (it's not) we'd be able to use the same identifiers but change resolution and mutations to a new process. Then we started talking to other SMEs to get their take.
Ultimately the solution that's gotten the most favorable response has been setting up an ICANN-style independent organization to operate it. This can be joined with a couple of interesting systems, such as mirrors which tail a certificate-transparency-style audit log, and which could even serve as transaction witnesses to indicate when the core registry might be rejecting updates ("write censorship").
What can I say, some things take time and stakeholder-building. Look up the history of DNS and Network Solutions Inc for a bit of a wild ride that people have forgotten about. One other thing I should point out is that the DID spec enables multiple registry methods. Atproto currently supports did:web, and if other methods show up which satisfy the requirements then we are interested.
¹ Secure against manipulation by the registry operators, longterm meta governance, highly available, reasonable transaction latency, reliably low cost that's not dogged by token speculation, low ecological impact.
Re: How to self-host all of Bluesky except the AppView (for now)
#18Earlier quoted context omitted.
dang doesn't have an alert and he doesn't see everything. https://news.ycombinator.com/item?id=41317232 The official way to contact the mods is in the footer, i.e. email hn@ycombinator.com
Ah thanks, good to know. I guess I've just been lucky with it and developed a superstition that it works.
He is also extremely active here, so there's a good chance he reads and responds to a random comment without an email. But email is the approved (and fastest) way to go about it
Re: How to self-host all of Bluesky except the AppView (for now)
#19author here, should you have questions!
What's in that 4.5 TB? e.g. message metadata? Message text? Media?
What time window does it cover? A rolling N day window? Everything since year dot?
Can it be pruned? e.g. only data of accounts followed or messages interacted with
Re: How to self-host all of Bluesky except the AppView (for now)
#20This is all academic for me until Bluesky gets the functionality to get an account back onto their main network, for DR if not peace of mind that an "undo" is possible.