It’s easiest to just register a domain name and use Couldflare Tunnels. No need to worry about dynamic DNS, port forwarding etc. Plus, you have the security advantages of DDoS protection and firewall (WAF). Finally, you get portability - you can change your ISP, router or even move your entire lab into the cloud if you wanted to, and you won’t need to change a single thing.

I have a lab set up on my mini PC that I often take to work with me, and it works the same regardless of whether it’s going thru my work’s restricted proxy or the NAT at home. Zero config required on the network side.

This shouldn’t even be a question lol. Even if you aren’t worried about theft, encryption has a nice bonus: you don’t have to worry about secure erasing your drives when you want to get rid of them. I mean, sure it’s not that big of a deal to wipe a drive, but sometimes you’re unable to do so - for instance, the drive could fail and you may not be able to do the wipe. So you end up getting rid of the drive as-is, but an opportunist could get a hold of that drive and attempt to repair it and recover your data. Or maybe the drive fails, but it’s still under warranty and you want to RMA it - with encryption on, you don’t have to worry about some random accessing your data.

There’s no harm at all in moving the unallocated space, assuming of course, that your partitions are healthy and have no existing issues (GParted would check for this anyways).

If you want to resize your btrfs partition you can save a step by moving the unallocated space to the slot before the btrfs partition and then reisize the btrfs partition, but it wouldn’t make much of a difference anyways because the btrfs partition would need to be moved left regardless.

Btw, questions like these are best posted to a Linux community, like !Linux@lemmy.ml

I haven’t developed a desktop app in ages so I’m probably not the best person to ask this, but my understanding is that if you develop a modern UWP app, then it’s automatically S0 aware, but you can also make use of WinRT APIs to execute background tasks during modern standby. The user can also choose whether or not to allow this activity.

I’m not sure if the WinRT APIs can be called from a regular Win32 app though. For Win32 apps, as far as I’m aware, they should get suspended by the DAM automatically (and background services may get throttled), but Windows may choose to unsuspend/unthrottle these apps if it thinks some critical activities are happening. I never looked into what it deems as a “critical activity”. Personally though I always disable S0 so that my laptop suspends as you’d expect it to.

Bottomline is, if you’re making a UWP app it should all just automatically work, maybe look into the WinRT APIs, and if you’re making a Win32 app you need to look more into the DAM. There’s some info on that here: https://learn.microsoft.com/en-us/windows/win32/w8cookbook/desktop-activity-moderator

Why don’t laptops have proper low power states

Actually, they do, it’s called the “S0” low power state, and it’s part of the ACPI standard. Microsoft calls this “Modern Standby” in Windows (and “suspend to idle” in Linux) , and it’s pitched to do exactly what you’ve described.

The only problem is, the implementation sucks. Most users actually hate the S0 state because it consumes so much power - on some laptops, even the fans may continue to run on S0, and your laptop may overheat if you’ve closed the lid and chucked it in a bag, and it’s in the S0 state.

Also, because Microsoft and Intel have been pushing this so much, the “standby” mode now defaults to S0 instead of S3 (which is full suspend-to-RAM). So many users actually actively seek to disable S0 and go back to proper S3 standby, via registry hacks etc.

So why is S0 so bad? Part of this is due to the limitations, long history and the variable nature of the x86 platform. All the power-saving stuff was implemented as an after-thought - both at the hardware and software levels. Whereas ARM, at least the modern ARM ecosystem, was developed with mobile usage and power saving from ground up. An x86 PC is also made up of components from disjointed manufacturers, and we need all those components to implement the same standards so that it all works well as expected. So for instance, if a particular component isn’t capable of entering a low-power or active standby state, then it won’t - and you can’t do much about that, unless you’re Apple and have a tight control over the ecosystem.

The second half of the problem comes with the software. All applications must be modern standby / S0 aware, if not, one of two things will happen: that app will keep the system awake, or the app will get suspended by the Desktop Activity Moderator (DAM). Either way, the app must be capable of running in the DRIPS phase (deepest idle runtime platform state), which rules out most Win32 apps (basically almost every app that’s not on the Microsoft Store).

Finally, the reality is that most PC users don’t care about modern standby regardless - and why should they, when they’ve all got smartphones, which handles notifications well? Also, hardly anyone does large file downloads these days, and the people who do still download, wouldn’t care about doing it while on battery (and if they do, they can take manual actions to lower the power consumption, such as switching to a power saving plan and turning off the display etc).

Ultimately, most people would expect a laptop to go into a fully suspended state when the lid so closed and they’re on battery, because if they’re on battery the #1 concern for them would be the battery life. So most people actively seek to disable S0 and see it as a hindrance.

Unrelated, but anyone know if they fixed the problem of not being able to add the ‘+’ button to the macro sequence?

