It’s likely CentOS 7.9, which was released in Nov. 2020 and shipped with kernel version 3.10.0-1160. It’s not completely ridiculous for a one year old POS systems to have a four year old OS. Design for those systems probably started a few years ago, when CentOS 7.9 was relatively recent. For an embedded system the bias would have been toward an established and mature OS, and CentOS 8.x was likely considered “too new” at the time they were speccing these systems. Remotely upgrading between major releases would not be advisable in an embedded system. The RHEL/CentOS in-place upgrade story is… not great. There was zero support for in-place upgrade until RHEL/CentOS 7, and it’s still considered “at your own risk” (source).

One of my grandfathers worked for a telephone company before he passed. That man was an absolute pack rat, he wouldn’t throw anything away. So naturally he had boxes and boxes of punch cards in this basement. I guess they were being thrown out when his employer upgraded to machines that didn’t need punch cards, so he snagged those to use as note paper. I will say, they were great for taking notes. Nice sturdy card stock, and the perfect dimensions for making a shopping list or the like.

Jesus, what a bunch of needless “security”

I disagree with this part. Ticket theft is an actual issue, there are lots of ways to get a copy of someone else’s barcode and either use it before they do or (more likely) sell it to someone else online. TicketMaster’s marketing is talking up the increased security to distract from their true purpose, which is of course to find more ways to take more money from fans. Of course it’s debatable whether the increased security is worth the decreased convenience for ticketholders. That is the inevitable tension when it comes to security, where any increase in security always incurs at least some cost in terms of convenience.

This is all for personal data mining.

TicketMaster might be selling user data, but I don’t think that’s their main aim. They want control of the resale market so they can take a cut when tickets are resold. Note how they don’t allow direct transfers between two mobile wallets, they only allow transfers using their app. That’s so they can monitor transfers. If they see someone transferring dozens or hundreds of tickets to many other TicketMaster users then that person is likely reselling and they can clamp down on their account. TicketMaster’s true intent is to force all resales onto their ticket marketplace, because that’s where they get to take a cut of resales.

Oh yes, I don’t mean to absolve them of any blame. They treated it as an expensive lesson, which is probably the best way for them to process it.

Also while TicketMaster is going to sell this as being an “enhanced security” thing, it’s pretty obvious that increased security is only a side benefit for them. Their angle in this is getting more control over the tickets they sell. As long as there are many people who want to go than can physically fit in a venue, there will be a reselling market for event tickets. TicketMaster wants to take a cut of these downstream transactions.

While the security of rotating barcodes does hinder outright scams, mobile wallets normally allow wallet users to transfer items like tickets to another user if the ticket issuer allows it. TicketMaster does not allow this for their tickets, of course, because it could allow someone to resell tickets while cutting TicketMaster out of the transaction. Currently TM allows transfers using their app, but I’m sure they monitor usage of the feature and clamp down on anyone transferring many tickets. In other words if you try to resell in bulk without using TicketMaster’s own platform (where they get to take a cut), they drop the hammer on you.

The reason you can’t use screenshots or printouts is because they’re now using rotating barcodes. Much like the rotating codes in an authenticator app, the number values behind the barcode are changing on some regular cadence. Only the most recent barcode value is considered valid.

The only other option is to use a mobile wallet, but that prevents me from sending my friends their tickets, since I purchased them all together.

Some ticket sellers allow you to transfer tickets from one wallet to another wallet, but of course TicketMaster isn’t one of them because they’re fucking TicketMaster. What TicketMaster does allow is transfers from one TicketMaster account to another. Of course then everyone needs to have a TicketMaster account, needs to have the app, etc. It’s either that or leave all the tickets in your app or wallet and go in together. If you tell the door person “I have the tickets for these X people,” they’ll be able to handle that.

Yes because the security of barcodes and screenshotted tickets were such a huge problem before.

I think what you just described is actually a problem. Friends of my parents were visiting somewhere, bought tickets to a show from a reseller, met up with the seller (normal looking guy, no red flags, gave some plausible story why he was selling) and paid cash for printed out tickets with barcodes. Printouts looked legit, dates on the printouts were correct, etc. Went to the doors, tried to scan their tickets, got told that unfortunately they’d just been scammed. The impression they get from the box office worker is that this sort of bad news is something they’ve had to deliver frequently. Anecdotal, but I doubt those friends of my parents were the only ones to get scammed in this way. TicketMaster still sucks as an organization but the extra security of rotating barcodes does serve a legitimate security purpose, just like the rotating security codes generated by an authenticator app.

Airlines have recently been having problems with stowaways using screenshots of boarding pass barcodes or QR codes too. Such stowaways should get caught before departure by passenger headcounts or boarding ID checks, but clearly there are gaps or breakdowns in these procedures because some of these stowaways are getting caught at the destination. Others may have successfully flown for free. If it keeps happening I bet we’ll see rotating barcodes come to mobile boarding passes too, if that hasn’t already happened.

Hardly the first time. I’d argue the US made the same mistake in Afghanistan in 2003, diverting resources to Iraq because Bush Jr. had such a hard-on for Saddam.

I’m sure there would be a way to do this with Debian, but I have to confess I don’t know it. I have successfully done this in the past with Clover Bootloader. You have to enable an NVMe driver, but once that’s done you should see an option to boot from your NVMe device. After you’ve booted from it once, Clover should remember and boot from that device automatically going forward. I used this method for years in a home theatre PC with an old motherboard and an NVMe drive on a PCIe adapter.

Same playbook the IDF ran during the Sabra and Shatila massacre. Cordon off an area and let some militia do the dirty work. Bet they’ll investigate themselves after the fact and conclude they had no “direct responsibility”, just like they did previously.

People here seem partial to Jellyfin

