HN user

flotzam

1,173 karma
Posts7
Comments211
View on HN

They acknowledge that it's odd, and give this justification:

"Using runtime panics has the nice property that inline assembly in dead code doesn't get in the way of porting software to Fil-C. Also, it's consistent with how Fil-C usually reports errors."

How come this obvious workaround isn't used much more often:

> If the system allows you to pretend that the vacancy is temporary, why doesn’t it allow you to lower rents on the pretense that lower rents are also temporary?

This does happen sometimes: it’s packaged as “incentive offers,” like 50% off the first 12 or 24 months rent, or 6 months without rent, etc, that lower the average rent over the life of the lease without lowering the “list price.” That’s common in residential leases, and I know it happens sometimes in commercial leases, but I don’t know how prevalent it is.

Ok that one looks legit :)

I was thinking more about his experience with e.g. the last one on the page, Roof Garden at The Post Building:

I still don't understand why it's here nor why it's open daily, nor why they insist on Photo ID "and a full written name" before they'll let you up. However I didn't get the chance to test this out yesterday because when I arrived the roof terrace was "closed due to essential maintenance work", inconveniencing probably nobody but myself.

more likely to get planning permission if their new skyscraper included a free public roof terrace

If that's the deal, it's crazy that some of those places are getting away with then discouraging the public from actually going there. Book your visit in advance! Present ID! Photography forbidden! This grumpy security guard will be hovering nearby <3

It's like Nathan For You S03E01 where a store advertises a $1 TV, then tells the drawn in would-be customers to please respect the black tie dress code, crawl through a tiny door, and squeeze past the alligator.

Keep Android Open 3 months ago

They are not affected (except through second order effects, e.g. some FOSS app developers might give up on development)

At the bottom of the page there's a link to the pdfresurrect package, whose description says

"The PDF format allows for previous changes to be retained in a revised version of the document, thereby keeping a running history of revisions to the document.

This tool extracts all previous revisions while also producing a summary of changes between revisions."

It's inherently a loss of privacy that anyone (given that the dataset is now public) can correlate

Dates of birth, Email addresses, Loyalty program details, Names, Phone numbers

"No tags were pushed to AOSP for the July 2025 monthly release of Android. We asked about this on the android-building group but each of our posts was rejected. We emailed people at Google we've previously contacted about mistakes pushing tags but received no response this time."

https://xcancel.com/GrapheneOS/status/1952413110947430786

"July monthly release was not pushed to AOSP and then neither was the August monthly release. September quarterly release hasn't been pushed yet."

https://xcancel.com/GrapheneOS/status/1963812920673861981

The section Benefits (after Introduction) lists 9 reasons why it makes sense. Some of them are about working around a mismatch with existing standards, but not all.

It really is a social anxiety off switch for me (once it fully kicks in after 5+ hours, lasting for about 24 hours before things slowly return to baseline). Alcohol in troubling quantities has that effect to a lesser extent, but of course it's sloppy as hell too and I hate the hangover. Not so with phenibut.

That makes it tempting to use before 7 days have passed just for this one social occasion. Although committing to not do that has flipped the dynamic: Even after enough time has passed I'm reconsidering, is today actually worth using it and being "blocked" for another week during which something more interesting might come up? Trying to make my occasional visit to normie vibe space count, it's kind of nice there.

Malware [c]an persist across reboots regardless of verified boot.

Some can, some can't. Even when it can persist, escalating to root after every reboot may be unreliable or noisy (e.g. 70% chance of success, 30% crash) compared to straight persistence as root without verified boot.

Also, there are devices out there that let you enroll your own keys, like the Google Pixel series.

This still applies to those devices. It's the main reason GrapheneOS (which exclusively runs on Pixels, with the bootloader relocked to a GrapheneOS key) is opposed to building in root access: Verified boot would be "enabled", but effectively bypassed. https://xcancel.com/GrapheneOS/status/1730435135714050560