zeluko

Indeed, not classically, but there are HSTS preload lists you can put your domain into which will be downloaded by supported browsers.
And via HSTS you can include all your subdomains, which would then force proper TLS connections for those you havent visited before too.

With the new TLS1.3 version we are getting the HTTPS / “SVCB” Record which not only allows ECH but also indicates to the client similar protection policies like HSTS. (RFC 9460)
ECH will then make such attacks impossible on TLS-level, assuming DNSSEC is used and client can make an integrity-checked lookup e.g. via DoH/DoT or validating DnsSec themselves.
The strength of this depends on the security-chain you want to follow of course. You dont need DNSSEC, but then the only integrity-check is between DNS-Service and Client if they use DoH/DoT (which is usually enough to defeat local attackers)

bUt iTs Ai InTeGrAtEd

Your own servers probably also dont have HSTS enabled, or clicking continue will be disabled (if not overwritten in your browser-config)

Thats why we now have certificate transparency reports and CA-records.
Sure not perfect, but at least with a compliant CA it wont just happen in the dark.
At some point you have to trust someone.

Thats why we have HSTS and HSTS preloading, so the browser refuses to allow this (and disabling it is usually alot deeper to find than a simple button to “continue anyways”)

afaik its using the backup of Rarbg and adding new content too
its the one with .to

Yeah and discord is allowing it. Thats all i am saying.
Of course Restorecord is doing it on purpose. There are some valid reasons, but maybe Discord shouldt allow untrusted bot-developers like them to do so.

afaik thats rather about the parallel service someone had selling the data for a subscription and getting that data from restorecord’s database.
In the video it is already suspected restorecord is in on it, and the update comment proves it.

The problem with restorecord getting that data in the first place persists. I am not aware if Discord is tackling that issue at all e.g. making it against EULA and banning those bots.

Discord bots were able to get a users IP via the verification system afaik.
And there are of course other ways to force users to do so. Its more interesting Discord themselves didnt care about these methods to ban such bots… well its Discord, not that surprising when i think about it.

https://www.youtube.com/watch?v=d0h4QPqAwss

Media is better indexed on Rarbg (which doesnt exist anymore, but the biggest copy is TheRarbg which works similarly)

But they are leaving it open…

big reason why i switched to kopia, borg just doesnt cut it anymore…

I would be careful with some of these providers depending on your usage.
You are potentially sending a ton of info to them…

I have access to Bing Chat Enterprise through my company, and only because its the Enterprise version i am half confident in using it with more restrictive data.
Though the frontend of copilot is so heavy and sucks, so i have a proxy for GPT-API to Bing Chat.
Had hoped GPT4All Bing provider would support login, but sadly not, so essentially had to reimplement it all myself.

umm… isnt the government or rather the judikative already deciding what extremist is?
How would specifically this be different?

I can understand the problems thos causes for the platforms, but the government injecting decisions is something you focus on?
Not to forget the many other places they inject themselves… one could say your daily lifes because… careful now… you live in the country with a government, whaaat?

Yeah, it needs those rules for e.g. port-forwarding into the containers.
But it doesnt really ‘nuke’ existing ones.

I have simply placed my rules at higher priority than normal. Very simple in nftables and good to not have rules mixed between nftables and iptables in unexpected ways.
You should filter as early as possible anyways to reduce ressource usage on e.g. connection tracking.

Have a friend with a Gen1, super easy to hack and not used in some time…
The others need a modchip, can be a bit pricy and is more fliddly.

Was just a matter of time

Copilot is weird and can give out very weird responses that have little to do with your conversations.

And of course it might just grab context depending on what you do (e.g. clicking the copilot button might already do that).

I found it works best as GPT model if you disable the fancy stuff like search. It too easily looses track of what happened or completly goes off the rails.
(i believe disabling search is a beta feature in some regions, but its a hidden flag you can theoretically set, i made a tampermonkey script to add a button).

I hate the slow UI of Copilot, so i translate requests from a different GPT interface.

DNS filtering only gets you so far. Its far, but certainly not at the end of the road. More complex and differently designed systems wont be bothered much.
Encrypted DNS or simply hosting legitimate stuff on the same domain cannot really be fully blocked entirely or make your life difficult.

Better quality releases and more active users with much less leeches as they get thrown out.
Though there are many site admins with some complex here too… your experience can vary.

And of course you need to contribute to the community, most trackers will grant you buffer for both uploading and keeping the torrent running. You want something, then you have to give back.
If the tracker doesnt give possebilities to build your buffer in multiple ways, other than just uploading, its usually a shit tracker.
And some are just super hard to impossible to get into. Start small, wait for open signups or just go to new trackers, they might get bigger over time.
Dont publicly beg for invites, you can humiliate yourself in private chats if you are into that.