I can assure you it won't be this llama.
Relative to their peers is somewhat more telling. But generally agree.

Jokes on you, a team I work with split their creds into multiple pieces, concatenate them where needed in their bootstrap, and committed then as plaintext in their repo.
I gotta ask: how often are you buying new (to you) records? What are you doing with the ones you've previously acquired?
I used to have a pretty solid CD collection, but I kept them all in a binder that's since been lost to time. Every once in a while I think about rebuilding a physical media collection and records are appealing. But we don't have a ton of free space and I'm wary of storage. Records are also physically large, which seems like it would make buying/selling difficult unless you have a local scene you can trade through without needing to ship things.
But! I am only watching from the outside. Any insight you can offer would be appreciated.
Single instance, but still federated is somewhat odd to me. Part of the point of multi-instance was to provide protection against a single instance going off the rails. That's not to say that multi-instance doesn't come with its own class of problems, like community fragmentation.
The entire description reads like it was written by a LLM. Fediverse users have a decent nose for generated images, so I'm surprised this generated language flew under the radar.
That said, I can't fault OP for using AI to build a thing they wanted to build. The plagerism machine is real, but it's hard to tell people not to use it. Even more so when it's being used to create something that wouldn't have existed otherwise (ie it's not replacing anyone's job).
Companies pouring money into AI are the ones to look at. Example:

They're still doing doing great if you zoom out further, but it's a potential start.
Not OP, but I'm in my 40s and the answer to both your questions is a resounding no. I went for a pixel 3a to a OnePlus 13 about two years ago and the thing is way too big. Even my work issues iPhone 15 is a bit too big.
The screen real estate is kind of nice, but pocket fit is abysmal.
I was living in texas in the 90s when my parents had my sister and I use these.
Disclaimer: I care a lot about the problems being solved than the nth degree of how.
That said, although we make a ton of use of agentic development at work we're still making the system design and architecture choices by hand.
There are certainly some team members who miss doing things like figuring out how to solve a puzzle, but we've had a ton more time to focus on system stability and performance.
I would argue that there's a third class of engineering: the splashy YOLO. We have one of those. The boss's boss loves the output, but the implemetaions are dog shit. We now have a personal atlassian token committed to the repo and said grand boss isn't technical enough to see why that's an issue.
In a statement, Utah’s attorney general, Derek Brown, said Kalshi had continued to operate in Utah, despite a federal court ruling that Utah’s gambling laws apply to the company.
“Gambling is illegal in Utah, whether you place the bet, run the game, or promote it. Calling it a ‘prediction market’ doesn’t change what it is, and being federally registered doesn’t put a company above the law,” Brown said in a statement.
This is honestly great. Talk about finding out.
As a developer, our executives and stakeholders have really losed focus. It seems like 10-20 years ago we were being asked to solve tightly scoped problems. Now we get massive sprawling edicts, tons of how I want it, and the result is a very unpolished product. No one seems to care about basics or details anymore. This predates our current AI mess and the AI boom has only made things worse.