The same can be said of all the paper/cardboard being used in the food industry - paper straws, cardboard takeaway containers etc are all lined with PFAS and other “forever” chemicals that leach into your food. We really need a law to force companies to disclose the composition of products that come in contact with food.

Desktop users exist

So do Desktop tools like Flameshot, which can directly upload to image hosts and copy the URL to the clipboard which makes it easy to share images, and there also exists third-party Desktop web-clients such as Photon, which could be updated with that functionality as well. But with Lemmy itself being open source, it wouldn’t take much effort to modify the code to use a third-party image host.

have a history of deciding to forbid hotlinking

There are plenty of hosts which do allow hotlinking though, like imgbb.com

history of suddenly deleting all (e.g. PhotoBucket) or some (e.g. Imgur) images .

Not a big loss, IMO. Lemmy isn’t an image hosting nor an image-centric site, it’s a text-heavy forum at first instance, and anyone posting images are encouraged to provide text alts for the benefit of blind users, so images not persisting isn’t a big deal.

If image persistence is really that important, there are other services which are better suited for that, such as Pixelfed. But in the first place, I wouldn’t rely on some random Lemmy server, which is vulnerable to DDoS and other attacks and could go down at any time (also why the importance on decentralization - no single instance is infallible). I mean, when there’s no guarantee that a Lemmy instance will even be there tomorrow, is there really a need to worry about image persistence?

This can be easily implemented client-side, like how third-party Reddit clients have been doing for years, by uploading to the likes of Imgur. Shift the responsibility away from the Lemmy server and onto dedicated image hosts, who have the storage to spare, plus manpower/policies to deal with illegal content.

Or just disable image uploads completely. We got by on Reddit without any built-in image hosting functionality for over a decade, so Lemmy should be fine without it as well - especially considering that we don’t really have many image-heavy communities, besides the NSFW instances. I mean, storage costs money you know, and with Lemmy being run by volunteers, it makes even more sense to get rid of image hosting to save costs.

• Star Wars: Galactic Battlegrounds (with the Expanding Fronts mod)
• Age of Empires II HD
• Serious Sam HD

Nice, but I wonder if they plan to switch to GPL, or stay with MPL. No mention of that on the website.

Eh, as an IT guy, I love seeing computer screens on TV. They’re either a good laugh, or they can be quite interesting.

Among the interesting/iconic interfaces:

• The 3D “Unix” system in Jurassic Park
• The Matrix
• Minority Report

I also love seeing vintage/fake-vintage interfaces in movies, such as SolarOS (a take on Solaris) in Tron: Legacy

and all the hilarious ones such as the infamous “I’ll create a GUI in Visual Basic to track the IP address” scene in CSI.

Also, here’s a bonus link for you retro fans: https://www.windows93.net/

Woah, wasn’t expecting to see pic of my hometown on .world!

become so inconsistent

Your title implies that it was consistent at some point, but it wasn’t. Android updates were never consistent. In fact, it’s actually become more consistent in recent years, since the introduction of Project Treble. Most mainstream flagships now offer 4 years of updates, with some manufacturers even offering 5 years (Google and some Samsung flagships).

I’d trust some random people running an activity pub server just as much as I’d trust Meta with my personal photos: I won’t.

I’m pretty sure Pixelfed wasn’t intended to be a place to share your personal photos - it’s meant for sharing photos you want to share with the public - could be a circle of friends or the whole world. Photos like pictures of your cats, food, landscapes etc. It’s a place to share photos with friends, or a place to connect photographers with other photographers.

There’s always a tradeoff in computing between security v/s performance/overhead, so the value of it depends on your threat model, and the attack vectors you’re expecting.

Anyways, RAM encryption is generally “available” in various forms, depending on the mobo, CPU, software used etc, but it’s not commonly enabled/used. Most AMD boards (at least, mid-range and above should) have an option in the BIOS to enable Secure Memory Encryption (SME). This allows the OS to selectively encrypt memory pages, making use of a hardware AES engine that sits outside of the CPU.

There’s also Transparent SME (TSME), which encrypts the entire memory and works completely independent of the OS and software. Usually only high-end/workstation boards have this, and it also requires a Ryzen PRO CPU. TSME also has a much lower overhead, I recall reading somewhere it’s something like only 5%.

I believe Intel also has something similar, but I never looked into it.

AMD have a whitepaper available with an overview on how this stuff works, if you’re interested: https://www.amd.com/system/files/TechDocs/memory-encryption-white-paper.pdf

Okay, so everyone’s saying it’s cute and all, but is there an actual practical use for this, as a grown-ass adult? I mean, sure it’s pocketable and all but if you’re thinking of portability, that would require your phone/tablet case to have a stand of some sort, which may not be an option (especially if you’re commuting). So either this thing has a very niche use case or I’m missing something…

Cool, but can you spot the difference between I and I?

It’s the opposite for me, private mode causes more Cloudflare prompts (and Google captchas).