Funny enough, if it is an API problem, then this is one of the scenarios that a scrapper could easily solve the issue and grant accurate results again. A playwright script written by ChatGTP could do it.

I read reddit with a client that uses a scrapper now. The fuck is reddit gonna do, block Chromium? They said they wanted to stop this, well, congrats, they started it instead.

I found that the best approach is to just have the link in the sidebar. This was how several communities first started introducing discords when it was basically an unknown piece of software. It became normalized without anyone noticing when.

Yeah, people think tracking you for ads will dissuade anyone? Like, Instagram has a content to ad ratio of 33%, and people give zero fucks.

I don’t think people will ever leave, and I don’t think we should want them to leave either. We can build better, smaller platforms much more easily than we can’t fix the world’s attitude and consumption trends towards the large ones.

A lot of people’s approach to social media is

• login an absolute total of times equal to one, on an app, and never again, that session better last

• do zero content curation, what comes is what you eat

• mostly scroll past shit, don’t interact, don’t produce

• maybe click on a navigation link once or twice per month

So of course they don’t know there’s porn. They’re basically only seeing their feed (which is a clone of /r/popular, so a bunch of clones of /r/funny and ragebait) and the default subs, which doesn’t have porn by default ever since reddit removed its ability to show up on default feeds.

This counts as discussion of self-hosting.

This post got the issue exactly. To use either React or Vue, the first thing you (should) learn from them is about the render mechanisms, which are introduced under the concept of component lifecycles, which only exist because both render things using a Virtual DOM. This is NOT hard, not even close, but it’s also non-trivial and it’s not immediately learnable with just hands-on code experience. It’s also boring to go through it first, so “first thing” has a ton of quotation marks most of the ways you learn it. It’s the kind of stuff that explains why the code is the way it is, and it makes sense of the thing, but can be new and weird.

I think a better way to relate to the issue is to ask people to recall how they learned git, specially those who tried to learn by doing. I’ve known SVN before I learned git, so when I had to sit down and actually understand it, some of the concepts were transferrable. But I’ve seen many, many people try to learn it and completely fumble to understand what the hell they were doing until they were presented with some visual representation such as https://user-images.githubusercontent.com/1256329/117236177-33599100-adf6-11eb-967c-5ef7898b55dc.png A diagram such as that is basically a shorthand to learning the mechanics of git, a sense-maker.

The problem with some of the comments here is that even “properly” written React CAN hit a performance bump, and optimization is a rather rare skill no matter the programming context (kinda due to little time given to it, so everyone is out of practice).

But I don’t know which ones are the ones talking about that, and which ones are just people annoyed at anything Node in general.

If there’s a parent component that has some data that it expects to always receive from its children, then that data should be in the parent’s state and the children should receive it and maybe some relevant methods as props. Even if it’s an unknown number of children. Don’t muck with useContext for basic inheritance stuff, you’ll mess with the render cycle for no good reason.

Now, if we’re talking about a very distant “top” component, that’s fine, it’s what it was made for. Although many people end up using stores if it’s some data with broad impact (like user data)

They also seem to want to replace moderators with AI and even bought a company that does so. Weird, and probably easy to abuse. Wouldn’t trust.