

In the same video it’s pointed out that this product wouldn’t exist at all without the AMD chip. It’s literally built around it.


In the same video it’s pointed out that this product wouldn’t exist at all without the AMD chip. It’s literally built around it.


Specifically AMD said that it’s achievable but you’ll be operating at approx 50% of available bandwidth, and that’s with LPCAMM2. SO/DIMMs are right out of the running.
Mostly this is AMDs fault but if you want a GPU with 96-110 GBs of memory you don’t really have a choice.


They’re removing the ability to download ebooks from Amazon. You are still able to add books via USB to your device.
The piracy is because you could download your Amazon ebook, strip the DRM and transform it to a more generic format, and distribute it. Unfortunately this now means you’ll be unable to make copies of your books for “backup in case Amazon decides to remove access” purposes.


There was a fuss a while back since the released source appeared to be waaaay out of date compared to what was being used.
They came out and said that they wanted the usernames feature to be developed fully before it got pushed public. Which they then did.
I work for the UK government. Everything my organisation does is licensed in either MIT or OGL (https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/)
Developing code in the open really helps ensure you nail down your secure coding practices.


blocked part of url because I have Kagi rewrite url to redirect to my private Redlib instance
I had no idea this was a thing. Thats going straight on my self-host todo list.


Thing is, a cross post is nothing special. It’s a) a post with an identical link, and b) a post with “cross posted from…” appended to the body content.
It is still just a post. Lemmy (and k/mbin) just attempt to mask the fact there are multiple of them.
I don’t know if it can be done any better though, ActivityPub has quite a few quirks.
On my Pixel I long press at the bottom and then press on the code. I think it’s called google lens or something.


Very first line of the GitHub readme. As a support tool it’s mostly useless, endless similar or identical questions answered differently or not at all and none of it indexed by search engines for use on the web.
It’s an awful data silo / black hole that increases volunteer load.


allows it to make its tokamaks at only two percent of the volume of conventional tokamaks
Strap that into a tank, with - hear me out - legs, and we’re golden.


It’s unfortunate that (at least on the Bluesky side) an attempt at following a person doesn’t result in them getting a DM asking for that to be ok.
Which means following a person on Bluesky is not possible unless they’ve already opted in.
All I want to do is follow a couple of authors or content creators but none of them know what bridgy.fed is :(


With a small amount of effort and the use of https://github.com/nanos/FediFetcher and https://github.com/g3rv4/GetMoarFediverse you can mitigate basically all those issues. It’s still not perfect by any means but it results in a perfectly usable single user instance.
The first populates the replies of the home timeline posts you see (as well as profiles of people it finds in those replies) and the second pulls down all the content from instances you select for your followed hashtags (choose mastodon.social and you can guarantee you’ll see most all posts with those tags)


“…prohibits repair stores from repairing components on the mainboard. Instead, the entire component must be replaced…”
A flagrant disregard for the costs of e-waste on the environment. What a surprise.


There’s a huge amount of it on the fediverse right now. People are working very hard at getting rid, all of them volunteers, and in their own time.
I was experiencing similar issues under Manjaro. I couldn’t tell exactly when it happened but attributed it to a kernel or other update.
Are you seeing anything in dmesg? I was seeing kernel ring timeouts just after booting (I don’t know how it recorded them from before the freeze but it did). My searches led me to find that the Ryzen 5600 silicon had degraded just enough to be unstable. I could underclock it and it got a bit better but not fixed. In the end I replaced it with a new 5800 and the issues completely went away.