• Summarising articles / extracting information / transforming it according to my needs. Everyone knows LLM-bssed summaries are great, but not many folks utilise them to their full extent. For instance, yesterday, Sony published a blog piece on how a bunch of games were discounted on the PlayStation store. This was like a really long list that I couldn't be bothered reading, so I asked ChatGPT to display just the genres that I'm interested in, and sort them according to popularity. Another example is parsing changelogs for software releases, sometimes some of them are really long (and not sorted properly - maybe just a dump of commit messages), so I'd ask it to summarise the changes, maybe only show me new feature additions, or any breaking changes etc.

• Translations. I find ChatGPT excellent at translating Asian languages - expecially all the esoteric terms used in badly-translated Chinese webcomics. I feed in the pinyin word and provide context, and ChatGPT tells me what it means in that context, and also provides alternate translations. This is a 100 times better than just using Google Translate or whatever dumb dictionary-based translator, because context is everything in Asian languages.

The thing is though, with traditional forums you get a LOT of controls for filtering out the kind of users who post such content. For instance, most forums won't even let you post until you complete an interactive tutorial first (reading the rules and replying to a bot indicating you've understood them etc).

And then, you can have various levels of restrictions, eg, someone with less than 100 posts, or an account less than a month old may not be able to post any links or images etc. Also, you can have a trust system on some forums, where a mod can mark your account as trusted or verified, granting you further rights. You can even make it so that a manual moderator approval is required, before image posting rights are granted. In this instance, a mod would review your posting history and ensure that your posts genuinely contributed to the community and you're unlikely to be a troll/karma farmer account etc.

So, short of accounts getting compromised/hacked, it's very difficult to have this sort of stuff happen on a traditional forum.

I used to be a mod on a couple of popular forums back in the day, and I even ran my own community for a few years (using Invision Power Board), and never once have I had to deal with such content.

The fact is Lemmy is woefully inadequate in it's current state to deal with such content, and there are definitely better options out there. My heart goes out to @Chris and the staff for having to deal with this stuff, and I really hope that this drives the Beehaw team to move away from Lemmy ASAP.

In the meantime, I reckon some drastic actions would need to be taken, such as disabling new user registrations and stopping all federation completely, until the new community is ready.

Katamari Damacy - The objective is to roll a ball-like thing called a katamari, to roll up objects, and make the katamari bigger and bigger. You can roll up anything from paper clips and snacks in the house, to telephone poles and buildings in the town, to even living creatures such as people and animals. Once the katamari is complete, it will turn into a star that colors the night sky. Sounds weird, but it's super fun, trust me. Plus, it's soundtrack is kickass.

They actually didn't update it at all. The Notepad app that ships with Windows 11 (and recent Win10 builds) is actually a completely rewritten, bloated, UWP (aka "Modern") app. The old Notepad is now an "optional feature" that needs to be manually installed.

If people really felt strongly about this, we would've seen it being done already. Perhaps the state of Lemmy right now is "good enough" so folks don't care too strongly about a lack of a minor feature, or maybe they find it easier to just migrate to something like Kbin instead and still be federated to Lemmy. Or maybe they prefer to just write a simple patch, which can be maintained and distributed separately, instead of forking the entire code. Afterall, it's easy enough to make a fork, but a PITA to maintain one. Much more easier to just make a separate patch set or standalone utilities or something.

Also, frontend features, like the infinite scrolling one which was quoted, are basically non-issues, considering so many good alternative frontends exist, such as Photon, Alexandrite, mlymm, slemmy, etc. There's no rule you have to use the default frontend. In fact many Lemmy instances have decided to host these frontends on their own servers, and if they wanted to, they could easily switch to it and make it the default landing page.

A mission might send you to the other side of the vast starmap, but the actual travel time between systems is always the same (and the poorly explained fuel system, which is actually just your range, isn’t much of a limitation). When I discovered that so much of space flight is effectively a series of non-interactive cutscenes, it largely shattered the illusion of exploring a vast universe. It’s impossible not to compare Starfield to the way you freely enter and exit planets’ atmosphere in No Man’s Sky, so it’s a bit of a letdown every time you see a planet and remember it’s just a picture of a planet you’ll never be able to reach by flying toward it. It’s something that happens a lot.

The fact that you can't fly over to planets and land, and that you get around the vastness of space by simply fast traveling, is disappointing. This seems less space-y, and more like Fallout-y to me.

As someone who isn't really into FPS games these days, I think I might give Starfield a skip.

All valid concerns, but if you really wanted to, you could roll your own home automation setup using something like a Raspberry Pi, and optionally Home Assistant, and keep it all offline so that it's safe from hackers.

That's highly unlikely. Samsung phones aren't very custom-ROM friendly, especially if you're going for a recent device like OP did. Also, Samsung devices use a hardware eFuse which is blown up the moment you unlock the bootloader, which permanently voids the warranty, and permanently disables some Samsung features, which also reduces the resale value of the phone.

So, I wouldn't advise rooting/ROMming a Samsung. Best to get something like a Pixel instead.

• Laptop: Framework. Modular hardware, easy to upgrade and repair.
• Smartphone: Pixel + GrapheneOS.

Also, the article doesn't mention anything about nanoplastics, which are far more dangerous. Nanoplastics have a larger surface area, which makes them more reactive - they can also penetrate cells, and cause damage to DNA, proteins, etc.

