thrdbndndn
My current Android phone (Pixel 7) has both Face Unlock and an on-screen fingerprint scanner. My previous phone (a OnePlus) had Face Unlock along with a rear-mounted fingerprint reader, which was even better.
Unlocking a phone has never felt as effortless on my iPhones; after all these years, it continues to be a nuisance. Face ID is fine, but you have to hold the phone right in front of your face (and its angle sensitivity is far less forgiving than on my Android phones, where it recognizes you even at an angle--unlike the iPhone, where you practically have to hold it parallel to your face).
Plus, there are countless situations where you cannot or do not want to pick up your phone from a table just to align it with your face. In those cases, I am forced to type in my passcode, whereas an on-screen fingerprint scanner would be a billion times more convenient.
I am mostly baffled that such a "solved," trivial problem in the Android ecosystem continues to be a topic or a matter of "choice" on iPhones.
It's just that I no longer really consider myself a programming hobbyist, because what I'm doing now doesn't really feel like programming anymore. I'm mostly just talking to an AI.
It's kind of like if I were into crocheting. A big part of the fun is the repetitive process of actually making something by hand. If I suddenly had a magic machine that could produce whatever I wanted in seconds, I'd obviously be a lot more productive, but I wouldn't really call myself a crocheter anymore.
For tomatoes, interestingly, it has two common names that follow this pattern: 西紅柿, literally translated as "Western Red Persimmon", and 番茄, literally translated as "Foreign Eggplant".
Other produce examples include 番薯 (Foreign Yam) for sweet potato, 西瓜 (Western Melon) for watermelon, 洋蔥 (Foreign Onion) for bulb onion etc.
It still uses 3.6 Flash for example.
Even when you have the MS Office suite installed, it doesn't really provide a good interface for LLMs or automation, so AI tools don't really use it.
For example, on your website, any chart or plot involving horizontal arrows breaks down because the assigned font-family (`ui-monospace, SFMono-Regular, Menlo, Consolas, monospace`, which ends up as Consolas on my machine) has no such glyph. Thus, it falls back to Segoe UI Symbol, which does not have the same fixed width (or is not fixed-width at all) as other characters: https://i.imgur.com/d2DPGHE.png
Props to Mullvad, but it's not like they're unique in this regard.
During COVID, lots of live shows (concerts, etc.) in Japan moved to streaming (and most of them stuck, so thanks to that, lots of large concerts today have real-time streaming, which is great for foreign fans).
Out of 10+ platforms, more than half have vulnerabilities that allow you to access the content freely (sometimes including the rehearsals, because they are also streamed internally), and on a handful, you can access the admin panel and, as the author said, stream whatever you want.
Most of them have been patched over the years (some are just the byproduct of them changing the backend/SaaS provider, though), but there remain some major providers where you can get content for free.
I find it hard to believe that anyone, no matter how dense, could come to this conclusion after this whole saga.
Also, Google Search's AI answer doesn't prevent the actual search results from still showing below; so if I later realize I need those (search results) instead, they're already there.
Also, I use browsers all the time, so typing things into the location bar is quicker than deliberately opening the Gemini app/website or whatever.
I value one fewer click/action a lot when such an action will be performed hundreds of times a day.
The author said:
You cannot just use the shortcut trick to install the evil extension directly because of new publisher trust system;
You can bypass this by using local workspace extensions which has no publisher screening, but CSP blocks it;
The solution seems to be that installing a local workspace extension which binds a shortcut of 'install extension without checking publisher'.
So I assume it means:
1. you need two extensions, 1st one is local and only for the keybinding, and 2nd one is the 'real' evil one and it doesn't need to (actually can't, because of CSP) be local anymore?
2. the CSP only prevents the JS in local extension but nothing about its package.json (or the ability to add shortcuts), right?
It's one of the few AI features, despite still being shoved in my face, that I actually find useful.
With that said, the worst thing is how search results have degraded significantly since the AI years, even before they added the actual "AI mode."
Google now (and quite a few search features on other services, e.g., Twitter) often returns results that have ZERO relationship to the search keywords I gave -- like an entirely different person when searching for a person's name, which I think should never happen and did not happen when search was still based on a "rigid" algorithm of indexed content. So, I can only assume it's because they have some AI thingy along the process.
My account really isn't that important but still makes my blood boil at the time.
1. OrcaSlicer: so it's a fork of Bambu's official client, Bambu Studio - but it apparently still goes through Bambu's servers for printing? How exactly does that work? Does it also "impersonate" the User-Agent, and Bambu was okay with that?
2. OrcaSlicer-bambulab: if the goal of this fork-of-a-fork is to bypass Bambu's cloud servers, why would it still need to "impersonate" the UA and communicate with Bambu's servers (as Bambu claimed)? Wouldn't the whole point be to avoid doing that in the first place?
Does it effectively bypass regional restrictions for you, so you can use something like the Claude API from unsupported regions such as Hong Kong, or does it still enforce the official providers' geo-restrictions?
Whenever I opened a N++ window in a remote desktop session and leave it open, and then use the same computer in-person, the whole UI of that window becomes a blurry mess and the boundary of the window is off (as in, if you maximize the window, moving the cursor to the top-right will actually not land on X.), which I assume it because of changing resolution/scaling between remote and in-person use.
The clue is already in the article itself. The author notes that "part of the jump at least appears to be explained by Valve correcting again the Steam China numbers." If you actually think about what that implies, it raises more questions than answers. A 31.85% monthly drop is obviously not organic, so yes, it makes sense to call it a "correction." But then why was the previous month's data so far off in the first place? Is there something fundamentally flawed in the survey methodology, like sampling bias, non-uniform distribution, regional skew, or something else?
And if this kind of correction happens this month, what's stopping it from happening in previous months? The reality is: it does happen all the time. You can usually spot at least one clearly unrealistic data point in almost every release.
At that point, it's hard to argue there's any real value in trying to analyze these results in a rigorous way.
But English is not my first language so please correct me if I'm wrong.
https://trustcompliance.xyz/_next/static/chunks/17psh0.nytnh...: 404 Not Found