Laxaria

In general the entire series kind of took a nose dive when the focus switched from cooking to how many superpower level absurdist cooking skills can we cram into the story to cook something.

Which is unfortunate, but I think the shifts in the manga over the years really foretold the changing priorities of the creative team (editor included).

As another example, the Path of Exile community moved off onto their own community-run wiki domain, but the Fandom variant (which is woefully out of date) continues to be one of the top results when searching for a PoE wiki page.

In some regards that's inevitable, but it clearly shows what Fandom's priorities are.

Fandom purchasing Gamepedia and moving everything onto Fandom Wikia was so awful. I'm so upset the Dota2 Gamepedia wiki is now on Fandom, and I'm sure many other communities feel that way for their own community run and community led wiki pages.

Not that I was particularly warm about Gamepedia either, but at the bare minimum I didn't feel like the page was all ads and no information. Fandom wikis are explicitly set-up to drive as many eyeballs as possible onto advertising and engagement, and are holding actually relevant information for the visitor as a hostage to get those eyeballs. It's information masquerading as a social media site.

The Runescape community convincing Jagex to cover the hosting costs and moving all their wiki pages to their own set-up has been such a huge boon for their community. It is super unfortunate that for many communities, the community-led wiki pages are a huge trove of information but the companies/games/groups these communities coalesce around have shown little to no interest in merely just financially supporting the endeavor.

TVTropes is what I sink my time in when I want a good laugh and have absolutely no motivation to do anything but doomscroll through text. Pick a favourite series you don't mind spoilers on and read through all the tropes for a good laugh or to reminisce over what was good or bad about the series.

The key difference between manifest V2.0 and V3.0 with regards to uBO is in V2, the extension has direct access to the browser's process in making web requests and can make direct changes to those requests. V3 instead requires the extension to declare a list of urls and the browser will act on the extension's behalf. This is a very simplified explanation that isn't in any meaningful depth and misses a ton of nuance.

The outcome though is V3 makes it significantly more difficult for uBO to achieve its goals for its users. It is a downright and explicit downgrade, and when Chrome fully moves to Manifest V3.0, uBO's ability to serve its core functions will likely be diminished.

You're asking about the same court who found standing for striking down the student debt thing?

in other words, this iteration of SCOTUS finds standing insofar as it fits their political whims regardless of actual legal grounding (unfortunately).

The Osaka sequence overstayed its welcome, more so when it's meant to be an establishing introduction for its characters but not all of them get seen after the sequence ends.

The long panning shots, the stunts, the combat choreography, a lot of that is pretty cool, but visual eye candy is not the only thing that makes a movie and the film falls a bit flat as a result.

Probably not the intended audience for it.

What a thinly veiled way to insinuate that she won't participate in good faith, given that good faith participation intrinsically means recusal.

The "numbers" are called Discriminators and served a variety of purposes:

• Identity wise it meant multiple people could have the same username text. If you wanted to be John, you could be John#6754 and someone else could be John#1298 and both of you could be John! Now there is only one john.
• It provided parity. EVERYONE had it, therefore no one is better or worse than other excluding particular number combinations. If you were John#5363 and hated the discriminator, well everyone else had one, versus someone behind john, and then someone having to be john_87 because there's already a john

You argue that being able to use effectively the same username everywhere is a good thing. The unfortunate reality is the rollout Discord used alongside the limited number of permutations (combinations?) of short usernames makes this impractical. For example, a friend largely goes by a 4-char username, and the switch by Discord means they can't use that 4-char username on Discord anymore. It's easy to say like "well, just add something to the end", but that is exactly what discriminators did.

At the end of the day the benefits weren't as compelling as the losses (it would suck to have one's identity impersonated or username stolen, or now most folks with short usernames have to stop friend requests cause they are getting spammed with them, or the fact these accounts are valuable and can be sold).

It is understandable that some people don't really care about the matter and that's fine, but it doesn't make the frustrations others feel less important.

Right there is inherent inertial momentum with upvotes.

I'm still on the fence, because understandably the potential (and actual) for abuse makes downvotes very unproductive as a feature, but there are also situations where they are very powerful.

It takes significantly more effort to refute a wrong position than it takes to make it. Downvotes serve as an explicit balancing point against that in ways that a well written response does not. Additionally, nested comments usually get less upvotes than their parent comments.

It is what it is I guess.

Reddit doesn't (at least as far as I know) store a history of edits, so what is saved on the database is what your comment literally is. The reason people suggest overwriting comments is because the comment itself has value (for a variety of reasons), so overwriting the comment with something valueless (in the sense that it has no value for Reddit) is better, so the database itself is updated with that valueless comment.

After that whatever you do with the account is up to you.

I in general find lay people have a very weak understanding of how research functions. This is a very generic statement, but everything from IRB processes to how science is reported in manuscripts and everything in between tends to be a quagmire, and this is absolutely with recognition that some of this process is mired in red-tape, bureaucracy, and endless administration.

For example, there's a long-standing idea that IRBs are the gatekeepers of research. In reality, any IRB worth their weight (and really, all of them are for compliance) should be viewed as a research stakeholder. They should be there to make research happen and let scientists do the best research they can with the minimal amount of harm to participants. Sometimes this involves compromises, or finding alternatives that are less harmful, and this is a good thing.

Another common example is scientific studies are frequently criticized about sample sizes. Yes, a lot of research would definitely benefit from better sampling and larger samples, but narrowly focusing on sample sizes misses a lot of the other considerations taken for evaluating statistical power. For example, if one wants to know whether beheading people results in injuries incongruent with life, one doesn't really need a large sample to come to this conclusion because the effect (size) is so large. Of course more numbers help, but past a point more numbers only add to the cost of the research without measurably improving the quality of the statistical inferences made.

In this topic about IRBs, A/B UI/UX testing for the set-up that Reddit did it, and being run out of an university setting? That's hyperbole. I don't like businesses doing aggressive user-focused testing without informing the user, particularly with UI/UX changes I dislike (looking at you too Twitch with your constant layout changes), but at the end of the day these kinds of testing generally don't ever rise up to the threshold needed to be a particularly meaningful blip. Insinuating otherwise vastly mischaracterize how research is done in formal, structured settings.