I think they understand that. They are just calling out how outdated those password requirements are. In reality, a 32-character password made up of just alphanumeric characters is more secure than an 8-character password that also includes special characters. OP knows this fact, but they see that the website does not, so they are bringing that up here.
This is a great secondary keyboard to keep installed so I can quickly swap to it when I am doing something where I need a lot of special characters or complicated cursor placement or something. For general use, I tend to prefer Heliboard, but there are a few things that Unexpected Keyboard is just much better at.
I feel like most comments here are missing the point. I think you understand the concept of “first in, first out” and are just wondering if the “first” here should be closer to the door hinge or further. You want to establish a standard for your family, like “Always keep the oldest milk to the left and use that up first”, but are not sure what logic to use to determine if you should keep the old milk to the left or right .
In short, I say that the oldest milk should be placed further from the hinge.
My logic comes from my experience in the restaurant industry and actually arranging coolers. Optimally, you want to make it so that without thinking, in a rush, the first item a user sees is the oldest one. This is usually the item that is closest to the door/opening/user/whatever. In the case of storing items in the door itself, I would say that the further an item is from the hinge, the closer it is to the user.
Whatever you choose to set as your household standard, the most important part is to make sure all users in the household understand the logic and follow the same pattern. Realistically, it is pretty arbitrary where the “first” milk is kept. Everyone just needs to agree on a single standard.
There are times when you want to always keep a staple ingredient on hand and never run out. If you wait until you have none before you buy more, you may unintentionally end up in a situation in which you are unable to restock that staple in a timely fashion for some reason because some life situation arose. In cases of these staples, you will often end up with two units on hand: one that is partially empty that you are focusing on using up, and a second one that is full and waiting for the first one to get emptied before you start using it. Furthermore, depending on how critical the staple is and how much you expect to use before you have the ability to restock, you may actually want to have three or more units on hand. Maybe you are going to host a large family event and want to stock up so you have enough on hand for everyone. Maybe your grocery store is going to be closed on your normal shopping day next week, so you want to stock up so you do not have to go shopping that week. Maybe the store was having a sale on the smaller size, so you calculated that it was actually a better unit price for you to buy several of those than to buy just one of the larger size. Regardless of why you have more than one on hand, it is smart to set a standard for which one (left, right, etc.) should be the one you always use up first.
It’s a homebrew app, not a commercial product. There are plenty of homebrew apps that do things awfully on hardware they really shouldn’t run on. But someone made it just because they can.
How well does that work on an eink device that is designed to only need to refresh the screen once every several seconds? I assume an emulator like this needs to run at dozens of frames per second.
The guide is one of the best I’ve seen for this type of project.
I would have to award that to GrapheneOS. Being a web-based installer, GrapheneOS is able to add buttons that directly perform the major actions right in the guide itself. At each step, instead of having a link or something and saying “go here and do this”, it simply provides you with a button that actually performs that step’s action right then and there. It is incredibly straightforward. The first few steps do involve some prerequisite manual effort to get your phone ready and web browser configured. But once those two pieces are able to communicate with each other, the rest of the process just involves pressing the buttons in the order it tells you.
I thought the official install guide was just fine when I installed Koreader on my Kobo. I assume their official guide for Kindle is just as useful: https://github.com/koreader/koreader/wiki/Installation-on-Kindle-devices
Prusa is pricy because they make the de facto standards - including PrusaSlicer which is the base of OrcaSlicer/Bambu Studio.
PrusaSlicer itself is just a fork of Slic3r, anyway.
Why might Framework want to sponsor Rails World? Everything else in that list makes sense to me, as they are software projects that can have a direct effect on a user’s experience witn Framework hardware. But Rails World is all about a web development framework, right? That is like, three degrees of separation from Framework hardware. Donating to Rails World sounds to me like just a roundabout way to keep donating to Omarchy without having to say “we are donating to Omarchy”.
So you don’t have to give Reddit clicks:
Dutch hardware, French open-source OS, no Google services.
Apologies for repeating this in pretty much every topic on Fairphone and /e/OS, but there is a lot of misinformation about this. The Fairphone hardware and software is developed by a Chinese company called T2Mobile (this is no secret, it is in Fairphone’s documentation).
Switching to /e/OS does not really change that, because they use the same kernel trees, binary firmware blobs, and device trees maintained by the same Chinese company. So you replaced opaque blobs coming from a South Korean company to those from a Chinese company and Qualcomm (pick your poison I guess).
Besides that /e/OS does not really decouple you from Google. It starts talking to Google pretty much the moment you first set up the device [1]. The device will download proprietary Google SafetyNet blobs that run as part of the privileged microG. /e/OS also contacts Google for assisted GPS, eSIM provisioning, WideVine provisioning, etc. Then if you install certain Google Apps, /e/OS gives them elevated privileges, breaking the regular sandbox model. For instance, if you install Android Auto because you want to use it in your car, some of the dependencies (e.g. Google Maps) have privileged access [2]. It does not stop at Google, e.g. for speech-to-text, Murena does not have any scrupules uploading your voice to OpenAI (and hide it somewhere in the terms that no-one reads) [4].
Besides that, both Fairphone and /e/OS have a history of abysmal security. E.g., both used to sign system images with Android testing keys (which meant that malware could hide in your system image without you noticing). Fairphone is absolutely terrible at maintaining kernel trees - e.g. Fairphone 4 is still using a Linux version that has not been updated since 2020, Fairphone 6 is still on firmware blobs from June 2025 despite Qualcomm pushing out monthly fixes for vulnerabilities since then. The Fairphone 6 is also shipping a Linux kernel that hasn’t been updated since September 2024.
Both the Fairphone stock OS and /e/OS are way behind on Android security updates. The Android Security Bulletins are only backports of security issues marked high or critical. On those they are typically 1-2 months behind and the ASB vulnerabilities are already known for 3 months by vendors due to Google’s new security embargo system. That means that Fairphone’s stock OS and /e/OS are usually 4-5 months behind on patching high/critical vulnerabilities. It is even worse for other vulnerabilities, which are commonly used as part of exploit chains. /e/OS and the stock OS are still on Android 15. Since they do not roll out other security updates than ASBs, it means that they are now 1.5 years behind in non-high/critical security updates (since Android 15 was released in September 2024).
And then we haven’t even talked about shady things like the /e/OS App Lounge getting F-Droid packages [3] through a MITM server (cleanapk) for at least 6 years now that often serves outdated package versions. To make it more fun, they do not want to reveal who is actually maintaining this service.
Similarly, hardware security is not great. In contrast to your old S24, the Fairphone 6 does not have separate secure enclave. They only use TrustZone, which basically uses the same CPU/RAM for the TEE (the OS gets isolated by secrets running it in a VM-like environment). TrustZone is vulnerable to side-channel attacks and PINs are easily brute-forced (so, on Fairphone you probably want to use a long passphrase).
Some people will say: who cares, I’m not the target of a state level actor. Remember that in the days of Cellebrite, etc. device security is important to anyone who ever goes to a demonstration or crosses international borders.
I understand that everyone is looking for European alternatives, please think twice if you want to replace them by Chinese blobs, very outdated software, and a security disaster.
[2] https://eylenburg.github.io/android_comparison.htm
[3] https://forum.f-droid.org/t/e-foundation-using-f-droid-with-middle-man-website/7162
Factorio? League of Legends? World of Warcraft?
It takes quite a shitty attitude to look at a comment which clearly only asked for clarification and then turn it into a semi-debate. It’s almost impressive.
Its getting better. Doesn’t mean it’s the best yet.
Are you implying that a particular older version of GIMP was the “best” version and that current versions are worse? Or what are you saying?
I know your comment definitely isn’t implying that GIMP is currently still awful for editing text, but I am curious how long ago you are talking about. I have used GIMP as my primary means of making memes over the past few years or so (which often involves adding text), and have never felt inclined to use a different program just for text.
Like, the source code?
8 still has the 2k screen, 10 is a bastardized 1080p screen
Is there really any need for a screen that small having that high of a resolution anyway?
Something similar to this concept is great for enterprise environments. Imagine an employee at home using a basic thin client that just connects to a “mainframe” of a server that exists on premises and is running an individual VM or whatever for each employee’s thin client. That is already a widespread concept. But for a home PC, with that VM being run on the OS manufacturer’s servers? No, I don’t think anybody should want to pay for that.
Literally Black Mirror
The special episode “White Christmas”