Indeed, protocol is independent from implementation language, but that isn’t the question at hand.
Do you know whether Beehaw will still federate with the lemmyverse (and therefore the rest of us) after moving to Sublinks?
Indeed, protocol is independent from implementation language, but that isn’t the question at hand.
Do you know whether Beehaw will still federate with the lemmyverse (and therefore the rest of us) after moving to Sublinks?
That could also mean client API-compatible, so Lemmy apps would work with it, which doesn’t address federation.
Will it federate with Lemmy? I would miss you folks.
I find this to either be a lie or self inflicted.
“I’ve never experienced what you describe, so it must be either imagined or your own fault.”
I’ve seen this nonsense over and over again in communities of all kinds, most often in tech forums (where there are always a few participants suffering from a big-fish-little-pond effect). It’s a very rude and foolish bit of human behavior.
There are more things in heaven and earth, Horatio, than are dreamt of in your philosophy.
Who cares? It’s run by reactionary incels, transphobes, and racists.
Wait until you find out who runs Lemmy development.
Linux user here. I don’t know of an open desktop calendar app that supports the protocol I need (CalDAV) without being one or more of:
The best compromise I’ve found so far is Thunderbird. It is bloated, but less so than any Electron app I’ve used. I find the UI annoying, but tolerable for lack of a better option. I’m thankful for an open, cross-platform tool that gets the job done, but I wish I had one that was lightweight and pleasant to use.
It would be nice to see some new work in this area. It’s a similar situation with email apps.
I imagine he wants to avoid dependence on fuel suppliers, or pollution.
How to turn them square?
I don’t think yt-dlp has built-in image cropping, so it’s just going to download thumbnails in the resolutions provided by the server. (See the --list-thumbnails option.) To crop what you download, consider a tool like (ImageMagick)(https://imagemagick.org/).
That explanation is fair enough but the headline is red meat the the EV disinformation brigade.
It’s funny how words affect people differently.
Not long ago, I posted a short, precisely-stated comment mentioning an observed fact that I had verified with a relevant authority. When I later checked in, I was surprised to find someone accusing me of spreading misinformation, and my comment removed by a moderator. It was clear that my accuser had badly misinterpreted my words. He refused to admit it or accept clarification. (And the mod had already acted, rashly.)
I re-checked what I had written about twenty times over the course of the day. There was nothing there to support the accusation. My best guess is that my phrasing or the subject matter might have touched on rough emotions from a bad experience, leading him to see what he expected to see instead of what I wrote, and triggering attack mode.
Communicating well really is complicated. It takes work on both sides, and can quickly turn into a bad time if it goes off the rails.
Because of this, I’ve been making an effort to read (and re-read) charitably, especially with people I don’t know well.
From the article:
In an EV era, tires are becoming the greatest emitters of particulate matter
The point being that electric drops tailpipe emissions to zero, making tires the next target for reducing emissions.
John Mashey wrote about this nearly 30 years ago. This Usenet thread is worth a read.
Like the Alameda-Weehawken Burrito Tunnel?
For example: Let’s say your email is jane@lemmy.com.
YSK: These domains are reserved for use in examples:
Why YSK: Using these instead of made-up domain names reduces the chance of confusing readers, eliminates the possibility of phishing attacks, and avoids sending unwanted traffic to made-up domains if they happen to belong to someone.
I hate the formatting of most forums. Reddit and Lemmy’s comment nesting is excellent.
The funny thing about this is that it’s just plain old threading, which has been around since the 1980s or earlier, with the slight variation of showing message contents directly in the thread tree instead of beside it (thanks to today’s high-res displays).
Usenet readers did threading. Email apps could do it if the developers wanted to; the required information is there. I’ll bet there’s forum software that can do it if an admin enables it.
For some reason, most corporations seem to have decided that classic message threading has no place in their interfaces. They resort to piling things into stacks or serializing them into seemingly endless scrolls. It fails to represent the structure of group discussions, and sadly, has been going on for so long that many people might not have ever seen the better alternative outside of reddit.
The law is pretty clear on how pending boos is supposed to work,
This is the first I’ve heard of pending boos. Did you mean lending books?
I’m on Debian Stable (with a few backported packages) for both work and gaming. It’s not the most beginner-friendly distro, but I’m no beginner, and I love how low-maintenance it is. It just keeps on working.
I would like to try Qubes OS eventually. I don’t think it will be ready for gaming any time soon, but for privacy and security-minded isolation of components, I expect it’s tough to beat.
Friendly reminder that OpenWrt exists, and is probably safer than the stock firmware in any consumer router.
From a quick look, I see that at least one of the affected models has official OpenWrt support: the RT-AC68U
this time from China (hopefully with the doors closed in the back)
“Fool me once…”
Let’s not forget that copyright enforcement is mostly funded by taxpayers. It’s a collectively massive cost to the rest of us.
It probably made sense for a limited time when we (society) were getting something of comparable value (cultural works) in return. But now that it’s effectively endless, and dominated by corporations, it looks an awful lot like systematic extraction of wealth… from us.