Hazelnoot [she/her]

Agreed, unfortunately. I’m not even sure it supports defederation :/

It’s good we have “Knewbies” in a sandbox when they start.

attention all companies: please stop making pet names for your employees, it’s weird

In my experience, the larger threadiverse instances have gradually collected the worst ex-redditors, who have brought the worst of reddit’s culture. I’m unfortunately not surprised that lemmy.world has queerphobic mods, given how the users behave. 😕

my employer has decided to license an “AI RDBMS” that will dynamically rewrite our entire database schema and queries to allegedly produce incredible performance improvements out of thin air. It’s obviously snake oil, but they’re all in on it 🙄

I’ve been using Xubuntu for half a decade, zero regrets.

The frontend is HTML only? Then I’d go with C# and ASP.NET Razor pages. Modern language with good DX, performant runtime, and server-side rendering.

Changing the domain of an established fedi instance is very difficult, almost to the point of impossibility.

In the past, people have stolen the problems to use in their own challenges, coding tutorials, and even commercial projects. The author has asked people to keep their inputs out of git or anywhere publicly searchable.

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.

They are mastodon-specific, but most fedi software has a similar feature. Or at least, all of the mainstream microblogging software does, as well as some of the image / video sharing platforms. I’m unsure about Lemmy and Kbin. Here are the equivalent settings for FireFish:

Defederating actually does stop Meta from accessing data (at least through ActivityPub) if you enable AUTHORIZED_FETCH / similar. That setting requires remote instances to authenticate themselves, which prevents blocked instances from querying anything. IIRC, Lemmy either already supports or plans to support that same feature.

Meta could, of course, just use web scraping, but that can be prevented with DISALLOW_UNAUTHENTICATED_API_ACCESS. Although admittedly, I don’t think Lemmy has this feature yet.

You’re thinking of LIMITED_FEDERATION_MODE, which is different from AUTHORIZED_FETCH.

Defederation actually does work both ways if the instance enables AUTHORIZED_FETCH. That setting requires 3rd party systems to prove their identity before they can retrieve any data, which allows an instance to block defederated domains. I don’t know if Lemmy or Kbin supports that, but practically all of the microblogging fedi software does (that being Mastodon / GlitchSoc, Pleroma / Akkoma, Misskey / FoundKey / FireFish, and GoToSocial).

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.