am very excited about Doll’s appview project. making relays non-archival was the key to making them affordable/easy to scale. Bluesky (the company)’s Bluesky obviously is archival, but for a community to run one cheaply this seems like a great way to keep costs manageable
The next feature is a configurable retention system. No more balooning database if you dont want it. You will be able to set the days it retains information and anything after that is pruned. You will of course be able to set it to retain all and backfill.
People have talked about narrow sliced networks to keep costs low - basically make the same compromises as Mastodon. It’s actually way more interesting (imo) to instead compromise on history - you’re reading fresh posts 99.9% of the time after all, and it wouldn’t break feeds like narrow appviews do
narrow vs shallow 🤔
a smart client could probably be clever and start hitting the PDS directly when it’s out of the archive window, then use backlinks or something to pull in old replies on demand. inefficient but the main hot path (viewing feeds) is still using the efficient atproto architecture
React 19.2 is now available!
This release includes Activity, useEffectEvent, React Performance Tracks, partial pre-rendering, and more:
react.dev/blog/2025/10...
Performance Tracks are a new set of custom tracks in performance profiles that show more info about your React app.
They include a Scheduler track that shows the priority of what React is working on, and a Components track to show which component is being worked on.
react.dev/reference/de...
activity is absolutely huge for RN though, since you have to basically keep every screen in the history mounted. now they can be deprioritised without using hacks like react-freeze
to be clear I haven’t fixed every Android crash ever. but we can see from the stats there’s been a definite spike since version 1.107, and I now know why (it’s the new toasts)