Signal doesn’t send anything in the payload. They just use it to wake the phone up and then download all messages that are waiting to be delivered through the usual encrypted means. All Google knows is that something happened at that time. They don’t know anything else.
But they only instruct Signal to wake up and download whatever is waiting. They don’t contain the message contents.
I miss being able to use the proximity sensor on my N900 as a button.
Sir, this is a Wendy’s memes community.
Although the amount of bad punctuation and emoticons might shift this into shitpost territory.
Damn. Yeah, that’s bad. Have you tried it with other compositors like Gnome?
Curious if that happens in BSD as well.
I can’t even see what the bug is supposed to be from the video.
Honestly, that’s what most web API’s are. You are just pushing data around. The “hard” part is that everyone has their own opinions on how it should be formatted.
And of course the minor inconvenience of having to give the user a way to make data entry easy, convenient and consistent.
But deep down it’s all spreadsheets. The faster you can wrap your head around that the easier programming is for you.
I’m more concerned about the Umbrella logo.
I’ve got a really obscure one.
Anyone here heard about FLI4L? Floppy ISDN for Linux? Built from the ground up to be usable on your really old PC as a router. Originally it fit on a single floppy disc and was able to turn a 386 into a modem or ISDN router. Later they added the ability to route between LANs and DSL.
By now the requirements have been raised to super beefy 586 PCs. It probably doesn’t fit on a floppy disc anymore.
Sure, but having /boot on BTRFS won’t save you if the bitrot fucked up your ESP.
Good luck, when EFI has to live on FAT32.
For anyone reaching for the downvote button:
Systemd-boot is completely independent from systemd init. You don’t have to be running systemd to use it. It’s a really really simple EFI bootloader. You just give it the location of your kernel and initrd and boot options and it does the rest.
Switch and Click had a video about that recently: https://youtu.be/M9qJI2u_be0
Reminds me of the time I was working on something for Mercedes but they couldn’t supply me with the computer for testing. I had to go into the super cramped actual car that was parked in a super expensive secure garage.
Left the company and when I went there for a visit I saw that the new guy actually got to test and develope on a computer they had ripped out of a car.
I was and still am on HDD. The CPU was upgraded as well. I migrated to a new server.
The main culprit was the database. As far as I’m aware Lemmy is missing some indexes and due to the ORM they used didn’t always have optimised queries. Now with 64 GB RAM the whole database (almost 30 GB) fits in there fixing most of those issues.
The real fix will probably come with Lemmy 1.0. They radically changed the database layout and queries.
Image proxying wasn’t bad for performance. Just storage space. It was growing really really fast. Now that only I am using it to host the pictures I uploaded it is still much too large (24 GB). But its directory structure is so convoluted that I can’t really debug it. My stuff really shouldn’t be taking up more than a few hundred MBs.
I am the only one using this instance. I am subscribed to a hundred communities or so. I am always pretty up to date with my Lemmy versions.
I wish that was it, but what are those unnamed 64 bit Linuxes supposed to be?
And those channels have been talking about Linux for months. Why now such a sharp increase?
Looks sus. Probably a fluke.
RAM. Maybe 32 would have been enough but 64 cost as much as 32 so that decision was easy.
The biggest advantage of Docker is that it’s a little bit easier to manage all the dependencies of a service. And often enough the Docker images come from the official vendor and thus should in theory be configured optimally out of the box and give you timely updates.
But if you don’t have any problems with your current install I wouldn’t touch it.
Bold strategy.