It should be called an API server, App server, or backend.
ExpoAppleAuthentication Error
Hey, I'm trying to use ExpoAppleAuthentication, but it's throwing a few errors: `The native view manager required by name (ExpoAppleAuthentication)…
Your ‘App’ Could Have Been a Webpage (so I fixed it for you…)
I was asked to install a mobile app to get access to the itinerary of a trip to Disneyland I'm taking with the kids. Fuck that noise: couldn't it have just been a Web page? An hour of reverse-engineering later, it is, and it's superior in virtually every way to the "app" that it replaces.
Updates
A library that enables your app to manage remote updates to your application code.
colibri.social/appview
[READ-ONLY] Mirror of https://github.com/colibri-social/appview. The AppView (backend server) for Colibri
API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited
19 votes, 14 comments. Carefully prepared and ran a task to have it running overnight and instead of seeing it in the morning completed, I see "API…
Some W users experienced problems today because W was relying on Bluesky’s AppView. When their AppView went down, parts of W went down with it. Our own AppView was already under development and it kept working. So we’ve now switched W over to our own AppView, currently serving verified users only.
New project I built last week: a kind of "isblueskydownforeveryoneorjustme.com" dashboard, so I can stop wondering "is it my PDS or is it the AppView" when the app isn't loading - bookmark it for the next time something doesn't work but you're not sure what 🙂 status.feeds.blue
Atmosphere Status
status.feeds.blueUpdate: The external AppView is stable again, so W has switched back. All AT Protocol users are now visible again. Our own AppView worked well as a fallback, but currently only includes W and verified users. In the future, you’ll be able to choose which AppView to use. Thanks for your patience.
Can think of it as two different AppViews (or just atproto apps) The DMs is did:web:api.bsky.chat#bsky_chat and the did.json is found at api.bsky.chat/.well-known/did.json And the AppView as we know it is did:web:api.bsky.app#bsky_appview api.bsky.app/.well-known/did.json
to reiterate on this, an AppView server should NOT be interposed between the user and the PDS: the client and PDS are in the user sphere of trust, but the service is adversarial. the PDS is the most important write sink and should be primary, since an app can't be trusted to not shut off PDS writes
mary🐇
doesn't mean i shouldn't try. mary.my.id/musings/atproto-and-oauth
