that’s just libertéslop. you only like it because you believe in the rights and dignity of all men
4 60atproto is cool because it is fundamentally pragmatic about what it means to be decentralised. decentralised where it matters, simple and scalable where it doesn’t
4 20 153ask yourself: does this change the power dynamics of the network
Y: decentralise it!
N: keep it simple!
1 1 30I really am finding that I prefer to use claude to write a very small amount of difficult code than a large amount of easy code
6 5 86claude is *really* good at custom eslint rules, it turns out
Add ESLint rule to enforce Lingui msg usage by mozzius · Pull Request #9789 · bluesky-social/social-app
Adds a custom ESLint rule 'lingui-msg-rule' that ensures the Lingui _()
function is called with msg`` template literals or plural/select macros,
preventing accidental misuse like _('str...
github.com
here’s my harebrained claude system idea:
primary agent does a plan->clear->implement loop, to keep context fresh. however, it then forgets things
this is where a team of “scholar claudes” come in. they each have a chunk of the full context, review the plans, and chip in with helpful insights
5 1 29the scholar claudes *must* believe themselves to be wearing long scholarly robes, and speak in a dreary tone
3 26when a primary claude finishes their task, they join the scholars, and become the expert on their plan
6finally found a fix for the video fullscreen+image crop being broken. turns out it was caused by changing the app icon using the secret settings page (it was hidden for a reason!)
Fix issue with activities being unavailable (fullscreen, crop-tool) by mozzius · Pull Request #9782 · bluesky-social/social-app
Fixes #9288
Fixes #9437
Fixes #9324
Turns out, if you changed your app icon using the unreleased settings screen (it was hidden for a reason 😡), my library would disable all other activities. What ...
github.com
lexicon has floats, if you’re brave enough to put every single IEEE754 float in a string field’s `knownValues` array
3 28don't look at the explore page. nothing is happening there, so you don't need to worry about it. please don't look
11 1 65moving my brain dumping thread here. I think there’s two issues at play w.r.t. perf
I tried putting it behind useDeferredValue, but it didn't do anything as it seems like the scroll handler has an unstable identity for no good reason
1. List component rerendering.
we need to change a scrollview prop on iOS. I already scoped this to iOS-only, so it’s not a perf concern on Android, but it’s got a massive over-render problem. changing this one tiny prop causes every list item to rerender, which is ridiculous
1 2Easy solution - take my existing useScrollsToTop hook, and put a useDeferredValue on it. therefore we can defer this nonsense until after the lightbox has finished rendering
alas no. List rerender anyway. Profiler blames onScroll, and I added logging and yeah it changes on that initial ctx change
1 2I’m pretty sure it’s just unstable, I.e. different identity on each render, which shouldn’t be the case - it’s not doing anything here! next step is to narrow down what’s causing it to change. Reanimated has some magical auto-dep-array stuff which is probably to blame - likely doesn’t mesh w/ RC
1 22. Slow on Android
Perf on Android is still unacceptable, especially for 2+ images. I have yet to dig in but I have speculation.
the animation gets triggered in a requestAnimationFrame. I’m guessing the main thread is getting locked up so it has to wait a really long time?
2 2Each time each image in the lightbox loads, it re-renders with its image dimensions. So we have 4 fairly heavy components (each image) rendering invisibly before the animation can begin, and each one re-renders as they load. maybe the animation is queued behind that whole process?
1 2what I will try is deferring rendering the other 3 images until after the animation is complete. they’re being prefetched already so it shouldn’t cause any functional changes?
1 1
