I know tar zxf and xjf off by heart. I probably do 100x as many extracts as creates. Tar is a stupidly antiquated command though.

They have to have a human respond to each and every complaint about that ad. Seems more sensible to automate and flag suspicious ads before the complaints happen.

There are other considerations here though. Google suffers reputational harm if users become victims through their platform. It becomes news, it creates distrust in users, it generates friction with regulators and law enforcement. Users may be trained to be ad averse or install ad blockers. In addition, these ads generate reports which costs time to process even if the complaints are rejected.

At the end of the day these scammers are not high profile advertisers and they’re not valuable. They’re burner accounts that pay cents to deliver their ads. They’re ephemeral, get zapped, reappear and constantly waste time and resources. Given that YouTube can easily transcribe content and watermark it, it makes no sense to me that they wouldn’t put some triggers in, e.g. a new advertiser places an ad that says “Elon Musk”, or “Quantum AI” or other such markers, flag it for review.

I’ve disabled personalised ads on YouTube and I see this sort of shit all the time. I’ve given up reporting them because 90% of the time the report is rejected. I don’t even understand the rationale for rejecting it because it’s an obvious a scam as a scam can be - ai impersonation, fake endorsement, illegal advertising category. It’s a scam YouTube.

I don’t even get why these ads even appear. YouTube has transcription & voice / music recognition capabilities. How hard would it be to flag a suspicious ad and require a human to review it? Or search for duplicates under other burner accounts and zap them at the same time? Or having some kind of randomized audit based on trust where new accounts get reviewed more frequently by experienced reviewers.

Because they are. Groups like PETA, or Just Stop Oil are clowns who hurt their own cause. Performative protesting might win people a participation prize but to everyone else it’s just “look at meeeeee!”. At a certain point it actually becomes toxic to the cause. I know if I wanted to harm environmental campaigning then I’d invent Just Stop Oil.

Meanwhile big business are sending lobbiests in to change politician’s minds, to make arguments that appeal to their rationality, or self-interest. THAT is what environmental campaigners should be doing - lobbying, extoling the benefits of environmental action, changing minds. Getting arrested in front of cameras over and over just becomes pathetic and performative.

No change doesn’t happen by asking nicely, but I think some joined up thinking by these groups would get them further than performative protesting and getting arrested. If you want change then you lobby politicians on the positive benefits of change, and businesses on the potential profits to be had from implementing it.

I think climate activists would just be better off doing what everyone else does - lobbying. Identify politicians who represent areas who would benefit from pollution controls, or green investment or whatever and push the message. Performative acts in front of cameras might feel good but it’s a blunt tool to change policy. Some protestors such as “just stop oil” campaigners are so stupid that they actually help the causes they supposedly oppose.

It doesn’t work like that. UTC goes forward always. Leap seconds are scheduled and known in advance. NTP time services will just smear time advancement a little to account for an additional second. Time never has to go backwards. This is how Google does it.

Leap seconds still make time go forwards, not backwards. NTP clients would also resolve small time discrepancies while still advancing forwards prior to the next time sync.

I didn’t say Unix time, I said UTC. And no it won’t report negative time, not unless somehow the system clock was modified while it was running…

UTC always goes forward regardless of the timezone and local time. That is why you should use it. To take my EPG situation above, I stored program start / end times in UTC so they would render properly even if DST kicked in or not during the middle of the program.

Spotify and other such services almost certainly sound worse because they are compressed. But it’s not really a like for like comparison with vinyl. Spotify is streaming audio for people who want to play music casually in cars, earbuds etc. It offers convenience, not perfect sound fidelity. FLAC / CD on the other hand could be compared to vinyl and would win hands down for better frequency and range. The only reason they wouldn’t is if the CD master sucked and the vinyl master didn’t.

