

That’s a handy tool, thanks for posting it. Do you happen to know how the lists are sorted? It’s not alphabetical.


That’s a handy tool, thanks for posting it. Do you happen to know how the lists are sorted? It’s not alphabetical.


I’ll have to look into these. Thanks for the tip!


This was my thought as well, but I figured I’d put it out there anyway just in case there’s some kinda workaround/magic that I hadn’t heard about yet.


Thanks for the tip about JetKVM. Does the JetKVM device itself require an ethernet connection to the router or can it connect over wifi? (from what I can tell, it’s the former)


Thanks for confirming. Your understanding is correct, I just want a way to grab some “clean” screenshots or videos of the laptop while it’s in boot or BIOS parts of the system. I have a video capture card in my “cart” but thought I’d put this out there to the lemmyverse before I smash that “Buy” button.
EDIT: I ordered this video capture card, we’ll see how it goes!


Clown take. This comment would make a lot more sense if the original post were made by some cry baby throwing a tantrum after getting spawn camped; however, in this case, the original post is spreading the word about how and where a product’s dev team can be reached going forward (and how/where they cannot be reached anymore). We very much need these kinds of announcements.


Does your group ever use video calls and/or screen sharing?


So Mumble for voice chat and Matrix for text chat?


When you say traffickers joined your rooms to post spam, how did they find you? Is it like email where they can just try every possible email address at a particular domain or was your room posted publicly on your website or something and that’s how they found you?


Correct, they’ve been sealed since I filled them three weeks ago. Thanks for explaining a little more around how gas degrades.


Thanks for weighing in. It would be going into a Mazda 3 or a Honda CRV.
It just can’t. This candle is burning fast at both ends.
I hope you’re right b/c right now feels like the classic “market can stay irrational longer than we can stay liquid” type situation.


you can use one of a million Jitsi instances (Element has a publicly available one)
Is there a list of public Jitsi instances? I know about https://meet.jit.si/, but otherwise I’m stumped. Searching DDG for jitsi instances returns a bunch of results about self hosting.
Extremely. I’ve tried KDE flavors of various distros and one thing that trips me up every single time is the workflow for connecting to my hidden WiFi network. On Gnome and Cinnamon I can do this in a few clicks from the network icon in the task bar. On KDE I always have to spend several minutes fumbling my way around the network settings before I can start using it. Every. Single. Time. I don’t know why, it’s like my brain just works a certain way and because this is such an early and crucial step in setting up a fresh install, I’ve never been able to stick w/ KDE despite all the rave reviews it receives in these types of posts.
Did you run into any issues setting up dropbear or did you get it working on the first try?
I’m attempting to follow the same guide that you linked to, the only difference being that I haven’t configured a static IP (I don’t think this step is required). Every other instruction, I believe I’ve followed to the letter (for the new version).
Where I’m stuck is after copying the client’s public key to the server, updating initrd, rebooting, waiting for the disk encryption prompt, and issuing ping <server-ip> on the client (replacing <server-ip> and <port-number> with the actual IP and port number):
myuser@client:~$ ping <server-ip>
PING <server-ip> (<server-ip>) 56(84) bytes of data.
From <server-ip> icmp_seq=10 Destination Host Unreachable
From <server-ip> icmp_seq=11 Destination Host Unreachable
Unsurprisingly, I’m unable to ssh in from the client:
myuser@client:~$ ssh -i ~/.ssh/dropbear -p <port-number> -o "HostKeyAlgorithms ssh-rsa" root@<server-ip>
ssh: connect to host <server-ip> port <port-number>: No route to host
Since the server is a laptop, I can physically enter the decryption key on the server itself, and then go back to the client and ping the server successfully.
I have not attempted the steps described on the Debian wiki (networking setup or converting the public keys to PEM). Should I add IP=:::::eth0:dhcp to initramfs.conf? Any pointers on what I should check?
EDIT: I’m attempting all of this over wifi, in case that matters (I have a feeling it matters, but I’m not sure what I’m supposed to do differently).
EDIT 2: I found a guide from 2017 by Marc Fargas (Enable Wireless networks in Debian Initramfs). Also found this thread from 2021 on StackExchange (How can I enable wireless for a dropbear-initramfs), wherein somebody links to this GH gist (Sample files to enable wireless on Debian initramfs ). I’ll attempt to follow these guides and report back.


Thank you for posting this!
Reading Josh Meissner’s article about the acquisition of bike route sharing app Komoot has reinforced the importance of promoting and fostering community-owned services.
I’m not sure how to reach the owners of the https://furtherheights.com/ instance of wanderer, but visiting their website results in a 1033 error. The next instance I tried (https://trails.tchncs.de/) works as expected, though!
One of the great things about Linux is that if the user is still undecided after reading the paragraphs and looking at the screenshots, they can boot into the live environments and see for themselves which one is right for them.
Have you actually visited the download page that you linked? Because it has screenshots, explanations, whole nine yards.


I also posted this question in another comment thread, but is there no way for an app to say “give me communities only” or “give me users only” when calling the webfinger lookup thingy? Because if there is, then Mastodon devs could update the behavior on their side to depend on whether the name starts with @ or ! (the same way Lemmy apps do).
Is this the way to go for off-site backups w/ family? In terms of low power draw, uptime, etc.