My bad, I didn’t think of that. My only thought was “$20 says this chucklehead won’t do squat” because we know.

https://grapheneos.social/@GrapheneOS Here you go, argue with GrapheneOS - it’s an open platform, go ahead and make a masto account and share your thoughts with them. Tell them what you think! The rep who handles their masto account is very well spoken and presents rebuttals of value so I advise you bring your A game.

There are already instances doing this (and Mastodon ones as well), it’s a thing - there are warehousing no-user instances[1] But they could be blocked! We can’t have that, luckily…

…the Lemmy API and RSS feeds have no authorization around them for consuming the firehose of data; if I were a person doing this data gathering, I’d just passively monitor the firehoses off the top instances from random rotating IPs. Could and is most likely happening right now, can’t block them.

[1] I personally wrote a simple script which uses the fediverse observer info, grabs the XX most popular communities and builds a subscription import file to bootstrap a new Lemmy instance. wasn’t hard, just some curl and jq work.

Put HE (dns.he.net) in your back pocket - they run a free DNS service which includes slave (do we still call it that?) service so that you can add their resolver as an ultimate failover / failback if your self hosted DNS takes a dive for whatever reason things break in our world.

Generally, hosting your own DNS “should” mean having a primary and secondary on separate AS networks, or at least different provider routes or locations. But if you’re doing all this from home, where is the second location for DR purposes… exactly? I sure don’t have one, power goes out here everything goes dark - in the old days everyone used to do this (share out tertiary DNS to each other) but it’s become a thing of the past in today’s world. HE can help fill that gap.

To your point - I use Gcore DNS and Bunny DNS for my stuff, as I mainly use online VPSes and don’t run racks of hardware at the house. The only things I physically selfhost at home are a pair of old laptops acting as storage servers which backup all my bytes and bits from online to some SSDs.

I feel attacked ;)

I have not tried/used it (yet?), but the kids are building Radicle for this very purpose. It gets a fair amount of techie coverage (blogs, comments, etc.) but sits in unique space compared to, say, Forgejo (classic self-hosted git).

You’re not going to like this answer - there’s a bunch of different ways depending on the app(s) and the desktop environment. The Arch wiki goes over it in detail: https://wiki.archlinux.org/title/Default_applications

I would guess that focusing on the XDG spec and covering Gnome, KDE and Xfce (Xfce can be replaced with anything else like Cinnamon that comes with Mint, “non Gnome or KDE”) is the best plan of attack for what matters to 80%+ of the population.

One I snack on with unsalted tortilla chips, the other I do not. But now I have to try it.

I see folks mentioning going back to their dormant LFM accounts. The Metabrainz Foundation has a project ListenBrainz, a more open FOSS style version; if you’re going to spin some scrobbling cycles maybe check it out:

https://listenbrainz.org/

(I stopped scrobbling years ago, privacy concerns)

Stars are just someone’s bookmark (me included) because there’s no simple “bookmark this because I’ll forget in an hour and want to look at it later when I have time.” If one trusts Stars, you’re literally trusting a bookmark that I didn’t put more than 2 seconds of thought into clicking because I have a bad memory. Many I know do the same.

I go straight to code history, show me what the commits look like. One can derive a lot about the project based on just the way the commit messages are written before looking at the code being changed. How the code is changed over time (process, communication, methods, etc.) adds more layers to the qualitative observation. I move on to Issues when I want to see how the devs interact with the users having problems, which is another story.

https://en.wiktionary.org/wiki/footgun

https://en.wiktionary.org/wiki/shoot_oneself_in_the_foot

The dichotomy here is you can’t be famous hosting exploits on smaller forges. Gotta be on the big platforms where you can be starred and forked for social media cred to make news stories to impress your friends. IIRC I think HeartBleed (maybe ShellShock?) was the tip of this popularity iceberg…