Hacker Newsnew | past | comments | ask | show | jobs | submit | thaeli's commentslogin

I'm the same way. The scanlined, subpixeled versions just look terrible to me.


FPGA based devices that can do this, and quite well, do exist, they're just expensive. The RetroTINK-4k Pro is the top of the line as of this writing but it's a $750 converter.


Emissions related components work very similarly, replace the software and it’s presumed to be a defeat device unless proved otherwise.


For emissions related components, EPA rules do kick in though. While the current administration appears to have paused enforcement, their position for many years has been that running anything except factory approved firmware on an ECU or other emissions related computer constitutes a “defeat device” and is illegal for an on road vehicle subject to emissions controls. (Granted, in practice 99% of the reason anyone installs new firmware on their ECU, or switches to an aftermarket ECU, is for a “tune” that does affect emissions. I’m sure there is some edge case exception, but it’s very rare in on road engines.)

The alternative, and there are a very few tunes that have done this, is to prove to regulators that the tune does not negatively affect emissions in any way. In practice this is done by getting a CARB exception since they’re the ones actually checking for tunes.


Well, many areas have banned app-only payment requirements (along with card-only) so it’s possible we’ll get some mandated alternatives.


Ironically, this check would be a pretty good use for a LLM.


Are there any additional mitigations folks are using for this? This issue is the only reason we can’t turn classic PATs off entirely.

Short lifetime mandatory reauth to enterprise SSO seems to be the best available, but it’s inconvenient for the single Classic PAT we actually need.


Maybe:

- create a GitHub App or something that can generate transient tokens

- implement some CLI that generates a token

- login with that token

- push

See e.g: https://medium.com/@tiwari09abhi/github-app-token-authorizat... https://martin.baillie.id/wrote/ephemeral-github-tokens-via-...

But I'm not even sure because GH auth system is all over the place and downright nuts in some places...

e.g a fine grained token with repo access can't curl a tarball with the usual URL, it has to use the /api which makes tooling that constructs URLs from repo names and versions break with no recourse as soon as you disable classic PATs


Yeah, interested to compare this with optimized and properly cached GitHub Hosted Runner builds.


The biggest problem with SE for me, and this is related to the culture issues you're talking about, is that the site has no good way of deprecating "formerly correct" answers. Even if a better, more correct answer is posted later, the reputation system has a huge incumbency bias in favor of older answers that have accumulated upvotes by being the best available answer at the time.

Their knowledge repository is slowly rotting under the weight of having to ask every time "okay, is this correct-sounding, highly upvoted answer actually (still) correct, or is it 10 years out of date?"


There was a common scam back then of sending cheap goods to someone, then billing them a high price, when they didn't order anything to begin with.


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

Search: