floatingatoll

Years and years ago, I took a photo set of the Santa Cruz boardwalk and all of its beautifully painted buildings and rides, in the middle of January when it was completely and utterly devoid of people. I think I encountered one person the entire visit. I was thrilled because it let me add a second album to my collection of “places that are gorgeous and deserve photographs taken of them without all those annoying people in the way”, and I celebrated the reactions from people. Which were, more or less, that is was incredibly weird to see it portrayed in perfectly normal lighting and color and tone, but missing the one thing that everyone takes for granted: passersby.

Anyways, I reawoke this old dead account (I have since changed names everywhere, here too) so I can link the album and talk about it. Not because I care about appreciation of my photos, but because as an early adopter of the trend, I found it was possible to create the eeriness of today’s ’liminal spaces’ without the ‘lifeless’ characteristics of the Backrooms, House of Leaves, an so on. It’s a lot easier to create that feeling with decay, with monotonality, with cookie-cutter cubicle mazes; and, the theory tends to connect with people more readily as plausible if you include ‘rotted by time and age’ to justify the emptiness as Horizon Zero Dawn and Last of Is both lovingly demonstrated.

But at the core of all of this modern liminal, is portraying human-dense spaces as human-zero, and then confronting the eternal question that haunts humanity: “What happens in the dark forest when no humans are observing?” Whether it’s a cubicle maze or a carnival ride, as the world grows more and more crowded and lonely, it’s no wonder that we want to spy on our busiest spaces after we’ve all gone home for the day. What do they get up to? Where did all the people go? Is this merely a painting of a screaming person on a wall, or is this space empty because they were consumed?

https://www.flickr.com/photos/floatingatoll/albums/721576328...

Thank you for doing so; it led me to see this post, and I appreciate that. I’ll vouch next time if I see it go back to [dead].

Well, I’m glad my question helped you uncover the root cause, in any case.

If Tesla said “working as designed”, then that would definitively confirm that it’s not a bug. Apple has said “working as designed, not a bug” about the most common feature requests (such as “uBlock support” and all the underlying capabilities to deliver that), leaving no uncertainty about them. So I do appreciate your point in the generic “any” case, certainly, but that uncertainty can easily be voided in specific cases — yet we’re ignoring that when it occurs. (I assume this is because framing feature requests as bugs is a common persuasion tactic, as any software maintainer would confirm, but I don’t have any certainty on that view yet.)

It could be considered such, if you file a lawsuit. No one else seems to be, so until it reaches a judge, I don’t know if you’ll see any response.

Bungie, another tech company, has been making this exact request of its community for years now, and their community has for years now found every excuse under the sun to ignore it. Bungie asks “tell us what’s broken, tell us what feels wrong”, and their community responds instead “recurring feature request X, cynical dismissal of intentions”, and then complains that bugs aren’t getting fixed in Bungie’s products. This self-fulfilling prophecy of refusal, complaint, and outrage repeats on an annual cycle, and yet these users continue to ignore pleas for useful feedback.

As of when I posted this comment, most of HN’s discussion of this post is a stellar example of this Internet forum social behavior. Safari asks “tell us what’s buggy and broken, not about recurring feature requests”, and this community is responding with “recurring feature request X, cynical dismissal of intentions”. There are three or four actual real bug reports in this discussion, but they’re drowned out by the non-curious ‘feature’ and ‘cynical’ repetition.

I’m kind of disappointed that they got a hundred plus viable bug reports on Twitter, but only a couple from HN. Given how much so many of us sneer at Twitter, it’s upsetting to see Twitter dramatically outshine us technically. We’re Hacker News, this ought to be a piece of cake.

For example: I wish that Elon Musk wasn’t prideful and troll-y online (these are feature requests that his personality team has refused us), but if he asked me to name a bug in Tesla’s cars that he isn’t aware of, I’d point out that Tesla cars allow you to drive at unsafe speeds when the fog lights are turned on, which is wasting untold megawatts of Supercharger time per year because drivers either don’t know that fog lights aren’t effective above a certain speed and because there’s no chime or automatic-off setting to prevent energy waste. Yes, Elon’s a jerk, and yes, I have feature requests and cynicism about that — but I’d leap for the opportunity to even have a chance at posting one paragraph that cuts all Teslas’ watts per mile by any amount at all. I wish others here found that as rewarding as I do.

Have you filed this bug or reported it to the requested Twitter thread? If anything else, a link to your HN comment posted to them would be enough — and then they’d realize there’s bugs here to find.

In the Safari menu, there may be a Feedback option that lets you report the broken site issue to them directly, without having to use Twitter. I’m not sure if it’s a developer thing or not, but if it’s not there, I imagine it’s present in the latest tech preview build.

That’s a bug worth reporting to them on Twitter! Which dates, incidentally?

Those are design decisions that result in missing functionality, not unintentional defects (“bugs”) in shipping functionality.

