🥕 eat plants 🚴🏼♂️ take transit
🧠 make tools 📊 seek data
if usernames are scoped to app, no way to know an account is associated with a particular website
seems strictly better to have @apple.com vs @apple
if usernames are scoped to app, no way to know an account is associated with a particular website
seems strictly better to have @apple.com vs @apple
but at least they don’t show badges for those ones! so it’s not actually overlapping in the app security design
but at least they don’t show badges for those ones! so it’s not actually overlapping in the app security design
but our web trust model is already built on them
perhaps would be nice if we had always disallowed registration of similar domains, idk, what’re your ideas?
but our web trust model is already built on them
perhaps would be nice if we had always disallowed registration of similar domains, idk, what’re your ideas?
you’d know that account was provided by gmail.com
but if you see just @gmail.com, that’s prob official gmail, bc they wouldn’t give that one out
you’d know that account was provided by gmail.com
but if you see just @gmail.com, that’s prob official gmail, bc they wouldn’t give that one out
this doesn’t provide association with the company bc they give these out to new users
but if you see a different domain at the end of a username, you know that website gave out that username
this doesn’t provide association with the company bc they give these out to new users
but if you see a different domain at the end of a username, you know that website gave out that username
the existing domain method allows users to prove, on their own, that their account is associated with a web domain
the existing domain method allows users to prove, on their own, that their account is associated with a web domain
BlueSky staff, or orgs like NYT that they trust, can add these badges
BlueSky staff, or orgs like NYT that they trust, can add these badges
what I described was how you can prove to people an account is associated with a domain
but their new feature explained at the top here is another way to verify!
what I described was how you can prove to people an account is associated with a domain
but their new feature explained at the top here is another way to verify!
the part after the / isn’t part of the domain. that separates the domain from the path in the URL
the part after the / isn’t part of the domain. that separates the domain from the path in the URL
each dot prefix is a subdomain, underneath the parent domain
things like com and net (on the right!! not in middle) are top level domains
each dot prefix is a subdomain, underneath the parent domain
things like com and net (on the right!! not in middle) are top level domains
e.g. if an account is @google.com, it must be Google. if it’s @google.com.tricky.net it’s not
if you’re not familiar with domains, prob worth understanding a lil! otherwise ya might get phished (scammed by an impersonator)
e.g. if an account is @google.com, it must be Google. if it’s @google.com.tricky.net it’s not
if you’re not familiar with domains, prob worth understanding a lil! otherwise ya might get phished (scammed by an impersonator)
i love the bus, but this is good too
i love the bus, but this is good too
vs. trying to build up an understanding from scratch, scanning docs for the right apis, etc.
it helps you quickly pinpoint what you need to know
vs. trying to build up an understanding from scratch, scanning docs for the right apis, etc.
it helps you quickly pinpoint what you need to know
you can read that code and know how to do something like that next time
its almost like a tutorial for your specific use case. could even ask llm to explain it all
you can read that code and know how to do something like that next time
its almost like a tutorial for your specific use case. could even ask llm to explain it all
i recognize most things, but what are the less obvious things you included?
i recognize most things, but what are the less obvious things you included?