PriorProject @ PriorProject @lemmy.world

Just an explorer in the threadiverse.

---

Read more

Posts

9

Comments

266

Joined

2 yr. ago

In the vast majority of cases, one can support variation in admin preferences by exposing a configuration parameter. Your downvote example is perfect because Beehaw doesn't run a customized lemmy codebase. There is a checkbox exposed to lemmy admins that enables/disabled downvotes.

Running a custom-codebase is generally the highest-hassle method of achieving some custom-config goal. The absence of communities around this approach isn't an accident, the people who develop customizations generally try to work with the upstream unless the devs give them good reason not to.

Are there instances that run modified versions of the base Lemmy software? For example, that use their own sorting algorithms, or provide users ways to block instances or specific users, etc?

If one had developed code to do these things, why would one not upstream it so it's released in core lemmy and all instances can benefit from that capability?

The idiomatic way to query communities in Lemmy is to interrogate your instance, not to interrogate the instance hosting the community. I think there are some sensible reasons for this:

• Large instances hosting lots of communities want to delegate read workload to the many instances out there hosting users. They don't WANT everyone coming to query the communities instance directly. That's rather the whole point of federation. Now, will one app doing direct community-hosting queries bring down the threadiverse? No, it won't. But it's not how community discovery is envisioned to work, and Jerboa being developed by the lemmy devs means that it's unlikely to employ non-federated community discovery hacks.
• If you offer community discovery by directly querying the instance, you create another discovery problem which is equally hard to solve... which is instance discovery. OP may have a particular instance in mind already that they want to query, but as soon as querying communities by instance becomes a commonly used feature... people WILL immediately begin asking how to search instances to put into that list... which again is generally a problem that is supposed to be addressed through federation. Also if you don't build instance discovery, you'll have tons of reports from people who mistype instance names and can't figure out why it's not working.

All of which is to say that while there is an approach that involves directly querying a specific instance... it's a partial solution that doesn't build toward a comprehensive one. I don't expect the devs to move this direction, but rather to focus on fixing the community browser in lemmy and exposing those capabilities through jerboa. This is the larger job I was referring to, and although there is a shorter path to OP's specific request, I don't think it's a likely one to be followed in Jerboa.

It's not guaranteed that every federated app integrates with every other federated app in a particularly useful way. You kind of need to take it on an app by app basis:

• Kbin and lemmy integrate very well. "Magazines" on kbin show up as communities in lemmy. You have almost certainly already read and responded to posts and comments from kbin users, and you may have subscribed to communities on kbin.social, the largest kbin instance. Interacting between the two is pretty much seamless.
• Mastodon and Lemmy integrate, but less completely. If you've seen a post full of #hashtags and with an @thecommunity@instance mention, that's probably from a mastodon user. I'm not sure how a lemmy user can initiate contact with a mastodon user, but a mastodon user can at-mention a lemmy community as if it were a mastodon user and doing that will create a lemmy post. Comments on the lemmy post look like replies to the mastodon toot.

Other fediverse projects will interact in varying specific ways, and you need to figure each pair out individually.

It wasn't a meme yet? So like... 30+ years ago?

1. The phrase hadn't been coined yet in 1993.
2. I said what I said.

ZFS zRAID is pretty good for this I think. You hook up the drives from one "pool" to a new machine, and ZFS can detect them and see that they constitute a pool and import them.

I second this approach, but if one isn't down with ZFS, LVM can bodge a raid onto any filesystem at the block layer. I don't remember when I got over hardware raid envy and decided that I preferred software raid for my home lab, but it was a long while ago and I've never regretted it. Being able to plug some drives into any old USB, sata, or whatever port on any Linux box is super valuable when things start going sideways and you don't have budget for spare hardware or rapid-response support contracts.

It's a frequently requested improvement, you are not alone. But there are no workarounds that I'm aware of either. There's enough apps out there that maybe one of them has better handling of hidden posts... but I follow a lot of lemmy app news and I haven't noticed any reports of it being done well.

... since I moved from OS/2 in I think 1996 or so.

Quitters never win. Warp is the OS of the future, we just haven't gotten there yet.

For anyone wanting more context, OPs article re-reports and links to https://www.wdsu.com/article/louisiana-heart-doctor-says-he-is-leaving-state-due-to-discriminatory-anti-lgbtq-law/44706683# , which has more quotes from the doctor.

