nah, there are plenty of truth wannabes (freeze peach bigotry safe havens) that actively federate. just look at literally any competent server’s blocked instances list and you’ll see a few examples. there’s a reason why nobody* runs completely open federation

*: aside from people who’re friendly with that crowd ofc

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

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

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?

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.

Logic errors will be a more relevant issue with a web app (things like not setting your JSON Web Tokens to expire) and Rust won’t save you from that.

I’m sure there is some arcane feature of Rust that’d let you encode that in the type checker somehow. Yeah it’d be completely unreadable and unmaintainable but knowing the Rust community there’s probably someone mad enough to take a crack at it.

AFAIK the issues l.w et al are struggling with are to do with the database. The language you’re calling out to Postgres doesn’t really matter when it’s Postgres that’s taking a lifetime computing through your hell-query.

I don’t know much about Go (I should really take a closer look at it) but it’s definitely also a valid candidate. (Perhaps a bit too bare bones for my personal liking, but hey you can’t win em all)

A long-running web thing like Lemmy doesn’t need the processing benefits of native compilation, and can avoid memory vulnerabilities with a garbage collector. Most things it does are IO bound (receive data from other servers, send data to other servers, occasionally render some HTML, interact with a database…) so you’re really not benefiting from anything specific to Rust, but you are losing a significant amount of developer effort into things like working with the borrow checker or the infamously long compilation times that could instead go into implementing functionality.

You could make something just as performant as Lemmy is today with Python or JS (JS would particularly work well given the prevalance of JITs).

I’d been eyeing azorius.net lately considering it’s much smaller/younger than Lemmy and already federates (and might make an interesting foundation to build something out of before it grows too large, hint hint to anyone who actually knows Go) but I don’t have the Go experience to actually go through its code.

I’ve been experimenting with ActivityPub on my own time and I am kinda starting to understand why all AP projects end up being large messes. It’s spaghetti code all the way across the fedi.

Because now you have to maintain that fork. If it was as simple as pressing the little fork button on GitHub and importing a few PRs in than there’d already be several forks right now.

The Lemmy codebase is a beast that’s evolved over several years. Not everybody can just jump in and throw anything they want just because of how complex a system it is internally. (I learned that the hard way.)

Across the fediverse all the major successful forks have a motivating factor. Glitch social is maintained by the only other paid developer hired to work on Mastodon and acts as an unstable branch / “feature fast track” of sorts, Akkoma exists because upstream Pleroma has sided with the freeze-peach crowd too many times to count. Firefish and Iceshrimp had a whole… thing… (too much drama to explain) (oh and upstream Misskey is way too Japanese for western developers to contribute, including commit messages and code comments) What’s the motivation to start a Lemmy fork? And what’s the motivation to keep maintaining it?

I really want to see a Lemmy fork. Particularly one that attempts to prioritize instances as their own individual communities (rather than the Redditesque “instances as free horizontal scaling” view of the fedi a lot of people seem to have). Hell I might end up attempting to contribute a quality of life feature or two of my own if a viable fork were to exist. Yet there isn’t any.

So, I guess what I’m trying to say is, the only reason no fork exists is because nobody has stepped up to the challenge.

EDIT: And of course with ActivityPub in the mix you also have to consider how it will affect federation with other instances, and building consensus among other projects (not necessarily just Lemmy) regarding any extensions you might decide to add to the protocol (though you’d have much easier time implementing extensions from other projects if they solve your issue)

> Aug 11 17:25:23 adam kwin_wayland_wrapper[2483]: error in client communication (pid 12396)
> Aug 11 17:25:23 adam plasmashell[12396]: wl_display@1: error 0: invalid object 213
> Aug 11 17:25:23 adam plasmashell[12396]: The Wayland connection experienced a fatal error: Invalid argum>
> Aug 11 17:25:23 adam plasmashell[12396]: The Wayland connection experienced a fatal error: Invalid argum>
> Aug 11 17:25:23 adam systemd[2384]: plasma-plasmashell.service: Main process exited, code=exited, status>
> Aug 11 17:25:23 adam systemd[2384]: plasma-plasmashell.service: Failed with result 'exit-code'.

KDE’s crashing and getting started back up. Due to how Wayland works this will also take down most programs you were running.

Why is KDE crashing? No idea. You may have better luck with Xorg if you aren’t reliant on any Wayland niceties (proper multiple monitor support, for example)

edit: https://bugs.kde.org/show_bug.cgi?id=447717 looks like a candidate, but there isn’t enough detail to make sure

it can be pretty useful for really specific cases, but i’m not exactly sure if this is one of them

the allowed instances list acts as an allowlist, meaning you’d be defederating yourself from the rest of the fediverse (and only federating with the instances you allow).

if that’s what you were going for ofc it’s your right and i sure won’t stop you from doing that, but i feel like you’ve misunderstood what it is.

fair enough. the files i upload tend to be pretty small (<25-30 MBs) so i haven’t needed to think about details like dash. there are a few projects like https://github.com/ShaneIsrael/fireshare and https://github.com/Hubro/clipface i could find with a quick search but none of them try to do anything adaptive (unless you go for a full blown solution such as peertube which doesn’t seem to be what you’re looking for)

whenever i needed to do that i just rsync’d mp4 files to a static server and posted a link. not entirely sure what extras you’d need.

The Synapse and Postgres containers are using about 2% CPU and 1.2Gb of RAM combined. If your strapped for resources, check them out.

with 1.16G i can run dendrite and iceshrimp (+redis and +sonic, shared caddy and postgres between both). i wouldn’t call synapse the “strapped for resources” server.

*as long as you have a good CPU, a minimum of 32GBs of RAM, about 200GB disk space, fast internet access, and 12 hours of time per clean build (or try incremental builds that will constantly break).

Having maintained my own branch of LineageOS for a while, I would not take compiling Android as lightly.