while i don’t have any specific opinions about this that other people haven’t addressed, i just want to flag up something;

How this could be enforced? No voting from the All and/or Local feed. Seems easy and straight forward.

this seems unenforcable. as in, you can’t really tell where someone discovered a post from. yeah you can just remove the buttons from those views clientside and it’ll probably work for the majority of cases, but alternate clients or modifications to lemmy-ui can simply put the buttons back in (or in cases of unmaintained or differently opinionated clients, just not remove the buttons at all). the backend can’t really differentiate which view a vote comes from. federation especially can’t differentiate which view a vote comes from.

epic megapost

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

What I’m more worried about are posts relating to news mainly. Where even if the immediate first level comments are fine, there are threads that get out of hand really quickly.

I agree that while posts inherently designed to be controversial may not benefit from Active considering the influences voting has (though me being on an instance that has downvotes disabled may be influencing my view here!), Active may make it significantly easier for an otherwise innocent post to devolve into a flame war.

The main excuse for this kind of algorithm seems to be around “promoting discussion”, but in my experience tech that’s intended to promote discussion does inherently promote flame wars too, as they’re extremely difficult if not impossible to distinguish without a human in the loop. I’ve attempted to write something about this on the microblogging side of the fedi, directly influenced by this post

I’m just throwing this out there but having the default sort incentivize comments seems like it’d highlight posts meant to cause flame wars… Is that what we want out of this platform?

(talking about microblog fedi here, Lemmy/threadiverse is it’s own thing)

don’t do hashtags. hashtags (especially common ones like #memes) are overrun by repost bots and low quality garbage.

the trick is to be on a small-to-medium instance you vibe with (1k active users seems to be the sweet spot. anything larger than 2k I’d avoid. do NOT join any flagship instances like mastodon.social), follow fun people from your local timeline, and see who they boost. and follow up the boost chain until your timeline is sufficiently fun.

I’m mildly worried I know (as in, am aware of their existence, thankfully not having interacted with them) who you’re talking about

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

AFAIK no open source library exists. Open implementations of gesture typing do exist (FlorisBoard had it some time ago, though it’s going through a significant rewrite still) but the lib loading on OpenBoard is specially intended to use Google’s proprietary libraries. (Which is why it’s an external download and not built-in)

Or that’s what the state of things were the last time I checked.

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

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)

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)

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.

It should. However moving things around is difficult and will cause synchronization issues.

In most cases starting from scratch on a fresh subdomain is the best solution. ActivityPub is really finicky unfortunately.