And vinyl is very lossy in its own way. The (digital) master of each side undergoes dynamic range & frequency compression to fit the limitations of the format (e.g. to reduce sibilance, track width). Then the master is cut into a lacquer disc from which a “father” is made, from which “mothers” are made, from which stampers are made and from which the vinyl record is made. So the vinyl in someone’s hand is a copy, of a copy, of a copy, of an altered digital master. The stamper too wears out so if someone is unlucky they get a pressing right the end of its life. And playing the disk can cause wow, flutter, distortion and general wear & tear can cause hiss, pop, dullness and scratches.

So vinyl will never sound better unless it received a better master than other formats.

In the 70s and 80s there were kids toys which played injection moulded plastic discs with a stylus that tracked the groove. I think you might be able to achieve something similar out of a printed record if it was spun fast enough but it wouldn’t sound great.

I had the misfortune to have some PLA snap just before and after the direct drive in my Bambu P1S and it took ages to get it out. I think age and moisture can affect filament, especially it blended with wood dust, sparkles or something which undermines it even further. I’ve resorted to packing my AMS with silica beads to hopefully mitigate for the issue and I threw out the filament that caused the issue. Ironically this is one of the few places a bowden extruder is any benefit - if the filament snaps just push it from behind through a heated nozzle until the blockage clears.

Yes as long as the rules are known, but it’s really just better to do things sanely and leave no margin of doubt.

True but so do most computers. Computers have a database of timezones and time offsets around the world. Depending on the UTC date and time, and your current timezone it will look up what offset to apply to show the local time. The database is very gnarly since rules change over time, e.g. maybe in the 70s some countries had longer DST to counteract oil shortages.

I once developed an electronic program guide for a cable TV company in New Zealand and I’d lose my mind if I had to use timezones. The basic rule of thumb was:

a) Internally you use UTC religiously. UTC is the same everywhere on Earth, time always goes forward, most languages have classes that represent instants, durations etc. In addition you make damned sure your server time is correct and UTC.

b) You only deal with timezones when presenting something to a user or taking input from a user

Prior to that I had worked for a US trading company that set all their servers to EST and was receiving trades through the system which expressed time & date ambiguously. Just had to assume everywhere that EST was the default but it was just dumb programming and I bet to this day every piece of code they develop has time bugs.

I think they need to be super explicit to stop the likes of Tesla weaseling out or doing the bare minimum:

• Wipers, speed settings, auto on/off should be on a stalk for front and rear wipers
• Indicators should be on a stalk with
• Hazard lights must be a physical button
• Horn may be on the wheel or a button
• Lights on/off/full beam/dip/auto must be a dial or a stalk
• Demister / heated window must be physical buttons
• Gears must be a physical rocker, lever or dial

And button / dial etc here means an actual push up/down button not some haptic / touch sensitive shit.

Because at the moment Tesla are basically cheaping out of providing physical controls to save money. It doesn’t matter if someone crashes their car fiddling to set the wiper speed because Tesla saved $20 on a stalk and that’s all that matters.

The EFF has some info about the practice - https://www.eff.org/pages/list-printers-which-do-or-do-not-display-tracking-dots.

I imagine there are ways and means of obfuscating / anonymizing the dots such as blocking the printer from emitting them (e.g. an empty yellow cartridge that the printer perceives as full), modifying the firmware, using a burner printer, or using a mono laser jet.

As a side issue, most modern bank notes have a bunch of yellow circles integrated into the design on each side. They look random but they’re in a recognisable pattern called a constellation that enables devices like copiers / scanners to recognize when people are trying to copy money or other financial instruments like checks.

Rust isn’t really OOP like C#, Java or C++ - it has structs with functions that you could consider an “object” but there is no inheritance. Instead Rust uses traits which are a little bit like interfaces in some languages.

The way the kernel is using Rust at the moment is to produce safe bindings for modules to be written in Rust, i.e. you can create a module in Rust source which will be correctly loaded up, the code is safe by default and will have access to kernel services via bindings. I expect over time that more of the kernel will become Rust, but the biggest impediment right now is Rust relies on LLVM and LLVM only supports a subset of targets that a kernel could potentially support with another compiler like gcc.