* https://addons.mozilla.org/en-US/firefox/addon/redirector/
* https://chromewebstore.google.com/detail/redirector/ocgpenflpmgnfapjedencafcfakcekcd
* https://addons.mozilla.org/en-US/firefox/addon/redirector/
* https://chromewebstore.google.com/detail/redirector/ocgpenflpmgnfapjedencafcfakcekcd
I would recommend getting them the hell off of Windows as well if you can, installing uBlock Origin in their browser, and disabling all browser notifications. Linux Mint is a great distribution for non-technical people. Just tell them to only install software from the Software Manager application and to think of it like the app store on their phone.
Usually, it's nothing a reinstall won't fix but if they can change the password/recovery of the Microsoft account and the disk is encrypted (which is the default if you sign in to a Microsoft account on Windows 11) it can be impossible to get their data back without the help of Microsoft support, who will treat you as if *you're* the one trying to steal the account. It is important to remember that the people running these types of scams don't have much deep technical knowledge (if they did, they could get a real job) so I've never heard of that happening but it is a serious risk.
rm -rf just got me, big time. I realized what had happened and stopped it in less than a second, but it had already deleted ~3000 (70 GiB) of files I didn't want to delete. Luckily I had backups in Restic.Fun fact: This is the first time I've had to restore more than a file or two from any of my Restic repositories.
Badblocks via
mkfs.ext4 -cc was taking too long on the full 1+1 TB array so I made new 250 GB partitions and neither drive had bad blocks in that range so it was just a waste of time. Maybe if I come back to it I'll do the full array and have the EFI system partition in RAID 1 just for fun. I didn't know that worked with software RAID.> The key part is to use --metadata 1.0 in order to keep the RAID metadata at the end of the partition, otherwise the firmware will not be able to access it.
I had the ESP on a USB stick for simplicity's sake.
Badblocks via
mkfs.ext4 -cc was taking too long on the full 1+1 TB array so I made new 250 GB partitions and neither drive had bad blocks in that range so it was just a waste of time. Maybe if I come back to it I'll do the full array and have the EFI system partition in RAID 1 just for fun. I didn't know that worked with software RAID.> The key part is to use --metadata 1.0 in order to keep the RAID metadata at the end of the partition, otherwise the firmware will not be able to access it.
I had the ESP on a USB stick for simplicity's sake and booted from that.
Even if the content is encrypted, though, you're still giving quite a bit of metadata to Google by using their notification service.
https://docs.ntfy.sh/faq/#how-much-battery-does-the-android-app-use
https://docs.ntfy.sh/faq/#what-is-instant-delivery
Mobile XMPP clients usually implement notifications using XEP-0537 and it goes like this:
Your XMPP server -> Client vendor's notification server -> Client OS notification server -> User's device
It's not end-to-end encrypted so servers will usually just send a dummy message through (You received a message from juliet@capulet.lit!) so you have to open the app to see the (hopefully) encrypted message.
It's a similar flow on both iOS and Android and I assume Matrix clients work the same way.
$ units -t '500 gigabytes per 9 hours' 'megabytes per second'
15.432099
That's very unfortunate.
$ units -t '500 gigabytes per 9 hours' 'megabytes per second'
15.432099
That's a very unfortunate speed in the year 2024.
If you're trying to make non-technical people set up their own Yarn pod, that's probably (unfortunately) impossible. Management software like Sandstorm make it "as easy as installing apps on your phone" (direct quote from sandstorm.org) and most people still pay Google to store their photos.
I remember you were trying to do paid hosting for Yarn pods in the past. That could work, but as I'm sure you know it's difficult to convince people to use this over X or Facebook, let alone host their own pod. I think it's going to stay a small community of fairly technical people for the foreseeable future.
I edited it because I started the line with
500., which the Markdown parser took as the start of an ordered list and made it number 1.
ffmpeg.txt comes in very handy.
No worries @aelaraji, it happens to the best of us.
Bcachefs has similar features (but not all of them, like sending/receiving) and it doesn't have the giant scary warnings in the documentation. I hear it's kind of slow and it was only merged into the kernel in version 6.7. I wouldn't really trust it with my data.
I bought a couple more hard drives recently and I'm trying to figure out how I'm going to allocate them before badblocks completes. I have a few days to decide. :)
This was a couple of years ago, so I don't know if anything's changed since then. It's really not a big problem, because it would be run with some kind of preset command line (systemd service, container entrypoint) in a production environment.
Yes, my backup target is my home server. I have a hard drive dedicated to Restic repositories. It's still not a real backup as I don't have anything offsite but it's better than my previous solution. I had two very old hard drives I kept plugged in to my desktop PC and I would (on very rare occasion) plug in another hard drive and copy all the files over to it. Luckily, I've never suffered any significant data loss and I would rather not start now. Once I have automated backups on each of my machines, the next project is getting those backups offsite.
@prologic I support the delisting of ciberlandia.pt in the Discover feed due to the sheer volume of posts from there and the fact that most of them are in Portuguese with this being a predominantly English-language pod.
I like @sorenpeter 's suggestion. It gives the users the information and lets them make their own decision instead of putting a big scary warning in their face. That's what Microsoft does, and we shouldn't be Microsoft.
restic backup for each one?
I asked this one almost a year ago and I started using Restic shortly after that. When I started, I was only backing up my home folder to the repository over NFS. Now, I'm backing up the entire root filesystem to a repository using the REST backend so I can run Restic as root without breaking the permissions.
I'm working on automating it now and I'm trying to come up with something using pinentry but my proof-of-concept is getting pretty obtuse. It will be spread out in a shell script, of course, but still.
systemd-inhibit --what=handle-lid-switch restic --password-command='su -c "printf '"'"'GETPIN\n\'"'"' | WAYLAND_DISPLAY=wayland-1 pinentry-qt5 | grep ^D | sed '"'"'s/^D //'"'"'" mckinley' --repository-file /root/restic-repo backup --exclude-file /root/restic-excludes --exclude-caches --one-file-system /
I'm curious to see how everyone's backup solutions have changed since last year.
I asked this one almost a year ago and I started using Restic shortly after that. When I started, I was only backing up my home folder to the repository over NFS. Now, I'm backing up the entire root filesystem to a repository using the REST backend so I can run Restic as root without breaking the permissions.
I'm working on automating it now and I'm trying to come up with something using pinentry but my proof-of-concept is getting pretty obtuse. It will be spread out in a shell script, of course, but still.
systemd-inhibit --what=handle-lid-switch restic --password-command='su -c "printf '"'"'GETPIN\\n\\'"'"' | WAYLAND_DISPLAY=wayland-1 pinentry-qt5 | grep ^D | sed '"'"'s/^D //'"'"'" mckinley' --repository-file /root/restic-repo backup --exclude-file /root/restic-excludes --exclude-caches --one-file-system /
I'm curious to see how everyone's backup solutions have changed since last year.
I like the simple architecture of Pass, and it would indeed lend itself well to a Git repository, but I don't like that service names are visible on the filesystem. pass-tomb might mitigate this somewhat but it seems messy and I don't know if it would work with Git without compromising the security of the tomb.
What's so good about Bitwarden? Everyone seems to love it. I like that it can be self-hosted. I certainly wouldn't want a third party in control of my password database.
To accept Monero, all you need is a wallet program. I recommend Feather Wallet. Create your wallet in there, then you'll copy the wallet files into monero-wallet-rpc for use with MoneroPay, see docker-compose.yaml.
To accept Monero, all you need is a wallet program. I recommend Feather Wallet. Create your wallet in there, then you'll copy the wallet files into monero-wallet-rpc for use with MoneroPay, see docker-compose.yaml.
Unfortunately, the characteristics that make it useful as a global currency for day-to-day transactions also make it useful for people doing illicit things. Many exchanges, fearing regulatory action, won't accept Monero for the same reason they won't accept Bitcoin from a mixer.
Monero shouldn't be banned just because people use it for bad things. It's just a tool and it can be used for good or evil. It's the same reason countries use when they ban or restrict Tor usage.
> On-demand Linux containers.
> Run almost anything, without having to touch the command line.
> Coming Soon
https://kyun.host/services
With Monero, it's not possible to trace any transactions with just an address. People can't see what you're spending your money on or where your coins came from. Transaction fees using Monero are also very small. It's less than the equivalent of 1 cent in USD.
Minuscule transaction fees and anonymity make it the best choice in my opinion for buying goods and services online. Monero is much more like "digital cash" than Bitcoin, which I think is better described as "digital gold".