bUt iTs Ai InTeGrAtEd
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”)
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.
But they are leaving it open…
big reason why i switched to kopia, borg just doesnt cut it anymore…
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?
I mean EndeavorOS can install the same gui package manager as Manjaro has, pamac.
Game support usually comes from using packages you need and those packages being up to date to support latest changes like fixes.
Am a long time EndeavourOs user, quite happy, it allows everything i need and pacman never broke on me… cant say the same about apt, when using non-standard repositories (for some up to date packages)
And the AUR is awesome. Has many packages not found in the normal repositories, just some have to be compiled which can take a bit of time, but i dont have to fiddle with it.
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.
Which can include programs which do this.
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.
I can change my screens too on desktop, pretty neat.
Unfortunately its a super simple implementation which doesnt take into account the brightness between different screens.
Ideally there should be a master slider and one per screen. The master slider should then use theother sliders current value as scaling factor to change them.
A more complex option could then also allow setting the brightness of each screen which would allow for better setting via the master slider. (not sure if this information is already available)
Or you use TPM, which you can get the key out of
I dont see why someone would need this deal anyways… most is already available, and most the new stuff probably too, even without API access.
I also expect the fediverse to be crawled and used for training, thats just the thing about publicly available stuff, it gets used, if we like it or not…
So i understood you just want some local storage system with some fault tolerance.
ZFS will do that. Nothing fancy, just volumes as either blockdevice or ZFS filesystem.
If you want something more fancy, maybe even distributed, check out storage cluster systems with erasure coding, less storage wasted than with pure replication, though comes at reconstruction cost if something goes wrong.
MinIO comes to mind, tough i never used it… my requirements seem to be so rare, these tools only get close :/
afaik you can add more disks and nodes more or less dynamically with it.
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)