Please correct my English.
The Lemming formerly known as /u/SatyrSack@lemmy.one
Agree. For things like semantic versioning, in which “1.20.1” and “1.2.1” are two different things, you want to pronounce them “one point twenty point one” and “one point two point one”, respectively. But that is a bit of an outlier. File size should be pronounced “normally”, because “1.20” and “1.2” are the same value.
SUPERHOT moves at your pace. Though it definitely does make you feel superhuman, just in a different way.
Maybe this was not supposed to have been posted until April fool’s day. Silly Zorin was too early for the joke.
You don’t have to use a “classic email server”, or even link your account to your current email address at all. The default onboarding procedure actually creates a new anonymous account for you on the default chatmail server. Reading through the site, I can’t actually even tell why someone would want to use their preexisting email address.
Delta Chat is not associated with your email account, as far as I can tell. Am I wrong?
HTML predates XML by several years.
Kongratulations
*KOOL
Goa’uld
Yeah, I cannot find it documented anywhere. Which is probably on purpose, to avoid malicious actors finding out ways to bypass it. But you can find plenty of users on Reddit and whatnot complaining about how they are not getting registration emails for whatever services in their new Proton email accounts, then it suddenly works just fine when they try again ten days later.
Is your Proton account new? I believe Proton automatically filters out verification emails like that until the account reaches a certain age. As a means of restricting users from creating an anonymous throwaway Proton account to use just to sign up for another service to abuse it. Verification emails will not appear in your spam/junk/deleted folder or anything. You will just not receive them in any way at all. I am not sure how many days it takes for that restriction to be automatically lifted.
Completely aside from the blob issue mentioned, the Tails team has recommended against using a multiboot utility like Ventoy to install Tails. Ventoy works fine for basically any other operating system (again, aside from the blob issue), just not Tails, which is what this post is about.
The linked article lists Raspberry Pi Imager as an option for writing Tails from macOS, and that is also available on Linux and Windows.
https://www.raspberrypi.com/software/
Though the site only shows how to install on Ubuntu, the GitHub repo for the tool does have an AppImage that should work on any distro.
Any time I’ve tried uploading them, they are converted to jpg files. The only way I’ve been able to include them is by referencing images that are already hosted somewhere.
I know that some instances have server-end logic in place to downscale uploaded images, or convert GIFs to WEBP, etc to reduce file size. I wouldn’t be surprised if your instance just converts all GIFs to a static JPG for some reason.
OpenSCAD?