this one is hysterical
Every now and then, someone shares a hilarious Kagi result. Now they'll have a place in the Kagi Bloopers hall of fame:
help.kagi.com/kagi/bloopers/
to add to this, there’s a few product-y reasons why I would really like a createPost API
1. we could run a server-side language detection model that actually works, so we wouldn’t need the language select in the client (it sucks)
2. you wouldn’t need to specify a createdAt time anymore (cont.)
Nerding out about the question of whether the client or the server should be the one who speaks to the PDS
The politics of purely client-side apps
There's a surprisingly nuanced discussion in development about the political economy of clients and servers in the Atmosphere
pfrazee.leaflet.pub
3. for more casual API users, i.e. people doing integrations, we could do stuff like auto-detecting facets. 1000x better DX
4. we could force people to specify aspect ratios on their images 😈
5. we could check if the post is actually gonna be valid - i.e. throw an error if it would fail a threadgate
3 2 19lotta product reasons here! it’s so weird from an outside perspective that our GET APIs are nice and normal, and our POST APIs are extremely unergonomic protocol-y jank. creating a post is the core feature of the app and for some reason we’re out here calculating our own TIDs 😵💫
1 1 18>ask if new browser is real or chromeslop
>”it’s a good browser sir”
>it’s chromeslop
6 21 219Call for retirees to be paid state pension for five years even if they die
Call for retirees to be paid state pension for five years even if they die
Call for retirees to be paid state pension for five years even if they die
independent.co.uk
is it just me or they took all the style out of the EUV interface compared to the new look of CK3/Vicky3. looks kinda old fashioned almost lol
3 7this is going to be really exciting! it’s cutting-edge stuff
We're working on a writeup that I'm pretty excited about --
Importing your address book to find friends is common for social, but it's insecure to enumeration attacks and database leaks so we've historically refused to implement it. The team has a proposal now that we think solves those risks.
if you don’t read this I’m hiding your reply:
1. IT’S EXTREMELY OPT-IN - bi-directional in fact, so maximally privacy-preserving
2. you don’t have to do it
3. it’s opt in
4. you don’t have to do it
5. you don’t have to tell me you’re not going to do it, I’m not going to do it either
6. see above
3 3 48election rigging!!! incredible
Salutations Victorians!
With the upcoming Negotiation and Amendments features for Update 1.12, you might be able to leave Traditionalism behind, for a price!
Join Chris and Victoria to see how you can shape the terms in your favor, but remember the fine print...
Read more here: pdxint.at/4nFVrbQ
like, wtf.... it's calling updateLayout() to tell the native side to re-adjust the sheet height. if you add a console log before or after, it's instant
5 2 18quick proof they’re doing this
Looks like X is juicing web visit numbers by opening a browser WebView in the background whether the user visits the link or not.
They've re-invented pop-under fraud (allegedly).
news.ycombinator.com/item?id=4580...
anyway found a nasty little crash caused by sparse arrays and implicit reliance on the order of things rendering
Prevent sparse arrays in snapToOffsets by mozzius · Pull Request #9329 · bluesky-social/social-app
I accidentally introduced something quite stupid in #7128 - it would lay out all the interest tabs, and then when all the tabs had been all laid out, it would set the offsets to snapToOffsets. Howe...
github.com
