hell yea bluesky app should stop using atproto

(of course, i’m not too serious, and i’m also not a web dev, and i do realise not everything would move to server side, but i do think there’s value in one api all apps share?)

i mean i guess it’s similar to inventing a new service, “app view view”, that talks html (or similar) and not atproto, but i guess the “problem” is that when you are running both the app view and the app view view, it’s unnecessary overhead to have the app view view actually talk to the app view

yep and in fact we were considering making such a service anyway (backend-for-frontend architecture). It’s actually way less overhead since if we run app logic in the rack right next to the appview it’s ultra low latency, we’re able to cut down waterfalls and give the client exactly what it needs

For example, we filter out a ton of stuff on the client side for mod reasons (think mute words etc). what if we did this on the server instead?

fwiw this could be an app view thing