right
imagine how easy switching to bsky would be if twitter used atproto

bsky might not have been needed to exist even! (just like the hosting providers example)

yes
so there're already platforms like that, pretty cool!

good read!

one question i have now
how will atproto help exactly if you want to move from bsky

yes the data is public, but how different is it from a data export?
cause the data is incompatible with other social apps anyway, unless they chose to do so, isn't the data also "dead" here?

any specific one of those made a good replacement?

we got a little preview of that with AI-generated written content and it's already dystopian

you don't even have to read the code to know it's AI slop

the clanker pr description is enough

ofc if you usually lift 100kg you won't lift 200kg by mistake

using tailwind mainly... so i think none?

oh, i see

would be happy to help with that

would it make sense to show ts errors if shallow: true & limitUrlUpdates properties were used together?
I feel this might trip up some users if they didn't read the docs carefully.

🎉🎉

regarding debouncing, is there any point of using it in case of SPAs? (shallow: true) as the state updates immediately

I wrote a short article about this:
islamnaasani.com/blog/ftdd-fu...

recently i started to explore serverless, yes it's not a sliver bullet

but for people doing side projects, or quick prototypes and can't (or don't want to) pay for it. Serverless platforms "Hobby" tier makes getting started very easy

That's why I started adding project rules (and not just user rules) that instructs the Al to never write comments unless specified.

and as a result, I started to develop Ad-blindness-like behavior, I unconsciously ignore comments now, which's actually harmful, because now I may skip over intentional, useful comments written by developers.

what possible security issues this may cause? any resources to read?

this really resonate with me, I would only add that you should still be an expert at one or two domains.