AmigaOS does indeed enable the extra half line when any visible viewports are interlaced. Fortunately that just works because the individual “non-interlaced” fields are still legible when shifted back and forth by a half line.
Forgot to add this earlier. Later versions of AmigaOS that support non-15kHz rates will promote all screens to the lowest screen mode that can suppprt all visible screen resolutions. So, if you drag a NTSC:High Res Interlaced (640x400@60i) screen down in front of a Multiscan:Productivity (640x400@70p) screen, then the front screen will also display in Prpductivity mode.
It’s worth noting that this is not actually explicit in the standard so much as it is just a natural consequence of not including the half-line. Since the raster is continually moving across and down, including during all retraces (until the actual blanking pulses reset them), the presence of the half-line means that the horizontal retrace doesn’t reset at the end of the half line, it just continues scanning horizontally while the vblank pulse resets the vertical deflection to the top of the screen. Similarly, all scan lines are actually very slightly tilted down on all CRTs unless there is compensation for it. The vertical deflection is consistently moving across the length of the horizontal trace.
Edit: if you have a set that is miscalibrated or worn out, you can end up actually seeing the retrace lines during what should be blanking
We're not talking about DOS here. This is AmigaOS, a fully preemptively multitasked OS from day one. No memory protection, but unless your code is running on bare metal like demos and games, there are other tasks running.
Top parent of this thread is talking about a package for AmigaOS being run on a bespoke emulator (as the Unusable Amiga Emulator of the 90s wasn’t really a thing that could be used for that)
At this point, Flock (and similar services) should be considered agents of the state, given the rates at which police are using them as such.
When is someone gonna spin up a predictive AI that attempts to tell if someone is going to commit a crime, and sells that to PDs, just so we can really dive headfirst into the Minority Report.
Piles of evidence that humans tend to treat AI as infallible, just like the police did here. They didn't use this as a point for further investigation, they saw the match and said "let's go get her" without so much as looking at the damaged vehicle for paint transfer, which should be remedial-level police instruction.
Modern AI was and is a mistake. It's only going to get worst before it gets better.
Unfortunately, our current government in the US is hard AI-pilled (oh, sorry, "super-intelligence-pilled"). They use it every day to present propaganda to the public via social media.
Ban AI use in all branches of government, and in policing. At least until there are ethical standards put in place that are very heavily punished when violated.
Also, state and federal level politicians should be prohibited from using social media in anything other than a purely personal basis without mention of political office or without speaking on the topic of politics. Want to post cool pictures of your family? Go for it. Speaking to your constituency? Must be strongly vetted for ethical violations, and punishable by immediate removal from office and a 10-year blacklist.
The problem is that they're treating the output of the AI algorithm as 100% fact. Countless examples of Flock matching incorrectly or police otherwise using the match found by Flock as "here's who to go arrest" and not "here's a starting point for further investigation".
Partial matches, correct matches but no investigation into things like paint transfer, it's happened way too many times (hint: one is too many times for things that can incarcerate people).
It's like they're speedrunning unworthiness to hold the monopoly on violence. This is how you get riots and revolutions. Sadly, today's Western world is complicit and complacent. Nobody who is pro-surveillance state will change their mind until it affects them or someone close to them.
> The locker fills the screen, hides the cursor, swallows the usual exit keys, and lags the browser, all to manufacture the sense of a broken machine and pressure the person into calling the number on the screen. Nothing on the computer is actually locked, but in the moment it is convincing enough to push people toward the scam.
Tell me again why the browser has to be its own Turing-complete platform? Rather than a document reader as it was designed?
The more things change, the more they stay the same. This is the equivalent of 80s viruses having full control over the machine they run on, without any real mitigation outside of prevention.
Web apps were a mistake. So was always-on connectivity where any given program could connect to remote services in the background.
In fact, allowing computers to completely take over the world to the degree it has today was a mistake, at least as implemented by the tech overlords of the 90s and 2000s that built things to be the way it is now.
Really, this is just the continuing fallout from the dotcom bubble. A few companies vaulted to mega status, the rest died. And those remaining companies have destroyed the world slowly.
JavaScript itself would be fine as long as browsers didn't present certain capabilities to the running script. Modifying the DOM and rearranging elements? Go ham. Intercepting input and hard-forcing viewport sizes? Fuck outta here.
Edit: I've been getting the "slow down" thing on HN for the last couple of weeks after like five or six messages within a half hour. Not connected to HN through any VPN or obfuscation. It's annoying because it seems to take a solid hour or two (haven't measured) to unlock.
When I saw the WebGPU “Deathray” published for macOS browsers earlier this month, my first question was how long until something similar would be used for phishing.
reply