nneonneo

39 ms·

451.
by nneonneo 3y ago
Canada has had eTransfer for several years now, which is functionally the same as Zelle (irreversible, instant, free bank-to-bank transfers), but somehow I haven’t heard the same level of complaining about fraud. I wonder why that is?
452.
by nneonneo 3y ago
They aren’t nearly as safe as they could be, and manufacturers have had to be dragged kicking and screaming to implement even basic safety features like seatbelts: some manufacturers even refused on the basis that adding safety features imp
453.
by nneonneo 3y ago
Is Perfect Dark up on https://decomp.me/ ? It'd be fun (even as an academic exercise) to actually get to 100% on the decompilation.
454.
by nneonneo 3y ago
Finished the free play levels (up to 48), and enabled “crazy mode”. No idea what that does, and I couldn’t visually work out what effect it has (maybe the timer is faster?)
455.
by nneonneo 3y ago
Oh wow, this is very cool! The way this works boils down to the following: by default, Git has a heuristic for determining the "context" of a diff hunk by looking for lines that start with certain non-whitespace characters. This c
456.
by nneonneo 3y ago
Yes, macros: https://github.com/hikari-no-yume/touchHLE/blob/trunk/src/ob... .
457.
by nneonneo 3y ago
The protocol does provide for fallback: if the client doesn’t understand the WWW-Authenticate: WebSession header, it can just choose to ignore it and send a request without Authorization, at which point the server can fall back to a traditi
458.
by nneonneo 3y ago
Probably more accurate to say that BB(3, 3) looks hard; that is, it encodes a Collatz-type problem, and many Collatz-type problems are very hard to solve (including, of course, the classic Collatz conjecture). However, this instance might
459.
Show HN: YouTube-DL on iOS(gist.github.com)
2 points by nneonneo 3y ago|0 comments
460.
by nneonneo 3y ago
Wow, I have to say it’s quite funny: https://web.archive.org/web/20120307132029/http://www.ninesy... From the manual ( https://web.archive.org/web/20080119120948/http:/&#x2F
461.
by nneonneo 3y ago
The patch that deletes the offending translation file: https://github.com/canonical/ubuntu-desktop-provision/pull/1... One of the commits that added the offensive language: https://github.com/
462.
by nneonneo 3y ago
Boost.Lambda ( https://www.boost.org/doc/libs/1_62_0/doc/html/lambda.html ) is probably what you want, and even predates the introduction of proper lambdas into C++! Here’s a few simple examples cribb
463.
by nneonneo 3y ago
FWIW, “^@“ is the escape code for an ASCII NUL (just like “^D” is the code for 0x04 “EOT”). Seeing lots of them could mean that you’re printing past the end of a buffer, or printing uninitialized memory.
464.
by nneonneo 3y ago
Developing on Android similarly drives me mad because of the volume of garbage spewed in Logcat. Yes, you can filter, buy if the problem is in an external component you might need to see the full log - and then it's wading through MBs
465.
by nneonneo 3y ago
The recent issue (from the last two years) does not appear to be Teams-related. The Teams thing was from the first wave of emergency call failures, which was traced to a bad interaction between Teams and the Android dialer.
466.
by nneonneo 3y ago
Cool, maybe they can fix emergency calling sometime in that seven year window? https://www.androidauthority.com/psa-google-pixel-911-emerge...
467.
by nneonneo 3y ago
There was a competition held a while back called Decompetition ( https://decompetition.io/ ) in the same spirit: given a bunch of compiled programs, write the source code that compiles to the same (or very close) binary. Most
468.
by nneonneo 3y ago
It’s worth pointing out that the 911 issue cropped up on Pixel 7 phones too, so the issue is not unique to the Pixel 6 line.
469.
by nneonneo 3y ago
When did you have problems dialing 911 with an iPhone? It seems like something worth reporting - feedback to Apple, public posting, etc. Dropped calls etc. do happen for a variety of reasons, but there have been next to no reports of iPhone
470.
by nneonneo 3y ago
And, it’s worth pointing out that the sales volumes of iPhones and just Samsungs (not counting any other brand) are many times that of Pixel, so if there was an issue even nearly as frequent with those phones it would definitely have been n
471.
by nneonneo 3y ago
This article is about an incident from just last month, but the fact that there are 20+ failure reports over just Feb 2022-Jan 2023 ( https://www.reddit.com/r/GooglePixel/comments/y039zn/i_compi... ), acro
472.
by nneonneo 3y ago
For completeness: - "Copy link" on images is now producing an image link that has "ex", "is" and "hm" URL parameters - The parameters can be removed (or altered) without affecting the link's val
473.
by nneonneo 3y ago
There are many, many places where it would be impractical to regenerate and repost links frequently. Plus, regenerating a link would require a Discord API call, and they could easily rate-limit that or add anti-bot features, which would put
474.
by nneonneo 3y ago
Let’s not forget that a decompressor for such a format would necessitate running the entire model, i.e. in this case, a 70B parameter decompressor. It’s perhaps not surprising that you can compress files better when given a (very) large dic
475.
CalcGPT(calcgpt.io)
2 points by nneonneo 3y ago|0 comments
476.
by nneonneo 3y ago
Early returns are very useful, just like break/continue. For example, I find it much easier to write for filename in os.listdir(dirname): if not filename.endswith(".png") and not filename.endswith(".jpg&quo
477.
by nneonneo 3y ago
I think the "errant advice" might originate with languages like C, in which an early return is an easy way to forget crucial deinitialization code, and where "goto"s can always be used to skip to the single exit point wh
478.
by nneonneo 3y ago
Cool! I don't believe I was referencing any specific challenge. We've had a number of challenges throughout the years that have had these issues. The most common culprits are challenges hosted by Asian organizers, as the ping time
479.
by nneonneo 3y ago
Java may be memory safe, but errors in highly expressive functionality like Java serialization and expression parsers have been responsible for some of the most impactful vulnerabilities in recent memory. CVE-2017-5638 was famously exploite
480.
by nneonneo 3y ago
Sadly I imagine this would also block people on poor connections such as cellular, satellite or Tor.

More ›