I think it’s just that Mastodon posts in Lemmy are weird.

Toots don’t have titles so it just duplicates the content, and then you have a mess of @ and # tags that don’t make sense in Lemmy.

Cross-ecosystem federation is cool but also leaves a lot to be desired.

It makes sense to me IF it actually works.

Having extra capacity when a device is brand-new isn’t a huge boon, but having stable capacity over the long term would be. At least for me.

Of course this will depend on your habits. If you replace your phone every year, then it doesn’t matter. If you’re a light user and only go through a couple charge cycles per week, it’ll matter less than if you go through 1-2 cycles per day.

Personally I’m at around 1 cycle per day on my current phone, and after nearly 3 years (over 1000 charge cycles now) the battery life is shit — much worse than just 80% of its original battery life. Performance also suffers. With my last phone, I replaced the battery after 3 years and I was amazed at how much faster it was. I didn’t realize throttling was such a big problem.

I might replace my current battery, but it’s such a pain, and it costs more than my phone is realistically worth.

WTF is up with that title. Jesus.

I use Wayland now but there are still apps I run in X mode. Notably mpv and Firefox, because I cannot for the life of me configure them sensibly in Wayland, and I don’t want to write arcane KWin scripts just to get widow sizing/positioning to stay the way I want them on launch. I tried; it was extremely frustrating and still not quite functional.

Perhaps there are other window managers that would make my life easier. I haven’t tried many, but in principle, there is no way for the widow manager to know the correct size and location of new windows for arbitrary applications, so I doubt it. I consider this a user-hostile design choice in Wayland and I pray it will change in the future.

The majority of people will trail behind by 5-10 years, same as always. As long as a small minority at the cutting edge continue to use and develop better things, everyone will have access to them eventually.

They announced that they’re working with an OEM to support new non-pixel phones (perhaps even shipped with GOS).

The Pixel 9 series will be supported for another 6 years, and GOS support for the Pixel 10 is probably coming after Google releases QPR1 source. Hopefully there will be viable replacements by then.

Google is obviously going to keep making this more difficult but the rest of the world isn’t going to just sit still.

The actual paper presents the findings differently. To quote:

Our results clearly indicate that the resolution limit of the eye is higher than broadly assumed in the industry

They go on to use the iPhone 15 (461ppi) as an example, saying that at 35cm (1.15 feet) it has an effective “pixels per degree” of 65, compared to “individual values as high as 120 ppd” in their human perception measurements. You’d need the equivalent of an iPhone 15 at 850ppi to hit that, which would be a tiny bit over 2160p/UHD.

Honestly, that seems reasonable to me. It matches my intuition and experience that for smartphones, 8K would be overkill, and 4K is a marginal but noticeable upgrade from 1440p.

If you’re sitting the average 2.5 meters away from a 44-inch set, a simple Quad HD (QHD) display already packs more detail than your eye can possibly distinguish

Three paragraphs in and they’ve moved the goalposts from HD (1080p) to 1440p. :/ Anyway, I agree that 2.5 meters is generally too far from a 44" 4K TV. At that distance you should think about stepping up a size or two. Especially if you’re a gamer. You don’t want to deal with tiny UI text.

It’s also worth noting that for film, contrast is typically not that high, so the difference between resolutions will be less noticeable — if you are comparing videos with similar bitrates. If we’re talking about Netflix or YouTube or whatever, they compress the hell out of their streams, so you will definitely notice the difference if only by virtue of the different bitrates. You’d be much harder-pressed to spot the difference between a 1080p Bluray and a 4K Bluray, because 1080p Blurays already use a sufficiently high bitrate.

Does it do that even if you set it to “use device MAC” for the wi-fi network you’re on?

The exact location might depend on brand/OS, but in stock Android it’s in Settings > Network & Internet > Internet > gear icon next to active wi-fi network > Privacy.

The only thing I would use such a thing for is installing an ad blocker for the real world.

It’s been a while since I ran a full-fat VM. What’s the go-to these days?

Representation…in AI image generation?

The idea that this is something anyone should want is hard to wrap my head around.

If I could opt out of being deepfake-able, I would.

If you can’t afford backups, you can’t afford storage. Anyone competent would factor that in from the early planning stages of a PB-scale storage system.

Going into production without backups? For YEARS? It’s so mind-bogglingly incompetent that I wonder if the whole thing was a long-term conspiracy to destroy evidence or something.

Alien meaning “external”.

Electrical interference can come from all kinds of places, near and far. I guess technically you might get interference from other planets but I don’t think that’s what they meant. :) Solar flares are a possibility, though.

I think all it does is install the virt-manager Flatpak and then set a bunch of kernel arguments with rpm-ostree kargs ... depending on various hardware detections.

Gotcha. Yeah, that’s been a pain point for me on previous distros. On Bazzite they make it easy with ujust setup-virtualization. I’m not sure if that’s a one-size-fits-all solution but it suits my needs, at least.

I’m running Bazzite on my “everything” PC. Do you feel like Aurora has notable advantages? Seems to me that “gaming” distros like Bazzite are just ordinary distros with correct GPU drivers and a couple other niceties. I don’t see anything that detracts from productivity.

Still good if you want ROM support or are willing to wait a few months to pick one up for dirt cheap.

GrapheneOS only supports pixels, and LineageOS only officially supports a few more models. If you filter the official LineageOS devices list to 2024/2025 models, you’ll see Pixels, Moto G 5G, and OnePlus 12R. That’s it. Options are similarly limited for Calyx, e/OS, and others. So with most other recent phones, you’re stuck with all the stock bloat and spyware, or unofficial community builds.

Also, they’re dirt cheap in practice in the US. MSRP is a joke. For most of the year, you could get an unlocked, brand new Pixel 9 for less than the MSRP of the low-end 9a. If memory serves, it dropped under $400 at times.

Aside from that, they kind of suck. I wouldn’t even compare them to high-end phones. They are mid-range phones masquerading as high-end. Credit to Google’s marketing department, I guess.

Yeah, I’d rather come at it from the opposite direction. “Everyone censors, so this exactly the kind of shit your government is going to try to force on you in the future.” Everyone should care about this, if only out of self-interest.

China’s writing the playbook. Other countries will follow it sooner than you might think. This is everybody’s problem.

I have a bookmarklet to enable text selection on any web page that tries to block it that way.

Here it is for your convenience. Bookmark it and give a try on the linked blog post:

javascript:document.styleSheets[0].insertRule("* { user-select:text !important }", 1);

Can’t remember where I swiped that from. Probably some ancient StackOverflow thread.

I actually did this a lot on classic Mac OS. Intentionally.

The reason was that you could put a carriage return as the first character of a file, and it would sort above everything else by name while otherwise being invisible. You just had to copy the carriage return from a text editor and then paste it into the rename field in the Finder.

Since OS X / macOS can still read classic Mac HFS+ volumes, you can indeed still have carriage returns in file names on modern Macs. I don’t think you can create them on modern macOS, though. At least not in the Finder or with common Terminal commands.