IratePirate

Public Key

npub13dhljdd0klzezz5pz4gy7ctk8juwvj0w0m43mtm4remcg38j0lnqw7sguh

NIP-05 Address

Profile Code

nprofile1qqsgkmlexkhm03v3p2q325z0v9mrew8xf8h8a6ca4a63uauygne8lesprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyf8wumn8ghj7mmxve3ksctfdch8qatz5ukk7j

Publishing to

relay.momostr.pink

offchain.pub

relay.snort.social

Author Public Key

npub13dhljdd0klzezz5pz4gy7ctk8juwvj0w0m43mtm4remcg38j0lnqw7sguh

Show more details

Last Notes

2026-05-01 18:00:06 UTC

Like many self-hosters, I've looked upon the recent price hikes for storage in utter disbelief. Faced with paying double the price of what I paid only last year for new hard drives, I dug around my hardware stash and came across about a dozen of old 2.5" 320-500 GB drives which I had saved from the dumpster once, but never deployed. After all, they were too slow to be used as PC system drives and too small in storage size for any meaningful use in a server. Now seemed like a perfect time to look for a way to put them to good use after all. And I found it in mergerFS.
For anyone not familiar with it: in spite of its name, mergerFS is not a filesystem in the sense that in order to deploy it, you'll need to reformat any drives (although this wouldn't have been a problem for my use case). Instead, you can theoretically take a bunch of drives (JBOD) and string them together with _no_ modification to their filesystem, keeping existing data intact. It is agnostic of the filesystems present on the drives, meaning you can even combine volumes formatted with, say, ext4, btrfs, and xfs. All drives will show up in your filesystem as a single volume, and - depending on the policies you configured - store some data on this and some data on that drive. Since data isn't striped, the drives will remain individually legible, i.e. there's no need to rebuild all of them after a drive fails.
Speaking of drive failure: while mergerFS itself does not come with RAID, you can add SnapRAID to the mix for parity-based RAID (although it's not real-time RAID; parity data must be written on schedule, so it's not for mission-critical data that is frequently being updated and rewritten).
Combined, these two technologies allow me to have my cake and eat it too:
* I can put drives to use that would otherwise be rotting in a drawer.
* I can avoid additional cost - both financial and ecological. (The energy bills won't increase by much, either, because most of the energy comes from solar cells on the roof.)
* I can always flexibly tack on more drives, regardless of size.
* I can have the added data security of a RAID, but at the price of very few (if any) of its drawbacks (e.g. no drives of equal size needed).
If this was news to you - maybe you want to give it a shot too. (I don't consider myself a very advanced user and I found it dead simple to deploy.)
If you're already running mergerFS and SnapRAID, feel free to showcase your use case and setup!
If you found any of the above incorrect or misleading, feel free to correct me.

2026-04-20 19:40:48 UTC

I just had an encounter of the turd kind with a banking app that I want to share.
I'm in the process of migrating to a new degoogled phone (GrapheneOS) and upon installing the app in question via Aurora Store, it gave me an error message, saying it had not been installed from a "trustworthy" source. It would, therefore, refuse to start and tell me to install it from the Play Store. (For anyone curious: it's the [Consorsbank app](https://discuss.grapheneos.org/d/28376-banking-app-refuses-to-launch-due-to-untrusted-store), and the issue is well-known at this point.)
In spite of being on GOS, I was faced with the prospect of
- installing Play Services Framework (sandboxed or not, I don't want that shit)
- installing the Play Store (sandboxed or not, I don't want that shit)
- logging in to the Play Store (I *definitely* don't want that shit!)
only to run a damn app.
I eventually used [USB-debugging and ADB](https://www.kuketz-forum.de/t/android-ohne-google-account-nutzen/13204/19) to trick the app into thinking it had been installed from the Play Store.
So even though everything is running fine now, this doesn't feel like a victory. For the first time in a long while, I feel I have come head to head with a piece of tech that was not just maladapted for my janky way of running things and just needed some tinkering. This was outright malicious, refusing operation and trying to force me to use services I want nothing to do with. It only gave me the option to either give in or walk away and stop using their services. Now, I don't mind doing that for non-essential things. I don't have big tech-owned messengers, I don't have social media (save Lemmy) and all the other stuff people these days feel they cannot live without.
_Banking_, however, is a different kind of beast. Banking _is_ essential. Second factor authentication is usually done via apps these days. And if this kind of thing becomes normal for banking apps, and Google keeps locking down Android so hacks like the above won't be accessible any more, things are looking grim.
Tonight has left me with more questions than answers. Is Android still the 'right' ecosystem? What are the alternatives if this thing becomes more wide-spread? How do we combat this? Put pressure on banks to keep technologies open? Revert to physical second factor generators, until those become phased out by banks as well?