I'm not restricting my considerations to "the technology that is implemented and available to Tor users today", given that what's available neither meets the needs of sites, nor the needs of users. If you think that the idea is inappropriate, please state so and make your case for why you believe in your viewpoint. If you think that the idea is impossible, please note why you believe that — and then consider the idea as if it were possible.

That would also remove essentially all potential for attacking workers. I like it far better than my idea. Good call.

Reputation is a feature of identity. Tor users are, by definition and intent, unidentifiable. Opting out of identification naturally opts one out of reputation, as is the case in reality as well — for example, Anonymous using Guy Fawkes masks to prevent reputation from being associated with their citizenship identity.

I don’t understand why Tor users would be interested in reputation at all, given the implicit identification it requires.

That’s all plausible sounding, but no one’s connected the dots and done it yet. We’re still at “step 2: ???”.

Not out of spite, but to protect the workers as they remove the trucks, which the article cited as a specific concern. It will have obvious ramifications in decreased value of the truck, but that’s an expected side effect of deploying it as a paramilitary blockade in a large city anyways.

archive.is requires captchas for iCloud Relay users as well as blocking Cloudflare DNS users, so I wouldn’t consider them to be a Tor-specific example.

Would a plasma cutter be able to permanently destroy the engines in each truck rapidly beyond repairability, so that they’re “disarmed” and can be relocated safely without malicious driver interference? I assume these are going to be taken out by demolition crane anyways, and it would provide a simple and immediate on-site tool to turn them into worthless scrap metal.

Not deanonymise, no.

Come up with a way for siteops to block someone and all their sockpuppet accounts, without knowing the underlying identity, and you’ll become a billionaire.

Without that, the only option we have today is deanonymization, which is a terrible option. We ought to do better.

There’s many debit card “send to friend” apps that fill this space, including Apple Cash and Square Cash and etc. but your most likely compatibility app is Venmo. I’ve had zero issues with any of the Cash apps I’ve used to date, though.

Tor provides anonymity without accountability; having some doors closed to all Tor users is the price paid for that anonymity. If that price isn’t acceptable, either modify Tor to allow more granular accountability in some privacy-protecting way, or don’t use Tor when accessing services that are closed to it.

You can download a prerelease binary early from FTP, but until they release it, there’s no guarantee you’ll get the same code that’s released.

In what way are any of these jerking the regulators’ chain? You list four facts, and you claim that these four facts are insufficient to regulators. Please provide the remainder of your viewpoint, so that we who don’t understand you yet can have a chance to consider it and be persuaded by it.

For example, here’s a question I can’t answer from this tweet or from this entire HN discussion:

“In what way do each of these four facts conflict with one country’s regulators’ decisions, characteristics, or historical tendencies?”

(However, if your goal is simply to preach to the choir, then your comment is certainly sufficient for that purpose — so long as it’s acceptable that it won’t persuade anyone that doesn’t already agree with whatever viewpoint is left unexplained here.)

Correct, in the 5K case the entire display is rendered at 5K, and ditto 2K etc. (I believe the internal canvas caps at 32K, but I don’t have the tools to find out for sure.)

Whatever-sized display viewports are just crop windows into it, and the crop window in internal canvas terms is scaled as necessary, and then it renders the vector canvas onto the raster viewport.

Good to know the threshold to stay under. Thanks for the heads up.

In macOS, the entire display is rendered at 4K no matter what you pick from the resolution box. Most apps have learned to provide 2x-3x “retina” icons so that their bitmap resources look crisp alongside the system UI resources at user-selected “resolutions”.

The Windows UI scaling slider behaves in exactly the same way, though fewer apps include 2x or 3x bitmap resources.

On the topic of color mixing in realtime, we talked about pigments previously this week:

Rebelle: Experimental online paint software https://news.ycombinator.com/item?id=30191520 (3 days ago, 22 comments)

Only the new Magic Keyboard with the roundrect corners and the Globe key have the new, dust-resilient key switches from the new laptops (which preceded it).

The prior model of Magic Keyboards with the Fn key use older defective dust-vulnerable switches.

Writing a Mac application in GTK is, again, not conducive to the goal of learning to program a new platform. Wrappers such as GTK around native objC, Cocoa, and Swift are a distraction from the main purpose of learning those things.

If Safari didn’t aggressively cache favicons, websites trying to overcome Apple’s objection would immediately start trying to use window.reload() and server-side dynamically generating favicon paths, for random “I made this up before coffee” example, which would burn more battery power on Apple devices for endless page reload events. Caching aggressively makes it a non-starter to try and engineer workarounds, and comes at zero impact to users (who are either accustomed to the old favicon and don’t care about rebranding, or ignoring it).

That would allow websites to override Apple's objection, and therefore they can't allow it, even if it will cause occasional problems for websites that think they can do a total branding pivot including favicon overnight.