I have the RG351MP, it's pretty nice. Solid aluminum too, so it doesn't feel cheap, but not really ergonomic for long hours of play. That's fine though, because this is the kind of device you carry around in your pocket for a short session during your commute, breaks etc. There's quite a few choices of opensource firmware that you can load onto here, and most of them have this cool app called "portmaster", which consists of native games ported over from other platforms - such as Prince of Persia (DOS), 3D Space Cadet Pinball (XP) etc, and they run really well.

My main issue with the 351MP is that although it claims to be able to emulate the Dreamcast and N64, it actually struggles with most games from those two consoles. Most notably, I wanted to play Rogue Squadron II (Dreamcast) on it and it was unplayable, the specs were too weak for it unfortunately. Which broke my heart, and I quickly lost interest in the device. I wanted a device that could comfortably emulate all consoles upto the Dreamcast, and the 351MP can only realistically handle upto the PS1.

I started looking for alternatives, and found similar drawbacks with most of these devices, none of them were capable enough to comfortably emulate the Dreamcast - unless I bought a pricey high-end device like the Aya Neo or the Steam Deck or something.

And then I realized, I could just get myself a cheap Android device from eBay (like with a bad ESN or some other non-impairing fault), pair it with a telescopic controller, and it'd be way cheaper + have better specs. So I did just that, got myself a cheap OnePlus 9 with a bad ESN for only $150 (SD 888, 8GB RAM), paired it with a Gamesir X2, loaded Dolphin emulator on it - and I was finally able to play Rogue Squadron II in all its glory - even managed to get an HD texture pack for it and it was glorious.

Eventually, I got myself a Galaxy Fold 4 as my main phone, so I didn't need the OP9 any more - my Fold 4 had better specs, plus the large 4:3-ish screen made it perfect for playing those old games.

As for my old RG351MP, it's still lying around, but I think I might sell it. The only advantage it has against my current setup is portability, but since I carry my Fold 4 everywhere, it's not really that big of an issue. Sure, I can't carry my controller everywhere either, but I'm not that desperate to want to be able to game everywhere and all the time (with physical controls).

TL;DR: Before buying a handheld, consider whether you really need that portability + physical controls, if you don't need it everywhere, then your phone (+ controller) could do a better job than most of these.

Not possible. At least, not yet. Two main reasons for this:

1. There is no standardized BIOS/UEFI equivalent in ARM, as a result, the boot process in every ARM system differs in general. The only "standardized" boot process you'd see would be for that particular type of system from a single vendor, eg the way most Android devices boot is generally the same - although even in Android, some manufacturers make their own changes, for instance Samsung introduces their KNOX into the picture, some devices use the A/B partition system but some dont, etc.

The lack of a standard boot/initialisation process, and the lack of a hardware auto-detect feature, means you can't just mix and match components like you'd do in a PC - the bootloader wouldn't know how to initialize those hardware bits, heck, it wouldn't even know the hardware existed unless you manually defined it somewhere - this is done using something called a Device Tree, which, although is a standardized format, still needs to be manually created, and also, the bootloader used needs to support this in the first place (like UBoot, but not all ARM systems use this).

2. The other reason is lack of standardized hardware. In the x86 world, PCs have a rich ecosystem of standardized components, from motherboards to graphics cards, which have evolved over decades, and standards were developed organically over time - and agreed upon by other manufacturers. Sometimes these standards were made or guided by special interest groups / consortiums / other regulatory boards etc. ARM lacks this.

But it wasn't always like this in the PC world, back in the early days of personal computing, you had different types of PCs and hardware that were basically incompatible with each other, similar to the ARM systems of today. It was mainly due to the popularity of IBM PC, that things began to change. Unlike many other computers of its time, the IBM PC had an open architecture. This meant that its specifications and designs were made publicly available, allowing third-party manufacturers to produce compatible components and peripherals. One of the key features of the IBM PC was the Industry Standard Architecture (ISA) bus (the precursor to the PCI bus), which allowed for the addition of third-party cards. This established a standard for expansion that was widely adopted and emulated.

As IBM PCs gained in popularity, other manufacturers started producing "IBM compatibles" or "PC clones." These machines were designed to be hardware and software compatible with the IBM PC. Companies like Compaq successfully reverse-engineered the BIOS, allowing them to create systems that could run software designed for IBM PCs. Also, IBM's choice of using Microsoft's MS-DOS as the operating system was crucial. As DOS became the de facto OS for PCs, software developers focused their efforts on creating software for this platform. This drove further hardware standardization as manufacturers aimed to produce hardware compatible with MS-DOS and its applications. As the industry grew, this lead to the creation of more standards, some of them competing, some losing out due to lack of popularity etc. The result is the PC world that you see today.

ARM lacks all of this rich history. Where ARM is at right now is where PCs were at before the introduction of the IBM PC. We need to go thru all those motions again to be able to build your own PC. But I don't see this happening any time soon, in fact it's doubtful if it'll ever happen, since the trend these days is for vendors to build closed, unrepairable, unserviceable systems - so that you get locked into their ecosystems, so that you're forced to upgrade your entire device just to get say, more RAM or whatever. And unfortunately, even PC manufacturers are picking up on this trend, as we're seeing with laptops.

So unless something changes drastically, like some big manufacturer stepping forward to create an open ARM PC and ecosystem, being able to build your own ARM PC will remain a pipe dream.