It started reminding me of the strategy where Google lowered the quality of the search results, forcing users to search several times, and see several times as many ads. And if that worked for Google, how is it not going to work for AI?

Ding ding ding.

Unlike immutable distributions that lock you out of the native package manager

Direct pacman use is blocked. /usr/bin/pacman is a wrapper around pacman-real

Regardless, I do support attempts to make an immutable and declarative Arch distro. An an ostree implementation on Arch is an interesting experiment. You might want to check out Darch which boots from container images.

Its a common courtesy that if you publish something on the AUR, then you actually think people would use it and you plan to maintain it. You don’t bother pushing some half baked afterthought to the AUR. Leave it on github. Otherwise you’re just squatting a perfectly good AUR package name.

People are publishing their slop projects as if they intend on maintaining them, but they clearly aren’t capable or willing to actually maintain them.

This is my #1 problem with it. Just put it on github and call it a day. Don’t act like its production ready at all. The #2 issue is namespace pollution.

$8 mil is pocket change for the investors. It’s like eight dudes all giving their bro $100 for his art project.

So its not tracking you across instances? Then its probably tracking the invidious instance itself and not you in particular unless invidious leaks some amount of data about your browser which is possible.

If you don’t want YouTube to be able to develop a temporary profile from a single invidious session then I think you’re out of luck. Either make a new session per-video or give up. Invidious needs to pass YouTube’s bot management somehow and once it does YouTube will give it a trackable session token.

Are you always using the same invidious instance? Does it track across different invidious instances?

Its possible that is YouTube isn’t building a profile of the user but a profile of that specific invidious instance which is all of its users collectively. Its also possible that invidious is leaking some browser info like User-Agent to YouTube. That way switching IP doesn’t matter as long as its the same invidious instance.

Switching invidious instances should clear that up. If not then you’ve got a serious problem with invidious.

You just change it when you want to drop any profile you developed. ie on browser start. The problem with changing it every page is sites will assume you’re a bot and either block you or serve you a captcha on every page.

Browser Fingerprinting. You must configure your browser to lie about what it is and change the lie repeatedly. Simplest way is plugin to change your browsers User-Agent. This will be a big deal on mobile because mobile browsers will actually report the device model in the UA. Be prepared to see lots of captchas if you do this though.

Yeah when will those expired GPUs hit the resell market? Or are they going to grapes of wrath them.

They are making the chips, building the data centers and collecting the data. None of those are the missing piece. The missing piece is being able to actually turn a profit from that entire pipeline.