Yeah, I get shit occasionally in random places for using bigger words when they actually would take multiple sentences to replace.
But there are a fucking lot of people who use big (or obscure) words purely as a kind of signaling that they're smart, rather than for communication. And it's usually really obvious to people who have better vocabularies (or better understanding of the jargon in a specific field) that they don't know what they're doing.
If after looking up a word, the rationale for the word choice doesn't become understandable on at least some level, it's probably nonsense. (There are some super smart people who just don't know how to communicate though and think the word's as simple to everyone else as to them.)
I wonder if PS3 is recent enough that better practices around source code were there. You'd have a lot better chance of making first party games (the ones that leveraged the hardware the best for the most part, and the ones you have less licensing issues with) run well if you could recompile them instead of trying to translate code heavily optimized for that architecture.
That was how the put them in buckets.
But I think it's at least as likely as not that whoever wrote that rule chose those buckets to be "unclean" because people got more sick more often. "I got sick once after eating it" is still one of the biggest reasons some people don't like seafood. Your brain is very good at turning single bad events into "don't touch this" if there isn't a body of safe interactions to fall back to.
Cloudflare's (pretty good IMO) response was pretty indicative of how bad this was. It sounded a lot to me (without that low level of familiarity of exactly everything they offer) like they specifically built some new tooling just to handle this issue at scale. They definitely said that changing links on pages (without an opt in for free users, who generally are less advanced/serious) is not something that they want to do, which is good, but I do think this specific scenario justified defaulting to enabled for customers who aren't paying for the service.
Was that not kind of known at the time? Common knowledge isn't the right phrase, because AMD and especially AMD's financial situation are pretty unknown to most people, but I definitely had a level of understanding that AMD was in rough shape financially and that Sony's big commitment to guaranteed volume was a pretty big deal for them.
Such source code isn't possible with the general audience service they offer, even if being open source were a requirement for credibility in any way.
You're comparing them to a company with a long history of actively hostile behavior despite the fact that there's never been a single hint of anything resembling hostile behavior from them, they operate from a country with meaningful privacy protections and only surrender data when compelled by their own courts (who only do so in circumstances that actually warrant it), and haven't actually given up information that's useful when required to because they don't have it.
I'll tell you what. When proton ships a product that takes a screenshot of my desktop every 5 seconds and stores it in an unsecured DB any user on my computer can access, we'll call them even.
Certain loans and contracts can prevent you from being able to sell something without the lien being lifted.
For example, if you have a mortgage on a house, or in some cases if you're paying a contractor to do renovations, you can't just sell the house out from underneath them and run with the cash. Someone "buying" shit with a lien on it could outright lose it in some circumstances (though it would be pretty hard to get there for land because the process is so protracted).
Not for the battery itself.
They are allowed to void your warranty, if, for example, they can show it's delivering out of spec voltage and that damaged the SoC.
To be fair, I absolutely respect keeping the development focused. Feature creep keeps projects from getting core shit done properly.
No, it isn't even a little hard. It's super simple pre-parsing of the input that can trivially be done client side before the query even touches their server. Advanced users who use those tools are perfectly capable of taking the extra step to indicate to the engine that they're doing a real search, and the worst case is still far less intensive per search than any of the LLM nonsense they added to every search and is almost never useful in any way.
They choose not to. It's exactly that simple.
Here's the thing though. You absolutely could still use operators reasonably well even if the results are fuzzier.
You just use them to control how you leverage the algorithm. AND feeds the algorithm the two sides and filters to results that appear on both. OR joins the two result sets. "Filetype" filters the result set for results that are the relevant file type. Etc.
If they're not that common they're not going to have meaningful costs, especially when most power users don't use them for most of their searches.
Pixelfed supports tags, so even if the official team didn't want to do that, it should be possible to make an alternate front end with different tools to allow you to categorize pictures in other ways without having to interfere with the actual mechanisms/structures storing pictures.
It would also be perfectly possible to branch further from Pixelfed, but still keep compatibility federation-wise to leverage the social stuff. This would, in theory, allow you to focus more on the portfolio aspect on your own site, while still also having the social feed portions for people to follow your work in real time. It might be easier to implement something like requiring moderator review before a comment on a picture displays with a harder fork.
That's all way past the scope of what I'd have time for, though. I'm more likely to make something simpler from scratch that fits my own criteria.
This means delisted, not "you lose it", right?
So what I mean is that, to me, a real gallery type site would allow you to do things like filter down by tags and explore specific types of posts by an artist that catches your attention, with combinations of filters, etc. (This would obviously depend on how they used tagging as well.) pixelfed is also built around adding pictures as posts.
There are third party clients that can present information different ways, but the actual website is how you'd generally expose people to your content (especially because it's not something massively popular like instagram). It also, while good at what it is, just doesn't provide the kind of control over structure and organization that I personally would prefer to share my pictures with, which is why I haven't managed to bring myself to add my pictures in bulk there.
But like I said, it's good at what it is and may fit his needs better than mine, so it's worth a good look.
That and an API (both things that there are search results implying they're on the roadmap at some point) and my use would go way up I think.
It's definitely not why I subscribed, but I'd definitely be all for options to use as many productivity tools as part of my subscription as possible.
It would be nice if it (at least optionally) was available separated into its own app at some point.
Are they actually suggesting you smoke 5 cigs over the course of a meal?
Even for hardcore smokers that'a wild.
There's busy and there's "checkout lines literally to the back of the store"