Post

And now we’re back to the “app goes away so does your data” problem that atproto helps mitigate. I also don’t want to be responsible for my users data across applications. PDS hosts should focus on being PDS hosts, and apps should focus on being apps.

now, explain that the average user who is not a tech nerd. "why do I have to create an account on bluesky to use XY?" "I created a bluesky account; what's atproto?" "why can I not create an account here?"

Brookie

@brookie.blog

This is just a UX problem. You don’t need to host the PDS yourself to explain this better. New User? -> Choose where your data lives (bluesky, blacksky, etc) -> PDS signup page (prompt=create) -> return to app. PDS implementations of prompt=create like this will help: bsky.app/profile/this...

Emelia@thisismissem.social

Y'all! New PDS release!!! 🥳 It includes support for the new prompt=create flow! So like, everyone using the reference PDS server can now sign up with OAuth on their PDS. Thanks to @divy.zone for shipping this! github.com/bluesky-soci...

Brookie

@brookie.blog

Alternatively, just offer non-atproto accounts in addition to atproto accounts and make it easy to upgrade a non-atproto account. This is the current implementation on @pckt.blog

I am not too sure about how a "oh, where do you want your data to be? [N random names]" works for non-tech guys all that well. tbh we need some QA from people who have no idea about atproto and test it

+, 99% of users currently being on bsky, and most atproto apps asking users to create an account on bsky, does not help at all at making anything decentralized. note, you knowing how atproto works and being nerdy, doesn't make your mother understand it

try to tell your mother that she has to (for example) create an account on selfhosted/.social first, before she can use that fancy twitter or instagram alternative you have been talking about. or better, try to make her figure that out on her own. apps have to be intuitive. every step you...

mew

@nekomimi.pet

what if i believe they should be hosting their own pds and not be on someone else’s hard drive

"they" as in the users? you cannot just ask users to set up their own PDS, unless you are only targeting power users

mew

@nekomimi.pet

i only care about atproto because it’s easy to self host your repo but apparently i’m alone in this

not everyone has a server, the know-how or wants to do it. not everyone is a tech nerd

This was something I was messing around with but couldn't wrap my head around. Make it so PDS tenancy is a library that devs can just pull in. Saves them rolling an auth solution and gets their uses on the atmosphere. Basically @selfhosted.social in a can

Teon ⁂

@teonbrooks.com

1 Feb

I would definitely like a world where an app dev w/ a domain could just manage new user repos in an existing PDS like Selfhosted and provide a subdomain for identity handle. it would decouple the two. It could provide a potential business model for PDSes: storage (free/premium), management, etc.

That's obviously oversimplified but a package that makes it easier to set up PDSes instead of having a user login table or cognito for auth

well, "just" a library to plug your postgres pool and S3 credentials into and "done"

Right. I got hung up on the fact that a PDS is an actual server, not just a bunch of records sitting in a DB (at least I think). But if that's not the case or there's an easy way to spin up a bunch of parallel servers on the same box then this would be the lib to make.

Or, speaking of cognito, @selfhosted.social or other PDS providers could set up a competitor to Okta... except user management creates PDSes for the users instead of just records

ehhhhhhhhhhhhhhhhhhh

a hot take but you're absolutely correct

Luna

@shi.gg

I don't think its that hot. every service should be usable on their own

Kara

@karashiiro.moe

client-only apps vanishing like tears in the rain

there are apps, like @pdsls.dev, where are PDS obviously doesn't make sense, since you don't have to login to use it. but generally speaking, a service should offer protocol/service on-boarding

🦌≈

@aviva.gay

idk kind of a mixed take, yeah big services should absolutely offer a pds but for smaller or more hobby flavor services pushing people to projects that actually intend to run responsible pds makes more sense. one day we will see a pds with no backups lose accounts

🦌≈

@aviva.gay