Like the other replier and GP, my Linux and Mac desktops run for months at a time without a restart. I only restart when there’s a software update that demands it. I don’t have much experience with modern Windows, but I expect that’s the norm from a modern OS.

If you’re running into runaway resource issues like this then you may want to spend a few minutes hunting them down and maybe replace the programs responsible. Daily restarts shouldn’t be necessary.

Apparently not in Windows settings:

If the BIOS says it supports Modern Standby, Windows takes it at its word and completely disables the ability to enter S3 sleep (classic standby). There’s no official or documented option for disabling Modern Standby through Windows, which is incredibly annoying.

Side note: for a while, there was actually a registry setting you could change to disable Modern Standby on the Windows side. Unfortunately, Microsoft removed it, and to my knowledge, has never added it back.

I’m not a Windows user, so I can’t confirm one way or the other, but toward the end of the end of the article the author gives vendor-specific instructions for disabling the S0 Low Power Idle capability from BIOS.

Alex Russell is a good read on React. His position gives him a broad view of its impacts and has kept him from being sidelined. This Changelog podcast is a decent distillation of his criticisms – it was recorded earlier this year, a few days after his Market For Lemons blog post.

(Sorry for the late reply! I’ve been a bit swamped lately and away from kbin.)

“Good vibes only” seems to be embedded in the culture of web development today. Influential devs’ Twitter accounts have strong Instagram vibes: constantly promoting and congratulating each other, never sharing substantive criticisms. Hustle hustle.

People with deep, valid criticisms of popular frameworks like React seem to be ostracized as cranks.

It’s all very vapid and depressing.

Thanks for this. I skimmed the proposal doc itself and didn’t quite understand the concern people have with it – most of the concerns that came to my own mind are already listed as non-goals. The first few lines of this comment express a realistic danger that’s innate to what’s actually being proposed.

The Verge article is paywalled for me, but the screencaps Alex shared in his toot don’t really support his summary. The article mentions that Threads can import content from Mastodon as an example of the sorts of things ActivityPub supports, and that’s about as close as it gets.

And then there’s this:

The company is planning to create a roundtable for administrators of other servers and developers to share best practices and work through problems that will inevitably arise, like Meta’s server traffic putting strain on other, smaller servers.

Emphasis mine. How would Meta’s server put strain on other, smaller servers if it’s not federating with them?

I’m fully willing to believe Meta wants to EEE ActivityPub, but this particular claim doesn’t seem to check out.

Anyone found any decent wireless ones with replaceable batteries? I was interested in the Fairbuds XL but it’s not well reviewed.

For a while I had a pair of Sennheiser TV headphones that took AAAs, but they required a dedicated transmitter and weren’t great for music anyway.

This reply’s interesting:

How can data licensed under the CC-BY-SA licenses (that SO content is licensed under) be “misused”? The license explictly allows others to do essentially anything they want with the data as long as attribution is given, in particular profit off of it.

When SO content is applied as parametric knowledge I’d expect the outcome to fail both the “BY” and the “SA” clauses, since model interpreters can’t provide attribution for it and their output won’t share the license. That’s true even if output is considered public domain: CC-BY-SA content can’t be moved into a public domain equivalent license. It seems practically indistinguishable from using any other in-copyright content as training material.

None of that’s to say SO is right to stop data dumps. It feels like they’re trying to find a technical solution to a legal problem, perhaps even one that rises to criminality on the part of Open AI and others?

threadiverse

I like this. I keep seeing and saying “Lemmy/Kbin” which is awkward in all sorts of ways.

“Threadiverse” has a good denim feel to it.

We have https://kbin.social/m/mechanicalkeyboards on kbin.

If you’re on a Lemmy instance then the best way to add it is to paste the full URL into search while logged in. It won’t show up right away, but if you wait a few seconds then it’ll appear in the search results. Every now and then it gets stubborn and you have to refresh the search results page to see it.

You can! To subscribe to something on another instance just go to the general search and type <community name>@<hostname>

For example here’s a search for ffxiv@possumpat.io

I agree with your parenthetical strongly enough to rule out a typo.

This announcement lists things that Reddit will humor, for now, and as a way of cheaply outsourcing niche and difficult problems. It clarifies that everyday third party apps were never intended to have a future with the platform. They’re simply an obstacle for Reddit’s most convincing path to revenue.

I might even have forgiven Reddit if it had said so up front, but the story they’ve been trying to spin – with prices that just happen to be orders of magnitude in excess of anything devs might afford – is outrageously insulting. I’ve never had my trust in a brand demolished so thoroughly so quickly.

It’s a fascinating idea, but it’s reading a lot into a small effect on a very small study group.

The authors also don’t seem to dwell much on the effect that novelty itself has on study outcomes. This is a common problem with A/B testing: introducing any divergence from what’s familiar can draw participants’ attention and affect outcomes. “Like” and “Dislike” buttons are familiar for anyone who’s spent time on the internet, but “Trust” and “Distrust” buttons are novel and will be treated more carefully. If they were used widely then we’d eventually develop a kind of banner blindness to the language, and their effect on discernment would be further weakened.

This approach could also overindex comments that express risk and uncertainty. Well-worded concerns and calls for “further study” are a time-honored way of disrupting progress (never forget the Simple Sabotage Field Manual) but often sound trustworthy.

Which makes this comment rather ironic.