for tranquil we also decided to do away with the singular admin password and instead have admin accounts. that way multiple people can independently added and revoked as admins without needing to worry about admin password rotations or special client-side admin auth handling
we have an admin page built into the frontend yes! im not sure off the top of my head how featureful it is yet but its there and we're definitely interested in making it as useful as possible!
relevant parties have been contacted and we believe the situation is under control. now we just have to find that password ...
itll show our oauth if youre migrating from one tranquil PDS to another ;3 but yes only in that specific case.
also technically tranquil PDSs can have just about anything as the oauth consent page as the whole frontend is interchangeable
as well as things like didplcbft
did:web as a techie option is fair though in my (nels) opinion though. it has enough footguns that non-techy people probably shouldnt be using it. at least not for their main user accounts. i think the way forward here is to instead improve the state of the trustworthiness PLC through the PLC org
tranquil has support for pds hosted did:web yes. but that comes with the major downside of under mining credible exit since you end up not really being able to fully migrate away from the PDS that owns your did:web.
pushed a tiny fix for tranquil pds on debug.hose.cam
the debugger now shows `version` from the pds `describeServer` if present, falling back on the `_health` endpoint (for bsky pds impl) and no longer failing if the response at _health is not a JSON object
idk about lewis but i (nel) would be interested to hear about it at least! if for no other reason than to hear what you got since the PDS holding the private key for your signing key is kind of built into the design of the protocol in a lot of ways
tangled.org/tranquil.far...
sometime in march we will call it "production-ready"
How it feels to use Tranquil
Source www.instagram.com/reel/DUDU87F...
Both of us will be at @proto @fosdem later today! come have a chat if you can and want.
oh very nice. do you have lexicons for those somewhere? i see the core of it is just getRepo and getBlob but i assume theres more since you mention stats?
be able to scale down.
Everyone should be able to self host their PDS and have a good experience with modern features! No matter if they're a single person with their personal PDS or a big organisation providing account hosting for thousands or millions.
Tranquil aims to be a PDS done "the right way". Yes it's a hobby project for us but it's also a project born out of a wish that we all had better options with more features. As the readme alludes to we want to be able to scale up to multiple node deployments but that doesnt mean we dont want to
probably will! we'll most likely have a backup section in the account management as well aiming to make it easy to do local backups. pointing to pdsmoover backups from there seems nice.
im not actually sure if we do yet but if we dont its definitely coming. if not in the migrator then in the account management interface, probably both
migration wise the work has gone into good UX. like resuming partially completed migrations, using oauth, an easy to understand stepped wizard, etc
migrations are built in to the frontend yes! we dont recommend migrating your main account yet. tranquil is still in its early stages. but its stable enough that an alt or the like can absolutely work just fine. heck @lewis.moe is on tranquil.farm so if youre fine being a bit risky you can do main
This is how it feels to work on tranquil
well maybe not “it all” but whatever seems sensible and/or fun
What features would you like to see in Tranquil that don’t exist in the ref implementation? We can do it all if you just ask nicely in an issue on our tangled repo
we finally moved the tranquil pds repo out from lewis' account and onto tangled.org/tranquil.far...
please star it! otherwise it looks like just lewis gets all the glory!
This is something Ive (Nel) seen as the one possible benefit of this becoming an official thing within spec ever since I first came up with the idea. It would be incredibly useful for the UX of using these accounts. Currently afaik its not exposed anywhere in our impl but I think we should do that!
Con: even after migration your original pds technically has full control of your account and could theoretically take control of your account whenever it wants to. effectively undercutting credible exit
Pro: self hosters get one single software stack to fully manage their account on atproto
Pro: easy did:web without having own one’s own web domain and serve a doc there
Con: if a PDS goes down, there goes the user’s identity, even if they’ve migrated away already
This account’s did:web is hosted by the PDS itself. This is an optional feature of Tranquil PDS!
Even if a PDS-hosted did:web user decides to migrate off this instance, a minimal did-doc will be served and available to edit no matter where the user goes. Pros and cons in replies…
did someone say PDS with passkey support? 👀
We aim to be fully production-ready around March. Until then, no guarantee of stability. This serves as a warning to anyone using Tranquil PDS before we announce that it’s stable! There is a risk of total account bork.
…at the same time we would love testers to find more bugs and quirks :P
seconded i *really* love that what. i love the moon so damn much. the sea of tranquillity is an amazing idea
ya go ahead
