• 0 Posts
  • 13 Comments
Joined 5 months ago
cake
Cake day: April 4th, 2026

help-circle
  • Websites have to search for new revenue streams. They don’t just walk into a corner of the internet and think “drat, someone already has a forum for that!” and walk away. They come up with some unique twist people won’t have normally thought of and run with that until it stops working. See this guy’s comment below:

    With reddit they need to be able to show that their advertisers aren’t just serving ads to bots (although we’re seeing ads for bots now apparently). They have to prove a certain number of real human beings saw something thus the login requirement.

    Now, people used old reddit because new reddit sucks. New reddit just shows you the top few posts, and makes you expand replies, thus proving you’re something they can bill for. This also serves the purpose of pushing nuanced, long running discussion down to where people don’t see it. Just look at the cat picture, upvote it, and move on.

    And for the record reddit has been crap for a very long time. At least since whoever that lame ass admin was who went into the backend database and edited someone’s raw post, and if not then, then Victoria getting the axe should’ve been a red flag to everyone that you weren’t a member of reddit…not really. I know there were some local meetups in that timeframe. How awkward do you think the AMA local BBQ was? Do you think reddit cares?



  • Sure.

    For a while now, if you needed the time from your computer, and it was running UNIX or a variant, you’d use something like gettimeofday() (it’s clock_gettime() now) which would hand you seconds since the epoch at midnight January 1, 1970 in UTC and microseconds/nanoseconds depending. You’d take the seconds, wash it through localtime_r to adjust for the local time zone, and you’d have a struct you could feed to strftime() for formatting.

    So my beef with time formats, and what I presume ChickenLadyLovesLife’s beef is, is that when the time format is “wrong” for whatever reason, given the similiarity between the backends of modern time systems, it’s “wrong” for reasons other than technical limitations. You’ve got a count in seconds since the beginning of time, and a function that’s been around for decades that can do whatever stupid stuff you want. Military time, month printed out, day of week printed out, two character years, four character years, seconds, julian day, Doing something silly like day of year, hour of day, and am/pm (“%j %I %p”) is just as easy as something practical like a large fluffy timestamp, or a minimalist four characters military time (“%H%M”). The hard part was getting the time from the GPS or cell phone tower or wherever. The easy part is the time format. Windows also exists, and uses something similar. Modern programming with C++ or Python will have libraries (<chrono> and datetime, respectively) that work the same way, and both those examples use strftime() semantics.

    So, if you’re unhappy with the way your device prints out time, the reason behind it isn’t the clock part of it, it’s the display part. There was some rationale on Android’s behalf for adopting the hour over minutes style, but it wasn’t because their available horizontal character limit dropped from four (five if you count a colon) to two. Maybe they can get more data widgets displayed around the time in a little halo? I don’t know, I don’t use android stuff anywhere. If it was apple I’d assume they did UX testing about half height characters and readability.

    So, now to the “end goal” part of what I wrote before. The hard part is done and a solved problem, and most time formats work fine for what they do. tmux is giving me (“%H:%M %d-%b-%y”) which works fine, and my desktop environment (DE) is using (“%a, %b %d %H:%M”) which is fine. The other DE is using (“%b %d %H:%M”) which is fine. All perfectly usable, all used the three character representation of the month avoiding problems between dd/mm/yy or mm/dd/yy, and all of those are adjustable to an extent with two of the three kicking back to strftime() if I needed it. So what did android get when they paid developers to make the change to hours on top of minutes? Is there a study I missed that of a group of people who’d never seen a clock before and had no concept of time found the “%H\n%M” style more easy to read? If that’s true, then was it worth irritating the subset of people who are going to care about the change to pick up the other group? I personally don’t see a point in paying to make the change unless they’re expecting to make more money from it, which at the core of a lot of things in the world these days. Here’s something that worked fine, but now it’s being changed to work differently but no better.



  • Debian.

    This is the future so Virtual Machines and containers are where most of the stuff will end up anyway. If you need a specific distro it’s minutes away with a VM or container.

    If you think there’s a chance you might want some Redhat cert for a job at some point it might be the time to jump to Rocky, and I’ve never used Proxmox so I can’t comment except to say that if I come into two fairly large computers for self hosting, the first one will get Rocky so I can get much more familiar with it, and the second will get Proxmox.

    It’s all systemd anyway.





  • RHEL9 and forward require v3, and the numpy in pip as of a few versions back uses either v2 or v3 instructions, so v1 is silently broke for certain workloads. FreeBSD works on it just fine as do Debian based distributions as long as you don’t need recent versions of numpy, but there’s no telling what else out there just tries to run and fails with an illegal instruction.