It’s not too late.

I have some success by using the “Hide Read Posts”, but it’s pretty flakey.

Noted on both, though I wasn’t aware that I was asking for ICT support, rather I was attempting to discover if the problem I was seeing was unique to me or experienced by others, which turns out to be the case.

I’d rather not delete this thread, but if the mods feel that it’s in breach of the rules, I’ll abide by their ruling.

As a creator, I’d be much more interested in a way to get paid into my actual bank account in such a way that didn’t involve Bitcoin (et. al.), PayPal or Stripe.

It works as it’s currently implemented.

That said, I’d like it to comply with my preference for Dark Mode without me having to install a browser extension to forcefully recolour the interface.

Not really. Sometimes I even get to the end of the feed :)

When I relaunched 20 minutes ago, it took about three screen fulls to find some already seen posts, then a whole lot of new, then more old ones from nine or so hours ago when I checked at lunchtime.

I understand. That’s not what I’m seeing, it’s the same (sequence) of posts.

But I’ve seen those posts before, so I’m not sure how I could have seen them if they hadn’t been pushed to my instance already.

Also, only one Lemmy account, so no potentially spurious side effects from switching between accounts.

Sort is set to set to All:New

Which is also weird. I just saw several one of those posts, 8 hours old in the middle of the feed.

If that was true I’d see the odd duplicate post, not a string of them. Voyager also shows crosposts like a post within a post, and I’m not seeing that.

Tah. I’ll have a look see.

Not sure how, or if, I’d want to install an Arch package under Debian, but it’s my understanding that the package I’ve raised a bug for under Debian implements, or is supposed to at least, the functionality you’re describing.

What I haven’t found is a recipe that documents exactly how it’s supposed to work (not to mention, in a Debian way).

I’d love to discover something that doesn’t start with instructions to remove all pipewire packages and install from source, since that completely defeats the purpose of running Debian Stable as the host.

In my adventures I did look at this, but it appears to require that you install support for this inside the guest, which is possible for modern guests, but not for ancient ones like say Debian Wheezy or Win98se.

I’d be surprised if they had been updated at all after their installation was signed off.

While I share some, if not most, of your disinterest, it’s probably worth pointing out that while “we” had a Saturn V rocket system and Apollo space program that did, at least superficially the same as Artemis so far, we could not actually repeat a Saturn V launch today, as-in we lost many of those skills and associated experience.

In many ways, Artemis is essentially getting back to where we left off in 1973 with the intention of eclipsing it, but the ongoing NASA budget cuts being perpetrated by the current regime are in my opinion going to curtail the program before too long.

If I recall correctly, after Apollo 11, the TV audiences dwindled for the rest of the program, with a brief spike for Apollo 13, so perhaps there’s an aspect of that to consider.

For me the disappointment was triggered by the poor camera handling during launch, the view of backpacks, food and plushies surrounding CAPCOM at Mission Control, the broken toilet debacle and the heat shield obfuscation, all of which made this less leading edge science and more of a shitshow.

I hope the astronauts land safety in a couple of hours, but I won’t be watching for days like I did for the first Shuttle launch in 1981.

The impact to society from space exploration is immense if not immeasurable.

• Weather forecasting
• GPS navigation
• Earth sciences
• Robotics
• Medical imaging

NASA has a website dedicated to the topic, as do other agencies around the world.

• https://www.nasa.gov/humans-in-space/benefits-to-humanity/
• https://www.asc-csa.gc.ca/eng/about/everyday-benefits-of-space-exploration/
• https://www.space.gov.au/why-space-matters
• https://www.esa.int/Science_Exploration/Space_Science/Benefits_of_space_science

There’s also a Wikipedia page on the topic:

• https://en.wikipedia.org/wiki/Benefits_of_space_exploration

Nothing says leadership quite like being the first to leave a toxic platform … oh wait.

Globally we’ve agreed that the ASCII code for a space is 32, 65 for the letter A.

Unicode characters are also globally defined, so when someone uses an agreed upon code, everyone sees the same thing, like this grimace smiley 😁

A private area is a place that we’ve all agreed is for “private use”. If a trademark owner wants to use their special character in their documentation, they can define one area to represent their character, but the only people who will see it in the same way, are people who installed their particular font.

Anyone without that font would see whatever the font on their own machine displayed.

Putting random stuff in such a place is no more than putting gobbledygook in a text and it might even be used as a way to fingerprint text.

I’m not sure what you want to “detect” or “mitigate”.

While this doesn’t answer your question, I use Docker for this exact purpose, since you can throw away everything if it fails, whilst keeping a recipe for success documented in a Dockerfile.

This is what the DPL actually wrote on the subject:

Recent discussions have started around new age verification legislation that may affect free software operating systems. In particular, the California Digital Age Assurance Act (AB 1043), expected to take effect in 2027, raises questions about whether operating systems and package distribution mechanisms could be required to provide age-related information to applications. In parallel, a recently adopted law in Brazil appears to introduce similar requirements and is already in force, with initial interpretations suggesting it could apply to components such as package management tools. These developments are currently under discussion within Debian and other projects, and SPI has initiated efforts to obtain legal guidance. At this stage, the situation remains unclear, and further analysis is ongoing.

From a non-lawyer perspective, it is not yet clear how such regulations apply to a non-commercial, volunteer-driven project like Debian, which does not sell software and provides it in a highly decentralized way. It seems plausible that obligations, if any, may primarily affect redistributors or commercial entities building products on top of Debian. In such cases, Debian would as usual be open to contributions that help downstreams meet their requirements, while keeping such features optional and respecting the needs of users in other jurisdictions. However, this is an area where proper legal analysis is still required.

Source: https://lists.debian.org/debian-devel-announce/2026/04/msg00001.html