iiinova — where your digital self keeps evolving

In this mortal life, the vicissitudes of fate are our lot; we come into the world weeping, yet must journey through it with a smile. Friends, let us keep this together indelibly in our hearts: however long our lives may last, the brotherly bond we share in this life shall remain.

270

im addicted to these amaran led panels 🥹

220

does anyone else need to put a fan right up next to their 4k x? mine likes to shut off i think every so often and im tempted to disassemble and put a ton of heatsinks on it

000

Xe @xeiaso.net · 29/09/2026

damn ok this game is crazy good

040

Reposted by midwest emo fan

I am a: - [ ] man - [ ] woman - [x] load-bearing seam looking for a: - [ ] man - [ ] woman - [x] way off this wild ride

317715

We need to talk about the MVG situation

120

i should probably not be a software engineer

280

geist is the new inter (derogatory)

2140

Bryan Cantrill @bcantrill.bsky.social · 28/09/2026

ne supra crepidam and all that jazz

000

Reposted by midwest emo fan

Fool's Expertise bcantrill.dtrace.org/2026/09/27/f...

bcantrill.dtrace.org

Fool's Expertise | The Observation Deck

59120

austin @aparker.io · 28/09/2026

worried about the death of the product as we know it

120

Reposted by midwest emo fan

hidden secret of software products - 1. you can explain 90% of all feature gaps in the backend by compute access/cost 2. you can explain 90% of all feature gaps in user-facing products by moderation access/cost

0433

Bsky+ @bskypl.us · 27/09/2026

woah my back still hurts

010

Reposted by midwest emo fan

Let's go over some of the extension features! ✨ Emoji picker 🚀 Much like in Slack and other chat applications, write a colon (:) followed by the name of the emoji and you will get an inline picker. Some emojis have fuzzy matching, so typos won't matter 😉

Bluesky post composer with :roket written, and the inline emoji picker showing the following emojis: 💔 🚀 ⛑️ 🌹 🤖 ☄️ 👨‍🎤

175

for as shitty as guillermo rauch’s politics are as least you can’t claim they came out of nowhere 😭

1120

for all the posts about the logo i’m surprised nobody noticed the font changed too

260

dame @dame.is · 27/09/2026

came in matrix doesnt sound nearly as good

060

Reposted by midwest emo fan

i’m seeing non-stop AI/EA/rat/x-risk/pdoom shit on my timeline and meanwhile there’s an entirely different neighborhood on bluesky that is having a neurotypical pikmin debate how does one move neighborhoods?

114615

rain 🌦️ @sunshowers.io · 27/09/2026

Strike iPhone gently to report a bug

020

Reposted by midwest emo fan

Friends don't let friends use serde_json::Value as a stepping stone

$Appendix: why not serde_json::Value? For reading versioned data, a naive implementation might do something like: struct ReadEnvelope { version: u32, data: serde_json::Value, } impl ReadEnvelope { fn deserialize_data<T: serde::de::DeserializeOwned>( &self, ) -> Result<T, serde_json::Error> { serde_json::from_value(self.data.clone()) } } But this has a few pitfalls: serde_json::Value has funky behavior around objects in a few different ways. For a payload like {"a":1,"a":2}, serde_json::Value drops the first a and only keeps the last one. This crate lets the deserialized type decide what to do with duplicate keys (a derived Deserialize would typically reject duplicate keys). There is no workaround for this with serde_json::Value. Object key order is only preserved if the preserve_order feature is enabled. This can lead to surprising roundtrip behavior. There are a couple different workarounds, neither of which is satisfying: Enable the preserve_order feature, which affects all other crates in the Cargo dependency graph. Accept that key order might not roundtrip. This feature-flag coupling is hard to explain to users; we can do much better than this. With default features, serde_json::Value cannot represent certain types that serde itself supports deserialization for, such as u128s. Like 1.2 above, turning on arbitrary_precision would fix this, but that is undesirable for the same reasons. If deserialization fails, the error message doesn’t carry a line/column offset. An in-between option is serde_json::value::RawValue, which allows part of a JSON payload to be stored as a string, and addresses points 1 and 2. But for point 3, RawValue produces incorrect line and column offsets on error (the offsets produced are relative to the captured part of the payload, not relative to the full payload). Incorrect values are worse than not having the line and column offsets at all.$

Instead of either option, we perform passes over the underlying JSON directly:

The first pass validates that the JSON is well-formed, and for envelope reads, records which top-level fields are present.
For envelope reads, the second pass reads the version, ignoring the data.
Then, depending on the read method called, we perform one or more deserialization passes through the VersionSet::parse callback.
Why not one streaming pass? Because data could come before version, for example if serde_json::Value is used without preserve_order, or with jq -S.

5775

Reposted by midwest emo fan

ponder @ponder.ooo · 27/09/2026

new scientific study suggests water may be wet

what improves developer productivity at google? code quality

1294

Why @why.bsky.world · 27/09/2026

god damn it what the fuck

240

Reposted by midwest emo fan

If you bring a coffee to an interview I’m gonna judge you based on which coffee shop you went to. The drink is not a problem but poor taste is. It’s not hard, people.

13935