That is not true. Many attacks (e.g. the recently revealed Operation Triangulation) do not have persistence.

For me, once Apollo officially stops working I won't have any ingrained habit for reaching out to reddit. I stopped using the website years ago except for reading search results that point there.

I'll admit I'm not the biggest FOSS evangelist, so this comes with a grain of salt. From a right to repair standpoint, I don't care for Apple's policies at all. But from a security and (perhaps counterintuitively) user experience standpoint, I agree with Apple's walled garden approach, locked down OS, and single app store. We see the alternatives in Android, and we see how much worse its security is.

I bought Gloomhaven right at the beginning of the pandemic, and my roommates and I spent basically that whole summer playing together. We still keep in touch by playing the digital version as our schedule allows. So that one has a special place in my heart.

I don't, but a coworker uses an ergodox and I've been eyeing it lately

Went a month or two ago to see Peter Pan Goes Wrong and it was hilarious, highly recommend. Before that, probably Hamilton circa 2019.

Yes it is. While I'd heard of Mastodon in the context of Elon's Twitter dumpster fire, I had no idea it was federated or what the fediverse was. I like it so far, with the obvious caveats that there's plenty of room for improvement. I'm hoping to learn more about how the platform works technically so that I can contribute a bit.

Current place:

• Work is done on a feature branch on a personal fork of the repo
• Codebase requires 100% functional coverage, and you're responsible for writing the tests for your code and including that in the same PR
• Run pre-commit hooks for style auto-formatters before you can commit and push your code to your origin fork
• Ideally run local tests as well
• Create a PR to pull feature branch into the upstream repo's main branch, which triggers the CI pipeline for style and tests
• At least 1 other person must review the code before a PR can be approved and merged into upstream main
• There's a separate CI pipeline for testing of publishing the packages to TestPyPI
• Releases to PyPI are currently done manually

I agree that Lemmy could end up filling the same negative voids that reddit does. I suppose my hope is that by restricting the conversation and limiting bad-faith arguments, there will be less toxicity here relative to reddit.

In the end, addicting us with anger and outrage in order to drive participation and clicks is the end-stage of all social media, and that cat is out of the bag. But perhaps there's a little temperance that can be found if we don't see social media foremost as an opportunity to harvest data but as a way to interact and share ideas.

I feel like reddit dying could be a positive thing for me. For years now I have felt the negative influence that its toxic environment - fueled by impersonal, discordant interactions - had on me. Not to mention the complete destruction of my ability to concentrate caused by the micro dopamine hit targeting of social media UX. I'm hoping that moving to a smaller platform will help with some of that pervasive anger I feel as a result of constant reddit usage.

I'd be happy to help contribute as best I can. I don't have much Rust experience but I'd like to learn more. One thing I'm noticing: I like that there are a good deal good first issue tags for the backend repo, but only one for the frontend. I'm not sure if there's really that far fewer intro tasks for the frontend or if they're just not tagged as thoroughly.