Hazelnoot [she/her]

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

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.

Jain’s team then built artificial-intelligence models that were able to stitch the microscope images together to reconstruct the whole sample in 3D.

The map is so large that most of it has yet to be manually checked, and it could still contain errors created by the process of stitching so many images together. “Hundreds of cells have been ‘proofread’, but that’s obviously a few per cent of the 50,000 cells in there,” says Jain.

Ah so it’s not a real model, just an AI approximation.

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.

Right?? I normally love it when websites have a fun twist, but this one really needs an off button. The other cursors keep covering the text and it becomes genuinely uncomfortable to read. Fortunately, you can easily block the WS endpoint with any ad blocker.

Thank you for this! You can also get rid of it with a custom ad-blocker rule. I added these to uBlock Origin, and it totally kills the pointer thing.

wss://tonsky.me
http://tonsky.me/pointers/
https://tonsky.me/pointers/

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. 🐝💙

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.

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!

“good” is subjective, but I can recommend the Tomb Raider reboots.

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.