You're approaching the turbaconepicentipede
For Valve, this is actually a more open way than they have historically done. Typically Valve publicly gives very little to no information on a project until it's done or almost done.
Couldn't get the solution page working on mobile (none of the buttons seemed to do anything); but my guess is it would be {1: []} due to |= silently using __or__ and an assignment, meaning b now holds a new reference
Natural Selection 2 is kind of like that
Before I got laid off, I was told by my manager of the company I was contracted to that people higher than him were wondering why I hadn't installed the copilot extension in vscode; he strongly recommended I do so. So I did install it. I then proceeded to immediately set the ignored file types to "*" (which, for those who might not know, is shorthand for "everything".) I didn't hear anything about it afterwards.
Reminds me of tangrams
I used to contract with a company where it was almost ubiquitous for someone to start a text-based conversation with the entire message: "Hey..." — ellipses and everything. It was bad enough that other members of my company that were contracted to the same contract would jokingly add ellipses to random things when messaging each other.
Roughly speaking, apps hosted on the internet can be divided into 2 parts: the frontend and the backend. The backend is the server that provides access to any of the data associated with the app, as well as handling any operations a user might request; this is typically done through sending specifically formatted data to specific URLs on the server. The job of the frontend is to make it more natural for a human to access the data and available operations.
A frontend can be many things; the most common, however, are webpages and apps. In the case of lemmy, there is a webpage frontend that comes default. There is also a popular third-party webpage frontend called Tesseract.
A few weeks ago, after updating the version of Tesseract they were using, the db0 instance noticed a large number of errors. In the end, they went through the code of Tesseract — which is publicly available on github — and found that it would silently reach out to a Tesseract server (importantly this is not the backend that whomever installed Tesseract was trying to communicate with), download a filter list, and silently apply it while disguising filtering any post you tried to access as an error.
The filter list was very opinionated, and often felt arbitrary; and due to the fact it was downloaded from the internet, it could be updated at any time without notice. Additionally, any of the options Tesseract provided around filtering had no effect on the secret filtering.
Because the code is publicly available, the instance owners forked it (made their own copy, with some ability to keep getting updates from the original source) to remove the secret filtering.
It's rounded to the nearest multiple of 10; it could be up to 5 (exclusively), and could still be listed as 0. It's why so many lower-calorie products are listed with a zero-calorie serving size in the US. I'm not sure about the specifics of regulations — if any exist — on selecting serving sizes; this particular example feels a little fishy to me.
Pretty good video on the topic, but it mostly just says what other commenters have said
It's not so rare now; but on the second day Silksong was out, I got the achievement for defeating Phantom when it was still 0.1%
Tesseract was an alternative frontend instances could host. Despite having configuration options for filtering or the lack thereof, Tesseract would silently both download and enforce a custom filter; this hidden filter could not be overridden by any custom configuration. The hidden filter included regex to block keywords, users, and instances, showing a generic error about anything filtered as being "incompatible with Tesseract".
view more:
next ›