Sounds like it may already have been[1].
Edit: might only be a minor API call issue[2]
2,552 karma · joined November 8, 2013
Edit: might only be a minor API call issue[2]
They do this to push Galaxy for convenience I suppose as most are used to clients that handle updates but it can be confusing if some wonder why for instance their offline installer shortcut opened Galaxy instead.
This appears to just be the output of LLMs itself? It credits GPT-5.2 and Gemini 3 exclusively as authors, has a public domain license (appropriate for AI output) and is only several paragraphs in length.
Stenberg has actually written about invalid/wildly overrated vulnerabilities that get assigned CVEs on their blog a few times and those were made by humans. I often get the sense some of these aren't just misguided reporters but deliberate attempts to make mountains out of molehills for reputation reasons. Things like this seem harder to account for as an incentive.
Ie: the much larger percent of users affected by this news would already be more technically savvy and one would assume be less susceptible to known scams.
To your parent point though, sideloading apps per se OTOH is something most Android installs can do without rooting or a replacement OS. Google is already rolling out developer verification requirements for sideloaded apps on GMS Android installs (most devices) to mitigate impact of malicious apps, so there is already action being taken for regular users.
One could imagine other reasons Vietnam may want to dissuade more tech savvy users from running AOSP-based installs (such as GrapheneOS, which is known to be robust against Cellebrite) and using banking is a decent place to start.
4K (Ultra HD) Blu-Ray is likely the last physical home video media generation to be produced. Disney has pulled physical out of the Asian market, Best Buy stopped releasing any physical media beside games, Target stopped selling them beside certain DVDs.
If you want any chance of actually having high quality releases continue it needs to be supported. An issue though is certain less mainstream releases in Ultra HD Blu-Ray can be rather pricey (if they get a release at all). However I still buy those I'm interested in since I don't want lower quality streaming-tier video to be the only option available in the future, apart from concerns about the volatile nature of online-only libraries (various of which have been wholly removed in the past when licensing/ownership changes).
Is there more context to this? I can't see anything preceding it that explains what it's referencing.
While if the endurance testing would exceed 1000 hours an extrapolated approach can be used to stress below the TBW but using accelerated techniques (including capping the max writable blocks to increase wear on the same areas).
Which is less dramatic than the retention values seem at first and than what gets communicated in articles I've seen. Even in the OP's linked article it takes a comment to also highlight this, while the article itself only cites its own articles that contain no outside links or citations.
[1] https://www.jedec.org/sites/default/files/Alvin_Cox%20%5BCom...
So much could be intercepted back then because of this. It wasn't until 2010 that various large services—including Yahoo Mail and Facebook—got a kick in their ass by a whitehat browser plugin that allowed anyone on the same network to trivially hijack session cookies of others, stimulating an adoption of HTTPS[1] during 2011-2012.
By the time the Snowden leaks occurred in 2013 the trend was heading toward encrypted-by-default and governments were having to adapt.
[1] https://threatpost.com/facebook-kills-firesheep-new-secure-b...
It used to be instant, which is something you really notice the difference with when it changes.
Like if a photo of Philippe Petit's WTC wire walking were instead masked and replaced with separately shot towers—it'd represent the event but technically not the actual snapshot in time it occurred, which kind of reduces the connection with the interesting concept at least for me.
There's no cookies disabled error handling on the site, so the page just infinitely reloads in such cases (Cloudflare's check for comparison informs the user cookies are required—even if JS is also disabled).
If you could get a perfect clock several times for the identical prompt in fresh contexts with the same model then it'd be a better comparison. Potentially the ChatGPT site you're using though is doing some adjustments that the API fed version isn't.
> If I had to guess, it’s that some NGO found some UK-based IP addresses which weren’t captured by the block because they weren’t properly geolocated.
Ofcom's clarified contention is that the geoblock is unreliable, while the lawyer seems to be rebutting the original statements that they interpreted Ofcom as claiming no geoblocking was active ('remains accessible to UK users', 'was directly available to people with UK IP addresses (with and without a VPN)').
On Mac it wasn't until the mid-10s that I found a decent player.
The issue is some sites won't display any content without cookies, even if it's unnecessary. The amount of React-using sites that will load the entire page only to a second later to fully blank out since the JS couldn't set local storage does get annoying (and can regularly be worked around by disabling Javascript if not used for anything substantial). A handful like this have appeared just this past week on the HN front page.
- Translation. See: Gizmodo firing its Spanish translation team and switching exclusively to LLMs.
- Editors. See Microsoft replacing their news editors at MSN with LLMs.
- Customer service. Various examples around the world.
- Article graphics for publications. See: The San Francisco Standard (which used it for various articles for a period), Bleepingcomputer.com, Hackaday (selectively, before some pushback).
- Voice acting. The Finals game used synthetic voices for the announcer voices.
This was the primary reason I'd never used Vivaldi browser's long-standing feature of being able to set sites within a side panel, since it ignored addons. Was only last year that was changed to allow addons.
- The requirement, unless I'm mistaken, would tie a real-world identity of the developer to an app, who may wish to keep that separate from a pseudonym they may normally release things with.
- Unwillingness to give Google PII or just not tie a particular pseudonymous identity to that PII on Google.
- It puts absolute control in Google's hands for whether any app is allowed to run on most devices. There may be concerns about the types of decisions that may arise from this, not merely from recognized malware. Certain governments may ask Google to regulate apps allowed on such devices via this approach.
- Once this globally rolls out in 2027 it will mean the audience for apps from devs who don't agree to this will shrink dramatically. Only those presumably with AOSP based custom ROMs will be able to use those apps which may have a knock-on effect for dev motivation.
Being able to insert self-interjections and such with the correct character would undoubtedly be more widespread if it were more accessible to insert for most.
Or in the late 90s when there was a commercial program that allowed OS 9 to show real-time window previews while dragging rather than merely showing the window border outline.
It's true though that aggressive denoising gives things an artificially generated look since both processes use denoising heavily.
Perhaps this was done to optimize video encoding, since the less noise/surface detail there is the easier it is to compress.
- The thread by the Chromium dev proposed what was originally a 1MB minified polyfill for the Javascript only XSLT calls that in just the last few days has grown to 3MB minified. XSLT was beneficial in the browser because it was native, while a 3MB polyfill is a rather big ask to suggest as a per-site replacement for anything meant to be snappy on slower connections.
- It seems from various mentions the catalysts for this to surface now were the sole maintainer for the XSLT library used in Chromium expressed having trouble maintaining it some months back and left it to a different sole maintainer, along with a recently disclosed vulnerability in that particular library. Firefox OTOH is said to use a different XSLT library.
- Chromium team routinely awards vulnerability discovery bounties in the tens to hundreds of thousands of dollars. Just the other week they awarded $250k to an author who discovered a tricky Chromium exploit. I'd be curious if they've funded development of the XSLT library they use in the past as it seems like they'd rather just be rid of it.
- Within days of posting the open question to the working group and a week prior to the PR of the spec removal a Chromium ticket by the author set milestones for XSLT removal in Chromium. It seems it's less a tentative proposal and more leading by example.