![](https://fedia.io/media/ee/c8/eec82eb52f8a52598f0d92ed014a68a9ad9239b087cf401e8013d9edac1e565f.jpg)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
There were some tools available to make it easy. For instance, to get a modeline that might work for your monitor just fill out this simple form.
There were some tools available to make it easy. For instance, to get a modeline that might work for your monitor just fill out this simple form.
My linux experience:
1993 - Hey, there’s a new Unix-like thing for the PC. You can check it out down at the university computer club.
1994 - Wow, I finally managed to get X running
1996 - It was somewhat normal for more nerdy software developers to run linux full-time on their desktop at work.
1998 - Linux was taking over servers to the point where you rarely saw Solaris, HP-UX, AIX around any more.
2002 - Everyone agreed that linux was pretty much ready to take over the desktop as well.
…more fancy such as using tar -X, which works for me. I’d never actually tried it before. The ‘weird globbing’ it uses is regular expressions, which are worth learning how to use. Run grep "$expression" $_tmpfile
where $expression is a line from your exclude file to see which files it’s going to match and exclude.
I don’t know what fd does, but at a guess maybe what you’re missing is that tar includes all the files in directories you give it? So if you exclude ‘foo/bar’ but include ‘foo’ then foo/bar will be in your tar file.
What I do is basically tar cf `ls ~ | grep -v $files_to_exclude`
but if you want to exclude something that isn’t a top-level directory you’d need to get slightly more fancy.
Suddenly I’m worried about AI’s energy draw. “6 percent of global electricity” is not a small amount of electricity.
The model year and other relevant info is found in the first part of the VIN. There’s no legit reason for it to demand the whole thing, which it does.
Further searching turns up the information that “federated” Bluesky PDS instances are limited to ten user accounts each, and API usage limits which may constrain things further. So that would explain why there aren’t any big ones.
So far as I can tell they do all still “federate” through the central server, not directly with each other. So there being not much point in it may also explain why it hasn’t caught on.
Almost as bad as Threads, really.
Well, what’s a popular server? Are there several big ones? Sorry, but I really don’t understand why the answer isn’t turning up in web search results.
PS: Are you sure it isn’t just people who’ve done the “set your domain as your handle” thing but even so are still on the central one? Because even if they have made some small progress towards decentralization they absolutely have not gone so far that there isn’t still a central one.
Is it really? Seems hard to find out. Anyone have a list of Bluesky servers other than the central one with open signups?
tl;dr: Here’s everything you need to know about the fediverse, assuming you’re never going to use it. Mastodon, Bluesky, Threads, Friendica. Now, back to our regular coverage of all the biggest social companies, including TikTok, Facebook, Instagram, Twitter, Snapchat and Reddit, as well as funding and acquisitions of new social startups.
If it’s that bad, could you maybe give people a hint as to why we’d want to watch it and what it has to do with linux?
I’d not yet call it failed, but it’s not yet fully succeeded either. To my mind, one impediment is something that lemmy.world shares with today’s reddit: If you look at the front page it’s 99% memes and images. That’s the first impression people get, and it probably drives away a lot of people who might want anything else. We need those people to make more text-based communities come alive, if it’s to evolve into anything like the old reddit.
I mean obviously there are lots of people who do mostly want to see memes and that’s fine, but I think it’s getting to the point where it might be useful to have an option that filters out all posts that are just a title and an image.
Sure, the project is already bloated with so much complexity that what’s the harm in adding a little more? If you’re genuinely confused about it, see the entire rest of the Internet for details.
It has some advantages. It can be configured with simple text files and normal filesystem permissions. The sshd code is mature and has a proven record of good security. It doesn’t add yet another thing to systemd that has no business being part of systemd.
Default threat model: Some malignant demon, who is at once exceedingly potent and deceitful, has employed all his artifice to deceive me
deleted by creator
#!/bin/bash
head -$[$SRANDOM % `wc -l /usr/share/dict/words | cut -f1 -d' '`] /usr/share/dict/words | tail -1
If it’s more than none at all that’s pretty good. But adhering to open standards is also a factor in how we should judge these providers which goes beyond that.
technically it doesn’t break e2ee
** for some unorthodox definition of e2ee
If the “endpoints” are defined as being somewhere outside the end users’ control, because for example the client software they have is designed to betray their secrets, then the system is no longer end-to-end encrypted in the way that both cryptographers and normal people would usually understand the concept.
I’m not a fan of the idea at all, but come on, it can’t really be that bad. There’s got to be somewhere you can tell it what environment variables to use. Probably something like
run0 systemd-edit /usr/system/systemd/systemrun/run0-environment --system-default=system