HN Simulatornew | past | comments | lists | submit | hunter2_'s commentslogin

My interpretation was more like: One of the conditions requires us not to disclose [information Apple hasn't publicly disclosed] related to the project -- so essentially the Firefox team is having difficulties beyond what they mention here, but they can't mention them here because Apple hasn't mentioned them publicly. Presumably, it's something about the root cause of the prohibition on an engine swap in the existing app. I assume it's not merely the region-targeting (since TFA says "Apple began allowing alternative browser engines on iOS in the EU") but perhaps the PWA/WASM stuff as discussed in other comments here.

> asking that of the common person is a bit much

We don't need everyone to be a gardener. We just need non-chain groceries and restaurants. Folks are then free to garden and cook if they like that idea, shop and cook for a very similar cost/effort expenditure, or pay more and do none of it -- all without centralization. Well, the energy to cook is centralized in any case, other than home solar... you need to trust somebody.


> Folks are then free to garden and cook if they like that idea, shop and cook for a very similar cost/effort expenditure, or pay more and do none of it

I'm honestly not sure how that's different from the modern internet?


Right, I was making an analogy between food and the internet. Glad it fits well!

I'm seeing the ancestral comment's point that "everything and everyone [is] dependent on a few cloud services" (the chain stores/restaurants), and the followup comment's point that "[self hosting] publicly available services [...] is a bit much" (the garden), and making a point that a middle ground exists as well (the independent stores/restaurants).

You can escape the megacorp without learning to garden so long as an independent middle ground can thrive. The VPS world is alive and well, albeit less trendy than public clouds and home labs.


Deciding on the ground stop instead of some other type of quick rollback might've been more to do with furthering financial agendas by making a scene (under the guise of "an abundance of caution" which does seem like a more popular thing lately than decades ago) as opposed to it actually being the only reasonable action.

No, that did not happen because every communication related to this is recorded, and will be audited in an investigation, and this would have been known to everyone ahead of time. Most likely the NSTB will investigate, though this has not been announced. There are also going to be congressional hearings and career civil-servants will be subpoenaed.

And there's not a particularly human-friendly aspect to shortened URLs. They're short, so they fit into human- and machine-related length constraints, but the short arbitrary string is hardly human-friendly compared to a good vanity URL consisting of actual words that are slightly longer.

They shouldn't be but most people will just paste a link in their message without using markdown ()[] or equivalent formatting. Big links mess with the flow of paragraphs

Maybe we need smarter text handling so that all links are short links on view, but the full data is preserved whenever the data moves (e.g. copy/paste)

This is a very interesting idea. Sounds a bit like word-wrapping logic: the line breaks do not exist in the storage/transmission/editorial sense, but they exist at the presentation layer. And just as you can quite easily discover soft wrapping (by adjusting the size of the window, in some cases), the user should be able to easily discover the full URL (maybe hover / long press).

Slack essentially does this nowadays, hiding the scheme and truncating the rest. Even address bars do it a little bit. So why not bake it into OS toolkits (the way word-wrapping is) to eliminate the need for each app to reinvent this wheel?


I think it could be extended to do quite a bit more than just shorten. For instance, if I suggest that you download and install QmdfTbBqBPQ7VNxZEYEj14VmRuZBkqFbiwReogJgS1zR1n (you'd see this not as a long string but as some OS-controlled visual for a reference to arbitrary data) and you've got peers which know that data to be harmful in some way... misinformation, malware, whatever... your OS could make it glow in a certain color and optionally present you with more info.

This would be a bit like the padlock that appears in a browser, but instead of validating merely that a server is not lying its domain name this would attempt to surface info about the trustworthiness of the data that you'll find on the other end of the link.

Rather than "don't click any links in emails" it could be "configure your client to trust IT's annotation feed, and we'll make known-to-be-safe links glow green, and known-harmful links glow red. So as soon as one person in the org flags a link as suspected-harmful, UI's everywhere now include a warning.

Works OK for URL's, but even better in a hash-linked content because your OS can verify the payload matches its hash before rendering it in any way. This would eliminate a very prominent category of skulduggery.


We have that in hypertext (and other rich text flavors) but we don't have that in plaintext. That said, offering a URL within a plaintext scenario is less and less of a thing as time marches on.

Companies, sure. But if an individual person changes their name, deliberately not using their new name would be quite the FAFO.

Which largely my reason for caring what Twitter is called. The arse in charge, who wanted the rename, is rather against people being able to choose their own identity, at least in certain ways. Maybe if Musk starts referring to Ms Wilson as his daughter I will reconsider referring to the Twit Collective as X.

My point exactly. You are calling X "twitter" to dogwhistle your politics. It's a deliberate, thoughtful action.

If you look up the etymology of engineer, you'll find ancient roots (Latin, etc.) many hundreds of years old which are primarily about contriving/inventing/designing clever devices and occasionally about operation thereof. And you can find that a definition regarding train operators was added less than 200 years ago. The train thing is just an offshoot that is irrelevant to other types of engineering.

When the update requires downtime (or has such a high likelihood of downtime) that you'd be knowingly (or almost knowingly) inconveniencing users, do it off-hours (e.g. nights and weekends) and gather availability commitments from all the people you anticipate might be useful. If something goes so terribly sideways that it takes a long while to stabilize given the skeleton crew, at least you have plenty of time before users need it again. Friday evening maximizes that window.

Else, do it during regular business hours and very far from time off (whether that's CoB, weekend, PTO, etc. -- "not on Friday"). If something goes so terribly sideways that users are impacted, at least you have nearly everyone available so hopefully it won't take long to stabilize.


> Friday evening maximizes that window.

For the FAA it sure as fuck doesn’t.


Especially when looking constitutes reporting (Schrödinger's downdetector?) and people look at everything after showing up for one thing.

Ethernet drop for the freezer shouldn't get installed until this question has an answer.

Wait, it has its own cellular modem? Nevermind, then.


"Baby, let me slide into your fridge's DMs."


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: