Notices by :mima_rule: Mima-sama (mima@makai.chaotic.ninja), page 14

I think I almost got spirited away to Gensokyo :mima_acchi_kocchi:

@Zerglingman@freespeechextremist.com If a reply works based on the context and your response then yeah :cirno_fumo_yes:

Usually though if you're thinking of quoting the post you're consciously do not want to reply for a reason :sagume_think:

@selzero@syzito.xyz

@MK2boogaloo@lab.nyanide.com That's black-and-red hair girl is Seija wdym :seija_coffee: :yukari_troll:

MUST. PROTECC. KAY

Best Ace Attorney girl :cirno_thumbs_up:

RE: https://lab.nyanide.com/objects/9dc4564d-4d35-4fa4-b20a-c6b18f493694

@roboneko@bae.st Oh yeah I agree. That's a different problem though but it is related to the problem of not backfilling at all :cirno_fumo_yes:

@Zerglingman@freespeechextremist.com @laurel@freespeechextremist.com @untyped@insufferable.tools

@laurel@freespeechextremist.com It's easy to fix but it's not the scope of the fedi software and shouldn't be in the scope of the fedi software ever. If every new instance decides to just backfill every new community it discovers that's gonna result in accidental DDoSes left and right :koishtare:

Separate script in a cron job for backfilling (while adding a reasonable delay between each requests) is the right way to go. :cirno_fumo_yes: Added bonus of being fedi software-agnostic too

@untyped@insufferable.tools @Zerglingman@freespeechextremist.com @roboneko@bae.st

@untyped@insufferable.tools Mastodon and pretty much every other fedi software have this problem too. But there are tools to automatically backfill each profile an instance discovers. I'm not sure if there's one for Lemmy tho :sagume_think:

@laurel@freespeechextremist.com @roboneko@bae.st @Zerglingman@freespeechextremist.com

@Zerglingman@freespeechextremist.com Anyway I don't even oppose that. Just make it clear that it's going to be kept forever within the local instance and don't mislead your users. That's all :alice_wine:

@untyped@insufferable.tools @roboneko@bae.st

@Zerglingman@freespeechextremist.com Well, I hope you never write and publish something you will regret immediately! :koakuma_giggle:

@untyped@insufferable.tools @roboneko@bae.st

@untyped@insufferable.toolsreliably deleting posts isn't really possible in a federated networkI did recognize it's not really possible and I'm not faulting Lemmy for that (that would be unfair!), all I want is for posts to actually be deleted immediately within the local instance than keeping it for an arbitrary duration of 30 days.

Other than that, fair :cirno_fumo_yes:

@roboneko@bae.st @Zerglingman@freespeechextremist.com

@untyped@insufferable.tools I still believe that most of those who moved to Lemmy use the old UI as their primary interface on the desktop web. Not the redesign. Call me copium :mima_copium: but who the fuck unironically not only uses the new UI, but prefers it over the old after having used that for a pretty long while???

Has to be the most Twitter-brained fucking normie if I ever see one :koishtare:

@roboneko@bae.st @Zerglingman@freespeechextremist.com

@roboneko@bae.st Agreed, actually. But it's difficult if not impossible to achieve that without sprinkling in some AJAX or JavaScript.

To be clear I'm not judging anyone for how they interact with their SNS software. If they're fine with the page going white every time they want to check for update, more power to them! If they can't stand that and need scripting, more power to them also.

What I want to say is, I'd rather have the honesty of Misskey devs having to target the lowest common denominator (Twitter web users) to be mainstream than the pretentiousness of Lemmy being a "forum" where a majority of forum users around the internet don't want and don't need constant updates. :seija_coffee:

@Zerglingman@freespeechextremist.com @untyped@insufferable.tools

@Zerglingman@freespeechextremist.com You know what, fair :cirno_fumo_yes:

@Zerglingman@freespeechextremist.com Quote posting is subposting now? Lol :kyou:

You know you won a "debate" you don't even intend to start when your opponent resorts to name-calling instead of actually engaging your argument :ablobcateyeroll: :koakuma_giggle:

RE: https://freespeechextremist.com/objects/9a36a285-f710-4742-9d95-01a70055227f

@Zerglingman@freespeechextremist.com Do you even read what you write? :SanaeConfuzzled:

The average SNS user doesn't want to refresh the page at all. They do not want to wait for every initial paint the browser does. They want the new posts, comments, and notifications to appear in the page "seamlessly" without having paint the whole viewport white for a few milliseconds whatsoever.

Again, they DO NOT WANT to refresh. They don't want your autoreload Firefox extension or something similar to that.

@untyped@insufferable.tools

@untyped@insufferable.tools I did say "Might be fine for SNS" if you have read my earlier reply above that. And unlike Lemmy, Misskey does have a better justification on why they require JS for the frontend to work. SNS users expect real-time updates nowadays for example and there's no way to implement that without refreshing the page. Which the average people find annoying and would rather execute arbitrary code in the browser than deal with that.

Forum culture is different from SNS. We're fine with refreshing. We're fine with static pages. We don't need to constantly check for updates in the threads we participate in; we will check at our own leisure. :seija_coffee:

@Zerglingman@freespeechextremist.com

@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.

@Zerglingman@freespeechextremist.com

@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:

@Zerglingman@freespeechextremist.com First of all it requires JavaScript. Might be fine for SNS but for forums this is just plain bullshit

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