Looking back through your history, that’s a post by a user local to your instance. You can see it because you’re on the same instance.

If I understand how federation works correctly, posts don’t go directly to the instance a community is on when they are made. They are created locally on your own instance, and then federate out if/when they can. Since you’re both on the same instance, you can see the post and interact with it, but the post and your comments are (presumably) stuck in a queue trying to federate to the now defunct instance. Since lemm.ee is gone, it can’t federate out, so other people don’t see the post/comment on their instance.

I think that’s what’s going on.

BlueSky uses AT Protocol which is similar to how you break things down: https://en.wikipedia.org/wiki/AT_Protocol

Should be trivial to set up something like that if you’ve got parts you want to work with. Any desktop with an automatic background switcher should be able to cycle through images in a directory you specify on a timer. Set up your favorite remote access software (SSH, Samba, NFS …) and you’re done. If you want more control over the behavior, you could script up something custom with a little more effort – but it’s still not particularly hard to implement something like that.

Watch out for burn in on the screen if you’re leaving it on all the time.

Instances go down a lot – often permanently. e.g. kbin.social, lemm.ee, etc.

When an instance goes down, it takes out all the user accounts and communities on it, and it’s hit or miss if you can find copies of the posts on other instances.

By “legacy” they probably mean that they work with the older process technologies, not that the fab itself is old:

The acquisition includes an existing 300 mm fab cleanroom of 300,000 square feet and will further position Micron to address growing global demand for memory solutions

In its May 2024 ’Hooray, we’re open!’ announcement, PSMC said it invested more than NT$300 billion (US$9.5 billion) on the facility, and that it had capacity to produce 50,000 12-inch wafers per month under 55, 40 and 28 nanometer technology nodes.

Those kinds of chips are still very useful for things like cars and washing machines and such where you don’t need bleeding edge chip tech.

I haven’t tried Nostr, so have no opinions on what the experience of actually using it is like, but cryptographic identity seems like it’d be a better way (technically speaking) of doing things than AP; tying everything to domain names has worked rather poorly – as we’ve seen repeatedly every time an instance goes offline…

I ended up on AP after jumping ship from reddit. I was on kbin first (since it was readable w/o JS and I liked the UI), and then later using the mlmym interface for lemmy as kbin because more unstable and eventually went offline.

reddthat is an instance hosted in Australia; so the answer to “how will the ban affect it” is “we already have an age limit in place”. That’s my point.

We discussed it in the community posts back in Dec 2024 when the law passed – February is when the sign up change happened and March was when the announcement went up. The UK’s bullshit may be what prompted the announcement happening then though.

On reddthat, we got this notice in an announcement back in March 2025:

Age Restriction

Effective immediately everyone on Reddthat needs to be 18 years old and futher interaction on the platform confirms you are over the age of 18 and agree with these terms.

If you are under the age of 18 you will need to delete your account under Settings

This has also been outlined in our signup form that has been updated around the start of February.

Wow, I didn’t realize. How time flies. 😲️

Thank you!

The fifth instance denied my application with, “read the coc and reapply”

Don’t know what instance that is specifically, but if their application process is anything like reddthat’s lemmy application process, there’s probably a bit in there about something specific you’re supposed to include in the application so they can weed out bots.

This won’t fix parents just buying a device to palm off to their kids, because if setting up parental controls is beyond them, setting up an account for them properly likely will be too.

Sure, but this limits companies liability if they make a good faith effort to comply; idiot parents being idiots and not setting up a kid’s account are no longer their problem, legally speaking, if they follow this law and respect age signals.

It’s already happening. California passed a law to require OS vendors and online services to support this functionality last month.

How is device-based age verification different?

You put your device in child safety mode, and it tells sites “I’m a kid, treat me like a kid” – otherwise the site can assume you’re an adult with full rights. Done. No intrusive ID requirements. No face scanning. No third-party payment shakedowns. Parents, in theory, can still stop their five year olds from accidentally accessing PornHub or other content that would disturb them by just clicking a button when they set up an account on the device.

It’s, frankly, the sane way to do this if we’re going to have age restrictions.

It looks like the connector is U.2 so I’d look for motherboards that indicate support for that explicitly. From a quick search, it looks like SuperMicro makes some. This is getting out of my area of expertise though; I just know the crazy drives exist…

Assume an unlimited budget for now, I just want to know what’s out there.

I mean, if you’re willing to pay the price of a car per SSD they go up to at least 122TB density per drive… (e.g. Solidigm SBFPF2BV0P12001 D5-P5336 – $16K~$20K depending on supplier from a quick search)

I don’t actually recommend that for personal use, but since you were curious about what’s out there, there’s some absolutely crazy shit in enterprise server gear if you have deep enough pockets.

If that doesn’t work when you try again later, then try searching in the community@example.com format specifically, and also try searching for the URL of a specific post – that might get it to federate the post and then you should be to access the magazine from that if it succeeds.

If that still doesn’t work, message the admin of your instance and ask them for help.

Good luck.

Try searching for the community explicitly – e.g. community@example.com – that should make the server aware that it exists. You may also need to subscribe to keep it from going stale, IIRC.

It’s been a while since my time on kbin, so apologies if I’m remembering something incorrectly or if mbin has diverged since then.

Just run a web server and expose the specific files you want to share through that?