Source code means you can refactor it to preserve that graphics. But realistically that’s unlikely if nobody wants to put the effort in

Was planning to get another Sony now but they stopped selling their phones in my country…

With Asus taking a pause and all other options being random Chinese brands or budget phones there wasn’t really a choice left…

The brilliance market justification of “see, people are buying [literally the only thing offered because options were removed], they like it [complaining loudly]”

Google’s “Material You” is “Material anybody-but-you”

So valueless in the metrics that actually matter

Clearly you have your ducklings in a row

That’s depending on client. I’m using Thunder on Android, it shows it

This is the cross post, original OP is here https://lemmy.zip/post/68335876

These days it’s probably an AI :/

Unless the person/entity has a history of bad behavior, which Facebook does

I think that’s an error with prebaked lighting effects, because it’s hard to see why it would give those square texture error style glitches otherwise

Found the dude on LSD

And regardless of if it’s Sweden or USA, it’s still stupid to have a misaligned clock.

I’m not upset, just annoyed that people choose to be stupid when they know there’s a better choice.

Who is? It’s not 8/4 here.

No, not when you put the sun and clock out of sync. Just fucking change when you set your alarm if you don’t want the health benefit of morning sun.

Having a deliberately wrong clock because there’s an unjustified offset when you don’t need the offset is stupid.

I live in SWEDEN, try again

Change your schedule, not the clock

Standard time is better for health, and much less stupid to have the clock synced to the day cycle

It’s Russia, if you’re not really high profile they don’t care

Wikis benefit more from the ability to mirror them and to link between them than they benefit from full federation. You need much better antispam on a popular wiki than in most other user content systems, and that’s not solvable with just blocklists like in many other federated systems. You need almost all antispam working server side, the user side fixes doesn’t work effectively.

It would be useful with atproto (bluesky) style portable identity where you could log into other wiki hosts from your own hosts user account to submit stuff (allowing you to maintain a single account in federation through OAuth logins, while still allowing each wiki to be centrally managed) with support for mirroring and native cross-linking between mutually trusting wiki hosts. You could replicate the Wikia/Stack Exchange user experience this way, without all the ads and without any central gatekeepers. (Very similar to stack exchange actually, as each individual Wiki would be read-only to you until you login to it separately (still using one a single account))

Things like content addressing could allow proper static links that survive page name changes for the cross-linking, etc.

There’s things built for entirely different reasons that can be used as a federated Wiki if you wish, like Fossil (a federated version control system with a Wiki)

https://www2.fossil-scm.org/home/doc/trunk/www/index.wiki

Note that Wiki federation has a whole bunch of potential issues if you try to allow automatic updates from arbitrary users. Wiki servers rely heavily on antispam measures which often require a lot of analysis of the user’s connection, data which often isn’t available over federation, so submissions by others have to be validated manually. Fossil being a version control system means it is more of a mirroring friendly Wiki than truly federated, but you can set it up so that mutually trusting mirrors can replicate each other’s validated commits/updates.

Depends on the federation model. For lemmy I assume things like comments aren’t pushed automatically (?) until the thread is opened, but in some models the instances pull all new content from at least the known accounts / spaces from known servers (I think regular Mastodon does that)

Genuinely, we’re better at preventing memory formation and experience of pain than actual sedation. Patients can be cognitively present, and the reason they’re not traumatized from a experiencing a surgery is that we’re preventing the experience from leaving a mark on the brain

https://pubmed.ncbi.nlm.nih.gov/40626585/