Very interesting, the lube experiment that was cited in the article was kind of shocking when you stack up the chain lifetimes. But when you start adding up all the lifetime maintenance and replacements, doesn’t a carbon belt setup start to make much more sense for most riders?

Alt: Copilot after dropping your production database

To save a click: May 20th

Ask it ten times to make list of 20-30 random words

This is true on ootb models but not the universal rule. You could adjust the temperature all the way up and get something way more random, probably to the point of incoherence.

The trick is balancing that with keeping the model doing something useful. If you’re clever you could leverage /dev/random or similar as a tool to manually inject randomness while keeping the result deterministic.

Someone remake this but with Good-Bad-Fanservice

Chili garlic tofu

Though to be honest I don’t usually use a recipe or cook anything. I cube a block of soft/silken tofu, dump on some chili oil, add some kind of vinegar (and maybe sesame oil if I have it), and eat it raw and cold.

You could probably do it with any kind of sauce you like and put it on rice if you’re feeling fancy

ITT: OP argues for I2P but doesn’t know it, asserts HTML can’t serve static content, assumes static content can’t be malicious or served by bad actors

Photos are the same as most other data, you can store them pretty easily long-term in a physical medium. Of course, capturing an image is much easier and more convenient with a digital device, but that doesn’t mean it has to live digitally indefinitely. It’s simple enough to have an instant digital camera with a built in printer and access to a high quality scanner.

If you held a gun to my head, I could pick out a few dozen personal photos that I own that are worth saving physically. If you allowed me a modern flash drive’s worth of storage (64-128GB, ~5000 good quality images), I could pretty easily store every picture worth a second look from my entire lifetime.

Apple’s marketing driven perception that every single person needs a cinema quality camera (and cinema sized storage) in their pocket is ludicrous. Only a tiny fraction of people actually truly need that. Let them borrow that gear from a library if we want to preserve fair access.

To be honest I don’t have any personal digital information that I give a shit about. It’s value is only derived from its ability to identify + track me, either for my convenience or for the highest bidder’s. Computational liberty is only an issue because we’ve made everything digital by default and that mindset has leaked into critical social functions (taxes, law, logistics, healthcare, etc…).

Software and data bloat is more astronomical than most people realize. Only about 10% of persisted data is ever touched again (don’t look up the ecological implications). Amazon could capture 90% of all compute hardware and the entire human race could get by just fine on 10%. We wouldn’t have access to niceties like app stores full of niche apps, 24MP phone cameras, 4k movies, 10 sluggish layers of software abstraction, 15 years of photos you never look at, etc…

But you could run a simple message server on basically any scrap of IoT e-waste. A highly available static website can be hosted with an old phone and a solar panel. Any device (fridge/watch/calculator/pregnancy test) can run Doom. All of Apollo 11’s source code is a fraction of the size of most web pages.

We’re continously expanding our hardware usage for infinitesimally small gains. We should demand that our governments legislate digital austerity for dozens of reasons, just pick what resonates best for you. Personal privacy, energy usage, ecological damage, corporate capture, information rot, brittle supply chains, national security, etc…

Crazy that companies will do this shady stuff with client side code. At least it was slightly obfuscated at first, but that’s just incompetent fraud to leave it so obvious that a self professed non-software engineer (though clearly a smart guy) can read it and deduce what’s happening. Throw a tiny bit of random noise to the stepdown logic and it becomes much harder to find and reproduce as proof.

I feel the bad feedback trope is inverted in 2025. Devs will release a game, get a solid audience, then completely change mechanics or style or direction for no apparent reason. The audience complains (pointing out what they like in the original release), the devs tell them to kick rocks and the game shrivels up and dies.

cough ^Battlebit cough

My shameful secret is admitting that LLMs are great for things like getting comfortable with a programming language. They’re generally trained on the same publicly available samples as these courses and the conversational extrapolation is great for identifying concepts you forgot the technical terms for (ie. “How would I do this in python: [Java code]”)

Vibe coding sucks, but walking through some examples with an LLM and a REPL can save hours of navigating docs or Hello World blog posts.

Idk the model but can check later. Removing/modifying it isn’t an issue, but my household wants to use it since it’s there.

I’m not personally opposed to a camera but would need to be in full control of the feed. My main goal is keeping it simple and cheap for now, so not replacing a functional camera is very tempting. Later on I can look into real alternatives but an afternoon project will do for now.

Wouldn’t be operable, but I like your moxy lol

Well most of cleaning is just making things aesthetically pleasing to your preference. So long as nothing is a health hazard or an obstruction to your normal function then it’s all good.

Might be a pet peeve I guess, but clean lines with no loose floppy parts feels better to me. They also always spread out and take up more space than I expect (oops, half my desk is now my phone charger).

I’m not one to perfectly route and bundle cables but even jamming them under furniture or behind a lamp feels “cleaner”. The dangling power strips would drive me nuts.

Not that bad imo. My rule of thumb is spills/sticky stuff/rotting food are the hard things, anything else is just a matter of moving stuff around.

For advice:

0. Toss the webs/decoration. That’s 75% of the bad vibes.
1. Pick up until you have a clear floor, even if that means into a laundry basket for later.
2. Clear off surfaces, shuffle necessary junk on desk until it looks intentional
3. Toss the big furniture things above the bed by default, you know deep down you’re never going to use them [this is the hardest part probably]

-------- Diminishing Returns --------

4. Better wire management, the more you can get out of sight the better
5. Organize shelves, toss/give away what you can get rid of
6. Simplify in general (Do I need the TV and tablet? Are these plushies bringing joy? Etc…)

Is this groundbreaking? Seems like stuff that other dependency managers have had for 10+ years

Couple of reasons of varying importance:

• Security. Even when you limit operations or table access it’s very easy to mess something up. Some new employee starts storing sensitive data in the wrong place or a db admin accidentally turns off the wrong permissions, etc…
• It’s secretly more overengineered than a standard api despite looking simpler. If your app needs extremely robust query capabilities then you probably have a use case for an entire analytics stack and could use an open source option. Otherwise your users probably just need basic search, filtering, sorting, etc…
• Ungodly, Flex Tape tier tight coupling. Part of the purpose of an api is to abstract away implementation details and present a stable contract. Now if you want to migrate/upgrade the database or add a new data source, everyone has to know about it and it’s potentially a major breaking change.
• Familiarity. If someone else steps in to maintain it it’s much easier to get up to speed with a more standard stack. You don’t need a seven layer salad of enterprise abstraction bullshit, but it’s useful to see a familiar separation of auth, queries, security, etc…
• Having the option to do business logic outside of the database can save countless headaches. Instead of inventing views or kludging sprocs to do some standard transformation, you can pull in a mature library. Some things, such as scrubbing PII, are probably damn near impossible without a higher tier layer to work in.
• Client support. Your browser/device probably has a few billion options for consuming a REST/HATEOAS/graphql/whatever api. I doubt there’s many direct sql options with wide support.

I probably wouldn’t do it outside of a tiny solo project. There are plenty of frameworks which do similar things (such as db driven apis) without compromising on flexibility, security or features.