git commit -m $(date)

well I just checked and while “sync contacts” did not turn itself on, “allow contacts to add me” did. there’s definitely something going on

the rule of thumb here is that you should really just use one browser ad blocker. having multiple will conflict especially regarding anti-adblocker prevention (as uBO will try to hide itself and redirect to a “defused” version of an ad script and whatever other ad blocker you have will think that’s an ad and block it)

not entirely sure how well DNS ad blockers fit into this. there is a chance they could make your ad blocking detectable by blocking a request uBO intentionally lets through (possibly in a modified state), but as far as i’m aware there haven’t been too many issues stemming from combining DNS blockers with uBO and the likes.

if this were to happen trust me when i say pluton’s role in enforcing it will be little to none.

as far as i can tell this particular image is fake. and as far as i know pluton does not work like that.

https://www.reveddit.com/v/Piracy/comments/wojic3/does_the_idea_of_this_concern_anyone_else_why_is/ikclsct/#faithfully_engaged

DNS blocking is the most unreliable way of blocking youtube ads you can imagine.
you could write a script to OCR your entire screen and click skip ad and it’d be more reliable than DNS blocking

One of the reasons I use containers instead of installing things directly is that i can completely uninstall a service by deleting a single directory (that contains a compose.yml and any necessary volumes) and running a docker/podman system prune -a

or that i can back up everything by backing up a single “containers” dir, which i could have on a subvolume and snapshot if i wanted to

systemd/quadlet on the other hand makes me throw files in /etc (which is where you’re supposed to put them, but ends up resulting in them being tangled together with base system configuration often partially managed by the package manager)

The Solution™ to this is configuration management like ansible or whatnot, which needlessly overcomplicates things for the use cases i need (though they’re still useful for getting a base system “container ready” wrt ssh hardening and such)

tldr: i want my base system to be separated from my services, and systemd integration is the exact wrong tool for this job

catbox and co are mainly useful for videos, as some instances (not sure about this one) have video uploading disabled (as that’s usually a lot more costly than image uploads)

In Logseq, everything is a nested list. This feels like a limitation, but I’ve been preferring it. The decision is made for you: you’re going to jot this information down as a list. So then you just start writing it.

Oh - this sounds interesting.

Whenever I needed to jot down any notes I’ve been finding myself just writing plain .txt files with bullet points, and trying tools like Obsidian or TiddlyWiki I always ended up being overwhelmed with the amount of stuff I could do (and with all the customization options) that I never got around to actually writing things down. I’m definitely gonna look into how Logseq works.

(Although I have to say, their website does look a bit “too hype-y” for my liking. IDK how to explain it, just a gut feeling. Still, at least it’s FOSS so it can’t be too bad)

Oh no it’ll federate alright.

The thing about ATProto is that unlike AP they don’t seem to expect each instance to have it’s own community with it’s own rules and vibes. They seem to be using federation just as a way to “scale up”.

If they can get any non-bluesky-the-company folk to create instances then that’s just scaling they don’t have to pay for and a convenient legal scapegoat for the inevitable consequences of their lax moderation. Why wouldn’t they federate?

remember back when 2g was the shit and speakers would start buzzing right before your phone started ringing?

fixed that part, words are hard

The thing I’m trying to say is that “having an API” does not matter in the long term if the API does not expose the functionality needed to use it properly.

And TBF if someone joined Lemmy only because it had an API and nothing else then they’re gonna be in for a very rude awakening sooner or later as the troubles of federation that previous (mostly microblogging) platforms have encountered and attempted to solve (not to mention novel problems due to the community oriented nature of Lemmy) start to show up.

This is only going to get worse, and throwing “more API” into the fire won’t fix any of the important problems at hand.

Picking a fedi server software is just picking how much (and what kind of) jank you’re willing to tolerate. The features are always secondary.

I don’t think an API is the thing that matters here. There are quite a lot of things you can’t hack on with a client alone and actually needs server side support to function (actual moderation tooling is a prime example)

Also most APIs aren’t “designed” per se and just expose the internal representations of the projects they’re of. A “common” API would either be too “wide” enough to be unusable (hello, ActivityPub C2S) or would severely limit experimentation and innovation (good luck on building microblogs in the Lemmy API) without having so many extensions that essentially end up being a third, completely different API.

Everyone wants a fork. Nobody wants to be the fork.

We need a small group of motivated and skilled developers to get together and decide “we’re doing this”, and actually go beyond announcing an empty Git repo. (i.e. actually have some usable code to show for)

Dealing with a codebase as janky and large as Lemmy is unfortunately beyond my skillset, otherwise I’d love to get involved myself.

The wording in the parent comment also seems to imply the Fediverse is just Lemmy/kbin, which is a weird self-centric take I see here (i.e. on Lemmy) a lot.

A lot of the broader fedi that has access to adequate moderation tooling are doing just fine and don’t seem too “ill-suited”. It’s really just Lemmy that’s like this.

I’m not entirely sure I’ll attempt joining “the new Beehaw” wherever it may set up shop (y’all are a bit too serious news-y for my liking, personally), but all the federated interactions I had with the folk from Beehaw had been quite positive, and it’s kinda sad to see y’all go. But I can definitely understand the reasons why, and I do have my own gripes with Lemmy (both the software and the unfortunate community it has picked up) as well.

And here are uBlockOrigin’s filterlist issue tracker: https://github.com/ublockorigin/uassets/issues

On the issue comment you can see maintainers @-ing each other to add things to upstream lists, so it’s all one big community rather than being extension specific.

One of the biggest performance issues is the blur effect in the UI. Disable that from the settings and on my current laptop it goes from “visibly laggy” to “fairly usable, even if not as performant”.

But I do miss having the “fucking [insert slur here]” “kill yourself” “only a basement-dwelling loser would have this opinion” comments auto-hid because the average passing user disapproved of it and decided to express their disapproval via downvote, instead of coming across it myself semi-frequently and reporting it.

If Lemmy does introduce a sort of “instance-level global moderator” role separate from admin role, I can definitely imagine smaller, tighter knit instances (think your average gay catgirl Masto/Akkoma instance, not Beehaw or the instance I’m on for that matter) giving mod rights to a significant chunk of their members just so these kinds of situations happen less. Anyone who sees anything of that sort and has the mental energy could just remove it for the rest of their community.

Of course there is a potential for abuse in this style of moderation especially as an instance gets larger, but then one of the good parts about federation is that you don’t need a large instance to have access to the content. And unlike Mastodon you actually get access to the entire conversation including all the replies here even with a single user instance due to how communities are implemented.

(just in case this comment starts getting strange interactions it’s apparently broken the lemmy containment barrier and has reached the microblogging fedi 😰)