I recently switched to Jellyfin and I’ve been pretty impressed with it. Previously I was using some DLNA server software (not Plex) with my TV’s built-in DLNA client. That worked well for several years but I started having problems with new media items not appearing on the TV, so I decided to try some alternatives. Jellyfin was the first one I tried, and it’s working so well that I haven’t felt compelled to search any further.

the internet seems to feel it doesn’t work smoothly with xbox (buggy app/integration).

Why not try it and see how it works for you? Jellyfin is free and open source, so all it would cost you is a little time.

I have a TCL tv with (with google smart TV software)

Can you install apps from Google Play on this TV? If so, there’s a Jellyfin app for Google TVs. I can’t say how well the Google TV Jellyfin app works as I have an LG TV myself, so currently I’m using the Jellyfin LG TV app.

If you can’t install apps on that TV, does it have a DLNA client built in? Many TVs do, and that’s how I streamed media to my TV for years. On my LG TV the DLNA server shows up as another source when I press the button to bring up the list of inputs. The custom app is definitely a lot more feature-rich, but a DLNA client can be quite functional and Jellyfin can be configured to work as a DLNA server.

After reading the article, I’m confused about how it works. Guinea worms are parasites that you get infected with from bad water sources. Unless you eradicate the source (e.g. the worms themselves), can you really say that you’ve eradicated the disease?

Many diseases can likely never be eradicated because they have a natural reservoir, some wild population of animal species in which the disease normally propagates. A natural reservoir will keep the disease in circulation and reinfection of humans can occur from contact with species in the natural reservoir. Ebola virus is like that, it keeps popping up now and then because it has a natural reservoir (believed to be fruit bats).

Guinea worms isn’t like that, which is part of why it’s a strong candidate for eradication. Its reproductive cycle has a step that primarily goes through people or dogs, neither of which would be considered a natural reservoir:

As such, if we reach a state where there are no infected people or dogs then guinea worm could go extinct. There would be larvae left in the wild at that point, but as long as those larvae don’t infect a suitable host then they never become worms. No new worms means no new larvae, and larvae have a fairly short lifespan so we would only need to maintain that situation for maybe a few years before we could confidently say that guinea worm has been eradicated (i.e. any remaining larvae must be dead by that point).

Containourboros!

You can do this with custom formats. You’d want to create a custom format that gives a score if the file is below a certain size threshold (say 1.5GB per hour), then add minimum custom scores to the release profiles you use (e.g. Bluray 1080p). You can also add custom filters for release groups that prioritise file size. YTS for example keeps their releases as small as possible.

I was actually kind of hoping for the second option, if only so that it would be Oracle footing the legal bill to establish a precedent. That Oracle didn’t choose this option may indicate that Red Hat’s coercive license wrapper (“if you exercise your open source rights to redistribute, we’ll close your account”) is actually an effective and legal end-run around open source licenses. I don’t want that to be the case.

From a practical standpoint, we believe Oracle Linux will remain as compatible as it has always been through release 9.2, but after that, there may be a greater chance for a compatibility issue to arise. If an incompatibility does affect a customer or ISV, Oracle will work to remediate the problem.

This is the part of the post I find most interesting. Looks like Oracle won’t be engaging in whatever workarounds Rocky Linux and AlmaLinux are using to continue operating as downstream distros of RHEL. Instead, if I’m reading this correctly it means Oracle Linux will essentially be forking from RHEL past 9.2. There were essentially three options before Oracle when Red Hat made their license change:

• Pay Red Hat for RHEL licenses. Lol as if, Larry Ellison didn’t become a billionaire by spending money he didn’t need to.
• Use whatever workarounds to remain a downstream distro and pay Red Hat nothing, while using their army of lawyers to fend off any ensuing lawsuits from Red Hat / IBM. It’s not like they couldn’t afford to fight the case after all.
• Fork from Red Hat.

That they’ve chosen the third options is kind of fascinating to me, and to understand why you’d probably need to understand how enterprise database support works. The Oracle databases I see day to day are massive, and they drive practically all of a company’s core operations. Unanticipated downtime is fucking expensive, so these companies are willing to pay a lot for top-tier support (not like I think Oracle Support is actually good, mind you, but that’s a whole other topic). The DBAs running these databases don’t want to deal with any headaches whatsoever, so they’re only going to install Oracle on approved operating systems. They can’t afford to have Oracle say “nope, sorry, unsupported platform” during an outage.

For a couple decades now, the supported Linux platforms for Oracle Database have been RHEL, SLES and Oracle Linux. Obviously Oracle Linux will remain on that list, and I doubt SLES is going anywhere either (it tends to be popular in Europe), but does RHEL drop off the list in future? Does Oracle think they can actually convert RHEL installs to Oracle Linux installs at customer sites? Or does RHEL stay on the list but become the red-headed step-child? Either way, this feels like an attempt by Oracle to erode the value of Red Hat’s platform. It’ll be interesting to see how it plays out.

Investment to zero any% speedrun.

Slack DM, three minutes after I pick up an issue.

“You have an issue in the sprint without any story points. Why doesn’t it have any story points? All sprint issues must be pointed.”

Well fuck, Janice, I don’t know. All I’ve done so far is click “Assign to me”. There’s no evaluation yet! I have no idea what the root cause is or how long it will take to fix. Let me cook goddammit.

This isn’t really a good recommendation for OP, since it has fairly hefty modern graphics card requirements, but I’d like to give a shout out to the System Shock remake. It finally launched two weeks ago (I kickstarted way back in 2016 lol) and I’ve been enjoying it. It’s mostly a graphical and controls update that doesn’t otherwise stray far from the original game’s design. Largely the same maze-like space station layout, old-school tile-based inventory management, etc.

System Shock 2 is one of my all-time faves, and I’d love to see Night Dive give it the same treatment.