Lvxferre

The site feels faster, the notifications are more reactive, and moderator view is a godsend.

As for now, the only new bug is fairly minor, markup-related. Examples here and here, screenshot:

Before the update, “há” “a” and “haver” would use a plain highlight colour (they were using the `code` markup); “dog**'s**” and “cat**'s**” had bold face.

Thank you, and sorry - I made sure to read the FAQ, but I couldn’t find the answer for this specific question.

Why do jc141 releases use DwarFS, instead of more typical compression formats like tarballs?

Seriously… it takes a big amount of stupidity, or a similar character flaw, to spam Microsoft products through a Reddit link in a federation where most people don’t want to touch either Reddit or Microsoft with a 3m pole.

So, whoever is behind this spam account: stop chewing on spoiled hay, you freaking barn animal.

I’m not asking anything because I’m a potato when it comes to software. I just wanted to drop by and say: thank you both for Lemmy. The platform is amazing, and it’s clear that you guys are pouring some heavy love (and labour hours) in it, as it’s improving at an amazing pace.

It’s a way to share files across seeders/peers of different torrents, as long as the torrents contain at least one identical file. For example, let’s say that:

• you’re downloading torrent1. It shares the files A and B. You got A already, but since the number of seeders dropped considerably, you’re having a really hard time downloading B.
• there’s also torrent2, sharing files B and C. Fairly active, with lots of seeders.

Without swarm merging, you’re stuck waiting for new seeders or peers from torrent1 that have the file B. With swarm merging, your torrent program will get the file B from people sharing torrent2 too.

I recall this feature from Vuze; but apparently BiglyBT also uses it.