The developers are relative beginners pretending to be experienced and it shows in the recent XSS exploit in their Markdown parser
The developers are also full-on tankies, the literal reason they created Lemmy is because of a grudge they have against anarchist Raddle, not out of benevolence
The whole project is a psyop, an entryist attempt by tankies to spread tankie, insecure, and privacy-breaking bullshit to the fediverse
@mima >First of all it requires JavaScript. Skill issue. http://precious.harpy.faith/Zergling_man/clemmy/ (Also lemmyBB if you care to patch it up, which shouldn't be too hard; I ought to do it at some point soon.)
>Might be fine for SNS Skill issue. I haven't written a client for pleroma yet though.
>The developers are relative beginners pretending to be experienced Many such cases. They didn't believe me when I told them that they were setting the tooltip on fedilink icons incorrectly (using <title> tag) which was breaking the page title, visible on lynx. So I proved it with curl and then they believed me.
>recent XSS exploit in their Markdown parser See above
>The developers are also full-on tankies, the literal reason they created Lemmy is because of a grudge they have against anarchist Raddle, not out of benevolence Irrelevant. The thing works.
>The whole project is a psyop [citation needed]
>an entryist attempt by tankies to spread tankie [citation needed]
>insecure [citation needed]
>and privacy-breaking bullshit to the fediverse [citation needed]
@anonymous@mima@laurel The easiest reason to despise rust is its godawful syntax. I refuse to touch any rust project for this reason (I think lemmyBB is in rust, so, great). But there aren't really any reasons to care about things other people write in rust.
@Zerglingman@freespeechextremist.comclemmyI don't care about third-party clients in this case. The fact that you need a third-party client to get away from the JS bullshit of the canonical frontend is proof enough that your software is bullshitMany such cases. [...]I can understand because HTML is bullshit anyway. I don't understand how they could've allowed that XSS to happen because if you're dealing with Markdown the first thing you must keep in mind always is the user can be hostile and put malicious code in their inputs. This is worsened by the fact that not only to you have to deal with that scenario locally but from the rest of the fediverse as well. That means taking as much precautions as possible like strict sanitation of HTML output (don't ever fucking allow to get outputted) and a strict Content Security Policy (don't ever allow scripts that are not self!).
Have you tried comparing a typical Lemmy instance's CSP and Raddle's CSP? You should if you haven't yet and you will see what I mean. (Oh and to add to the irony Raddle's software backend is written in PHP)Irrelevant. The thing works.So theoretically you're perfectly fine to use some pedo's Akkoma fork literally named after incest as is because it "just works". Sure it's an extreme example, but you did say "the thing works" so I want to test how far you'd go with that. :koakuma_giggle:privacy-unfriendly[citation needed]I forgot the issue number where this is discussed but Lemmy IIRC doesn't delete your posts and comments immediately and instead just keeps them hidden (but still visible to the admin) for 30 days. And it's intended behavior according to the devs.
Now you can argue that you shouldn't expect any privacy in the fediverse due to its open/public nature (I agree but I think we can do better), but you can't just not honor the user's request to at least remove their content from your server as soon as possible. It's their data; respect that. Again I do not expect all instances to honor their delete request (it has been a problem since Usenet and I'm not expecting this to be resolved in the near future) but two wrongs don't make a right.
Also last I checked Lemmy still doesn't support proxying media, and because you can embed images in your Markdown post and comment, it means you can find out if someone read your post or not because the recipient's browser will automatically load your remote image. I thought we left webbugs / beacons from email behind. :sagume_think:
@laurel@freespeechextremist.com I'm not a fan of Rust (compile times can be a nightmare and dependencies are as ridiculous if not worse than Node), but I don't care enough to call for its head.
The evangelists are annoying though, I can wholeheartedly agree on that. But that doesn't make the language look bad. It makes its supporters look bad. Pretty big difference IMO.
If you don't plan to look a its internals and/or hack on it, I agree. But I plan to do so and rust being so difficult to read is a problem for everyone. For maintainers, system admins and those looking to modify it.
@laurel@mima I don't really consider it a choice. Some stuff I work with is written in rust, so I sometimes read rust. I'd rather python but most people never got the memo that python is actually good if you don't run the default interpreter. (Which I do anyway :^) ) I'd agree that PHP is easier to read than rust. Not assembly though; since I think rust's syntax was basically "hey I really like assembly but I also really like java let's make our syntax like both of those".
It might be PTSD after I had to read a convoluted cli frontend written in rust. The backend code was readable but the front was something else. Could be done with one twentieth the complexity with bash or python.
@laurel@mima You can *usually* get them to admit that python is nice to write, but they'll dismiss it with complaints about pip (lol) or "hurr it's slow".