Broken input sanitization probably.
Issue will thankfully no longer exist in the next lemmy release.
Broken input sanitization probably.
Issue will thankfully no longer exist in the next lemmy release.
Great original retort there. Not part of “the lot” I had in mind in my previous comment at all.
if 9 people are fine sitting at a table with a Nazi, you have 10 nazis
Good thing there is no table involved.
both sides
Actually, if you read carefully, you will find that my arguments are against both sides, where the sides are the Stasi and McCarthyists.
That is if my argument was ideological. But it wasn’t. It was a technical and practical answer where I consider(ed) whatever ideologies supposedly involved irrelevant.
Monitoring instances and gouging their supposed collective thought, and making decisions based on that in an attempt to appease the masses, will make the job of general purpose instance admins unattainable.
It would be a very effective way for the likes of Reddit to fuck with the Fediverse, actually.
Weekly instance defederation talk loaded with emotional/psychological manipulation, moral grandstanding, and why not, some bullying.
“table with a Nazi” analogies. Linking the Paradox of tolerance wikipedia page for the 345636556th time. The lot.
This may work with instances that like their Stasi or McCarthyist wanna be agents (a.k.a. users) keeping their eyes out for baddies.
For general purpose instances, this will be a great way to make them quit. A desirable outcome for some. I’m not one of them. So, I, and hopefully others, am willing to take the hit and speak out, and state things that some admins may want to state, but don’t feel comfortable doing so publicly.
A general purpose instance with no claimed “safe space” offering should only be burdened with instance-level defederation talk when another instance is behaving badly at a technical level, or when its admins are actively involved in, or not actively trying to prevent, spam, brigading, repeat copyright infringement, and stuff like that.
Bad thoughts expressed in text form by individual users shouldn’t be ground for such talk, and to create a foray over such an inactive instance is quite self-indulging.
If anything, maybe a couple of previous defederation decisions were taken in haste, and should be reconsidered!
If you’re looking for a “safe” instance, there are a couple that should suit you. One of them was already recommended to you.
There is the option to upgrade with the sanitization commit reverted of course.
From a technical point of view, I’d rather Lemmy didn’t federate except with itself, and maybe possibly also with similar networks, but only as long as that doesn’t hold Lemmy back from doing its own thing.
Getting ActivityPub federation to work reliably between Lemmy instances alone is already proving challenging for developers.
From a personal point of view, I have zero interest in what I consider a shit paradigm of social communication. The “micro” lie in micro-blogging, as you quickly conceded, is long gone. The interface is horrible for effective exchange of well-thought ideas. The social networks formed are hypernormalized echo chambers of unhinged ranting faux intellectuals and champagne activists, usually led by a cult of personality or two who are tasked with making sure the one-upping posturing game continues forever.
When you are about to "micro"blog, presumably you will be writing something coherent enough that it relates to a certain subject of interest to a section of the public. It is also presumably meant to be viewable by the public since you’re not sharing it in a private group chat.
If that’s the case, there should be a community in Lemmy where those interested in that subject congregate. That community would either be low-traffic, then you can make your "micro"blog a post there breathing more live into it. Or it would be a high-traffic one, in that case a lounge/chat/MegaThread post should exist where you can chat with people interested in that subject, in an interface that actually facilitates good discussion.
Imagine if media in Lemmy was all hosted in a distributed network filesystem like Iroh, where instances only function as inserters and exit nodes for that media.
This way, smaller instances can have a smaller cache corresponding to the media that was actually needed by it (recently). And independent peers can help by participating in the distributed file-system network without running instances themselves.
Would you have escaped them a priori?
Do you consider markdown-it
’s typographic replacements common knowledge, and thus intuitively escapable?
Should lemmy apps be pushed to use markdown-it, in your opinion?
While it may seem nice
No, it really doesn’t, its a horribly bad design choice.
I wanted to give some balance to my argument. I guess I was over-cautious with that one.
@dessalines@lemmy.ml
And btw, that’s '../lemmy'
in the comment above with two dots. I didn’t write it wrong. The third dot comes from markdown-it
(confirmed using their live demo)!!
Good, because I speak Rust, so, if there is an itch to scratch, I will scratch it, even though I’m not a UI guy.
I tried running the UI yesterday standalone and had ‘error loading’ message or something like that.
btw, mentioning needing ‘…/lemmy’ available in path, and needing the wasm target installed (via rustup target install wasm32-unknown-unknown
) may help non-rustaceans in particular, if added to the contributing instructions.
Also, the UI was listening on *:1237
, not just localhost, so maybe a WARNING regarding that is advisable, together with explaining the purpose behind leptos also listening to port 3001.
All trending communities’ icons are shown. So the fix appears to be working.
Thank you.
Will there be a way to run the UI in client mode only, without being attached to a running instance?
The codec is basic, uses decades-old tech, and was trivially REed.
Lemmy instance choice does not check out ;)
https://github.com/LemmyNet/lemmy/pull/4024