![](https://lemmy.blahaj.zone/pictrs/image/PG5vaKqMsg.webp)
![](https://lemmy.dbzer0.com/pictrs/image/a18b0c69-23c9-4b2a-b8e0-3aca0172390d.png)
if this were to happen trust me when i say pluton’s role in enforcing it will be little to none.
People Outside the Threadiverse: Please tag @ShittyKopper@blahaj.zone on your replies as Lemmy federation can be iffy. Particularly if your instance has Authorized Fetch enabled!
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.
I imagine infinite scrolling would be much easier on the server (and overall less janky with less repeated posts) and therefore more likely to be added after 0.19.x due to the switch to cursor-based pagination. That said Lemmy devs may or may not be against something like that on the default frontend due to well being reasons (unsure on where they stand on this tbf)
That said, custom frontends do exist and I assume there has to be at least one out there that already supports it (and isn’t mobile only)
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
I swear fossbros lose reading comprehension skills faster than Tumblr once you ask for any kind of software recommendations
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?
i was thinking of attempting something of that sort but i quickly realized that it’d be even more useful as a generic “list of communities for/about [thing]”, and people could then use that generic list both as a subscription list AND as a block list, depending on their interests
and then i swiftly gave up realizing the scale of it all so if anyone wants to run with this idea feel free to do so
I imagine the most “ideal” outcome would be “whatever link the default webui shows as the fediverse link (the colorful icon on all posts / comments)”, as that’s the “canonical” link (technically, the ActivityPub ID, which is I think required to be a link as per the spec) of that specific post or comment.
It’d be the most accurate in terms of visibility (could be deleted by OP and the delete might not reach your instance), latest edits, vote counts, and replies for that specific thing, that said it’s definitely not as convenient as just copying the link in your URL bar and pasting it to wherever.
Also depending on the exact software running on an instance, that link may not point to a human readable page, but that’s a pretty rare edge case that even the most incomplete real life implementations I’m aware of handle reasonably well (even if it ends up doing a redirect)
i’m using tilt controls!
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)
i belieive lemmy groups will boost the like activities they receive to all instances, whereas mastodon doesn’t try that sort of thing (likely due to privacy reasons, as this means all instances know who liked what)
I remember looking into it back when lemmynsfw was brand new and flooding all with un-nsfw’d porn and the devs seemed to be explicitly against giving mods the ability to edit posts, which NSFW tagging kinda falls under.
That’s why gated communities like Tildes and all these curated instances will never reach Reddit levels: they are starving the engine.
The phrasing here kinda implies this is a bad thing and everyone should be focused on 🚀 constant growth 🚀.
Tildes in particular has an extreme focus on quality over quantity and has some really interesting ideas on moderation (that haven’t been implemented due to lack of time on Deimos’ part). The site is still considered an alpha after all this time.
Every time a site update/announcement/whatever happens everyone with an account older than like a week (iirc?) gets topped up to 5-10 invites. You can (could?) also just go to r/tildes or email and ask. They use invites more as a way to slow registrations down than to be an exclusive club so it’s really not that hard to get your hands on one.