> An "ohnosecond" is the second after one makes a terrible mistake, such as deleting the wrong file or sending a text message to the wrong person, where the person in question can do nothing but say "oh no". The term is believed to originate from Elizabeth Powell Crowe's 1993 novel, The Electronic Traveler.
Reminds me (and probably a lot of devs) of a time when I deployed something breaking to production many years ago :), of course I didn't know it would break production beforehand. Recently, I accidentally deleted my entire shell history which caused me quite a bit of slowdown for some time. I'm quite used to modifying complicated commands with Ctrl+R and fzf; the deletion of my shell was truly horrifying.
Tom Scott, as usual, has a great video about the onosecond (sic):
Also interesting is this interactive viewer of cloud seeding live in the US: https://chemtrail.app/, although this website seems to be vibe-coded and heavily against cloud seeding: "How can I help stop cloud seeding in my area?" from the FAQs.
This is actually very, very interesting... and some what genius. In the past, I've felt the urge to buy _something_ for that dopamine hit, even if I didn't really need anything.
I've impulsed bought books before (most I do not regret) and some vinyl records (none I regret). I don't impulse buy food though (as the article discusses) - I regret ordering food most of the time as I feel unhealthy afterwards.
This concept may very much be in line what I need for other impulse purchases. Imagine a dopamine-hit amazon-clone which lets you browse, compare, and order the current obsession-of-the-week - saving your bank account in the long run. I may just try making this.
Here's how it works in our group. The professor gives papers to the PhD students or PostDocs, who read the paper completely. I regularly 'sub-review', as it is called, meticulously looking for issues. I have heard that there are professors who review entire papers in 2-3 hours, since they have a lot (10+) of papers per conference to review without any compensation while they have their own research, teaching, and funding to juggle.
It's not a pretty system sometimes.
Edited to add: Conference's also require declaring that there was someone who sub-reviewed the paper. The professor / PI mentions the PhD student's name in the review form of the paper. Of course, the professor also double-checks all the sub-reviews
Uhhh, I don't think Ente is Norwegian? Yeah, they have an office in Norway, but I remember them starting from India --- Ente means 'mine' in Malayalam, a language spoken in Kerala, South India.
> For just over five weeks, from February 7 to March 14, visitors will be allowed to climb the towering 20-foot scaffold inside the castle’s Sala delle Asse to view conservators at work on Leonardo’s mural, after which it will be sealed off again for another 18 months, making this limited public access a rare opportunity to see it up close mid-restoration.
From the last sentence - it's a chance to see it mid-restoration. But will it be publicly accessible after 18 months?
Ah, it initially appeared that the capital I and the lowercase L have identical-looking glyphs. But scrolling down, I see the ss02 and tnum features add noticeable glyphs. Looks like a nice typeface.
As much as I appreciate the tiny serif for lowercase L and numeral 1 to differentiate l I and 1, I am not the biggest fan of the capital I glyph without the horizontal serifs. It's my biggest design gripe with most sans-serif fonts as it makes it FRUSTRATINGLY difficult to differentiate when looking at words by themselves.
Is that lota or Iota? Is that iodestone or lodestone? Both real examples where I fumbled reading them -- once in front of a class :)
This is why my favorite sans-serif typeface has been (and will always be) IBM Plex Sans [1]. It's an open font [2]. I have all my laptops and desktops set to using the IBM Plex typefaces, including browser overrides. If only there were a way to do it system-wide on my Android phone...
I agree with other comments that this research treads a fine, unethical line. Did the authors responsibly disclose this, as is often done in the security research community? I cannot find any mention of it in the paper. The researchers seem to be involved in security-related research (first author is doing a PhD, last author holds a PhD).
At least arxiv could have run the cleaner [1] before the print of this pre-print (lol). If there was no disclosure, then I think this pre-print becomes unethical to put up.
> leading to the identification of nearly 1,200 images containing sensitive metadata. The types of data represented vary significantly. While device information (e.g., the camera used) or software details (such as the exact version of Photoshop) may already raise concerns, in over 600 cases the metadata contained GPS coordinates, potentially revealing the precise location where a photo was taken. In some instances, this could expose a researcher’s home address (when tied to a profile picture) or the location of research facilities (when images capture experimental equipment)
This is a wonderful write-up and a very enjoyable read. Although my knowledge about systems programming on ARM is limited, I know that it isn't easy to read hardware-based time counters; at the very least, it's not as simple as the x86 rdtsc [1]. This is probably why the author writes:
> This code is more complicated than what I expected to see. I was thinking it would just be a simple register read. Instead, it has to write a 1 to the register, and then delay for a while, and then read back the same register. There was also a very noticeable FIXME in the comment for the function, which definitely raised a red flag in my mind.
Regardless, this was a very nice read and I'm glad they got down to the issue and the problem fixed.
> This was in snapshots for more than 2 months, and only spotted one other program depending on the behaviour (and that test program did not observe that it was therefore depending in incorrect behaviour!!)
Fascinating. I wonder what that program is, and why it depends on the NUL character.