I stand by the meme even if I can't stand by the statistics in it.

Fwiw I'm in it too. I'm not going to say what year was the year of Linux on the desktop for me, but it wasn't a meme yet. And I've continuously run an actively used Linux desktop (or mostly laptop) since, often at work but always at home. I unironically prefer it to Windows and Mac, which I also also daily drive and consider to be worse in most ways that matter to me.

I think desktop Linux gamers are right to cheer for the Steamdeck, as its success translates quite directly to an improved gaming experience on desktop Linux. So yeah, the reason this meme is so clear to me is because I see it in the mirror each morning.

This, but desktop linux users are on the step for 193rd place while excitedly screaming and holding a third-place sign. Steamdeck users are on the 3rd-place step while calmly playing their deck.

I enabled it and out of the box none of my containers could resolve DNS, even though aardvark was running.

I experienced this on Ubuntu as well, and addressed it by opening up a firewall rule on the network interface for my podman network allowing the ip-range of the podman network to issue DNS requests to the gateway-ip (which is where aardvark-dns sets up shop).

Also had to add a firewall rule to open whatever ports I exposed from all src-ips to the podman network range before exposing hostPorts would work.

Again, not critiquing the very capable macvlan setup, just sharing tips I've picked up on making netavark work.

This is a pretty awesome how-to. I knew nothing about containerizing GPU workloads before this, and it seems quite a lot less scary/involved than I feared.

FWIW, I think some of your DNS and general networking woes may be due to the macvlan setup rather than using netavark. Netavark seems like the golden path going forward for a batteries-included experience. Not that I have anything against macvlan, in many ways macvlan feels simplest and nicest for homelab setups and I've used it with LXC and other container runtimes in the past. But for the most docker-like "it just works" experience, I feel like netavark is getting the upstream love.

Fwiw, it's straightforward to do this on lemmyverse.net, which works well on mobile. The way federation of new communities works means that it's a relatively big job to create a usable community browser within Lemmy right now. I wouldn't expect rapid progress in this area, and would consider adapting your community browsing habits to rely on lemmyverse rather than in-app browsing.

Is it necessary to add an instance to the allowed list? If federation is enabled, isn’t an instance ’allowed’ by default?

Your understanding is correct, and making your "allowed" list non-empty is a big deal because it implicitly defederates you with every instance that isn't in that list. I rather suspect that OP doesn't understand what the allowed list does and is trying to find ways to promote small Instances while lacking knowledge about how things work.

Defederating from all major instances would almost certainly relegate small instances doing so to irrelevance.

Fwiw, federation is known to be relatively unreliable at the moment. https://github.com/LemmyNet/lemmy/issues/3101 is marked as closed, but it seems pretty clear to me that many of these behaviors persist in 0.18.3. There may well have been improvements, but we haven't yet achieved full resolution of these things.

I wish the feature was better. It both doesn't do a great job of ignoring the publisher, and also you can only ignore publishers that set up an optional publisher page: https://na.alienwarearena.com/ucf/show/1908376/boards/gaming-news/News/now-you-can-ignore-some-publishers-on-steam. This creates a perverse incentive for publishers NOT to create a page, and some big ones choose not to.

I'd like to see:

• Publisher pages be a mandatory step in publishing a game. It should not be possible to sell a game on steam without having a publisher page.
• A flag to control gray vs hide behavior. I don't totally hate the darkening, as sometimes I want to be aware of what a publisher is doing even if I don't intend to buy. But people who want full hide should be able to get it, and that's possible for the steam client to do client-side... It's not incompatible with steam serving a non-personalized storefront.

There are some known bugs around comment counts handling deleted and edited comments. The counts aren't exact right now, nothing you can do though.

1. Kbin doesn't federate downvotes from Lemmy, and I believe it has a smaller user population than Lemmy (or at least one that generates fewer total downvotes). So you'd expect downvote counts to be wildly different.
2. On upvote counts, federation is just real flaky right now. I don't have GitHub issue links handy, but there are several major issues detailing posts, comments, and votes Federating unreliably. You can pretty easily extrapolate that to expect vote counts to vary by 20%-60% from server to server depending on how many federation messages a particular server decided to drop on the floor on any given day.

Lemmy is pretty cool, but it's a lot rough around the edges right now. It's improving fast, but if you break out the magnifying glass, you're gonna find problems.