zeluko

bUt iTs Ai InTeGrAtEd

I will guarantee you, these will be additional ads, not replacing existing ones.

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

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.

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 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.

If it was just forked, cant you just switch the package/container-image and be done?

I dont see the “manager” part in your zip archive…
More like a bunch of text files… and you are doing the job of the manager

afaik, most if not all modern browsers and clients in e.g. apps, use Diffie-Hellman key exchange in TLS.
Some Apps go even further and implmement certificate pinning, only allowing a set of specific certificates the server is allowed to “present”.

You can only break it by an active Man in the middle attack, presenting your own Diffie-hellman parameters toeachother and signing them with a certificate the client trusts (we can probably assume US agencies have access to some CA keys and can do this)

I dont think this is very feaseable on a large scale as you’d need to intercept every interesting connection, break the handshake, risking detection, and further proxy and process the whole traffic.
Metadata will be more juicy en mass than the content and easier to obtain with less risks.

Looks like its only for copy, not left-clicking to open it.
Also doesnt stop click-hijacking. If the Site encodes a url you cannot decode, you have to go through the site or, if the link is also visible as text, grab that.

The interface is weird and unintuitive at times…
I have a dropdown menu at the button “New custom field” and can select “Hidden”.

I like that KeePass has the option to set fields as protected

Vaultwarden can do that, though its quite stiff in some aspects like folders… subfolders? nonexistant…

Ideally keypass would allow handling such conflicts internally.
Thats the big disadvantage of a single-file approach.

Could easily be avoided e.g. sync whole folder and now you can have multiple files, e.g. 1 write file per program used.