Mastodon where you can’t use the letter “e”: https://www.vice.com/en/article/its-like-tweeting-but-you-cant-use-the-letter-e/ ( oulipo.social )
Yes, but that’s a supported way to install Proxmox.
https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm
You have some options that aren’t in the installer e.g. full disk encryption
Your CPU should be perfectly capable of that. I ran Proxmox with some VMs and containers on an i5-2400 with 16GB RAM just fine.
You could run on bare Debian as well but virtualization will give you more flexibility. If you get a Zigbee Dongle or the like, you can pass it through to the VM Home Assistant is running in.
I don’t know MergeFS but usually the recommendation is ZFS.
Does it? On Android, it never asked me to grant location permission unless I try to share my location to another user. Similar with contacts and calendar, it’s working perfectly fine without them. Where exactly does it link those identifiers and with what?
Thanks a lot for your response! I too was a bit misguided by the way Proxmox presents LXCs but I’m mostly on VMs and haven’t explored LXCs further so far.
What’s your motivation for the switch? Second time in a short while I’ve heard about people migrating to incus.
You can have the best of both worlds - scheduled auto updates on a time that usually works for you.
With growing complexity, there are so many components to update, it’s too easy to miss some in my experience. I don’t have everything automated yet (in fact, most updates aren’t) but I definitely strive towards it.
I think auto update is perfectly fine, just check out what kind of versioning the devs are using and pin the part of the version that will introduce breaking changes.
I don’t know all of the tools, do you mean the tor relay?
On Android or postmarketOS? Very cool regardless!
Absolutely agree. I didn’t like the crosspost bots but this button? Sounds great.
Everybody knows by now, there’s it’s own community for it. It really doesn’t need to be posted here every day
Not much to do against scraping. On a small (but actively moderated) instance, a spamming bot will easily be detected and hopefully suspended. Generally, moderation is often better on smaller instances, so I’m not too worried about people migrating towards bigger instances - usually it’s the other way round.
For 2. - dedicated corp instances will be defederated from many instances quickly. Bridge accounts on other instances need to be dealt with by the mods.
Yes, of course this can increase moderation effort. But spam accounts are way more easy to deal with from a moderation perspective than issues between real human users which usually takes wayyy more effort to deal with.
That’s cool! I’ve always had the idea of a small k3s cluster on old phones with postmarketOS. I guess it doesn’t work with older phones which don’t have the latest Android Version but given the homelab trend generally goes towards small, low power devices, this could continue the trend with super small and low power phones. Probably in 2 years when current gen phones rotate out of company leasing contracts?
Are you selfhosting on your Desktop? What exactly is the use case? I’d recommend different distros for a server or a desktop.
I think there’s several open source rss-to-lemmy bots already so I think there’s not much need for another one. If you want to do it for experience go ahead but not sure it’s necessary.
Also, be careful with how often the bot posts etc. Filling inactive communities with botposts usually does not help with actual user activity.
Hehe thanks! Not 100% decided yet but since it’s running on my homeserver and not some VPS I guess I won’t open except for friends maybe.
That sounds good! If Pixelfed or similar implemented that, it could be sufficient. A new fedi service starting from scratch would lack the existing pool of resources since federation only happens when a post gets posted/boosted but after some time it could actually be useful.
Don’t worry, I didn’t :)