honestly, it feels like the Threadiverse is slowly turning into Reddit (in a bad way). There's so much toxicity and right-wing talking points all over the network. You can see it in nearly every community, on many different instances.

Another vote for the steam controller - it's versatile enough to work comfortably with every game I've wanted to play.

My product manager is doing the opposite - pushing us to replace "bandwidth" and "effort" with "time". We're now expected to provide an accurate hour estimate for all work items, projects, and bugs. Getting it done later or sooner is penalized on the metrics.

There's a limited pool of random inputs, so it's possible to collect them all with enough input samples. In the past, the creator has asked people not to upload their input file because there are bots that scrape GitHub looking for the inputs.

Thanks for the reminder! I almost forgot to set up my repo. 🤦‍♀️ I'll be publishing my solutions on GitHub for anyone interested. This year I finally got around to restructuring things to keep the input files out of git, so I won't have to feel guilty about leaking the problem inputs.

I appreciate the transparency through all of this. It's nice to know about the problem while there's still some time to handle it. To be honest - I probably would not follow Beehaw to any new non-federated platform. Its nothing against Beehaw (I love this community and its admins) but I'm just not convinced that we could ever attain enough regular users to keep critical mass on the niche topics I follow. That's the real advantage of Lemmy - all (well-behaved) instances get to share their user base.

Unfortunately, I also understand why staying on Lemmy might not be an option. Same with forking or using another Fedi software. Either way - I trust y'all to consider all the options and make the best choice. 🐝💙

I agree that this is nothing to panic over, but I want to clarify that Lemmy is not safe from this. Lemmy and Mastodon both use the same protocol (ActivityPub) and that's also the protocol that Threads will use to federate. Just as Mastodon users can like, boost, and reply to Lemmy threads / comments, Threads users will be able to do the same. That's why it's important to defederate Threads on all ActivityPub-enabled instances.

I was working through a list of nature-related names, looking for an uncommon one that still sounded like a real name. I was almost ready to try out "Ember", but then I saw "Hazel" and it just clicked. So that's what I've called myself ever since!

I feel like this design would work pretty well even for a modern phone. Just flatten the bottom-right menu section and extend the screen over it, and you'd get a regular full-size smartphone with a slide-out keyboard and some handy physical buttons!

The same problem can also be solved with signed messages, like the HTTP Signatures used by Mastodon and most of the other microblogging fedi servers. Signatures allow a message to flow peer-to-peer instead of requiring a direct connection. You would only need a connection when actively interacting with a post on another instance, and its very unlikely that all 10K instances would be interacting with each other. Most likely, the network will consist of smallish groups of loosely-related instances plus a few giant servers that can handle the load of being popular.

Email is my go-to example when explaining fedi to unfamiliar people. Its especially accessible to non-technical users because almost everyone has sent an email to someone with a different provider.

This is really cool, thanks for sharing! Do you plan to update it again in the future? I'd love to see what happens an about a month!