For serious comments, my true audience is the unknown reader. For jokes, my audience is myself alone.

Lemmy dev suggestions: Remove all downvotes. User blocks should keep the blockee from seeing the blocker.

  • 0 Posts
  • 11 Comments
Joined 2 years ago
cake
Cake day: September 27th, 2023

help-circle

  • For me, the important thing is that this is a vibrant community.

    That means that from the mods’ perspectives, they don’t get too loaded down with moderation work, or need to defend themselves and create friction with the community.

    It also means that when people want to contribute to the community, they’re not afraid of what the mods will say. If they post without reading the rules, like probably most people do, it’s really the poster’s fault. But if they are afraid to post even after reading the rules, then I think that has a freezing effect on the community.

    As for people who are looking for loopholes, I think they’re trying to make the mods’ lives harder, and so I don’t really think they’re worth worrying too much about. They’ll probably get banned sooner or later because that is the attitude of a troll.

    Just my opinion. I’ve never been a mod, and I don’t think I could handle that responsibility. I just try to be empathetic with everybody involved.


  • You’re right. One problem is, even though mods already have the power, specifically saying in the rules that the criteria is subjective sounds like something that a mod would make when they are tired of having to explain their moderation choices.

    They can just say that it was low-effort, and problem solved. They don’t need to explain themselves, right?

    But when the rules are vague, I think they’ll end up with more complaints from people who have different criteria of low-effort from the mods. This sort of interaction leads to accusations of mods power-tripping.

    If the mods can nail down exactly what is low-effort, like, “X will always get removed. Z will never get removed unless it violates other rules. Y may be at risk of the moderator’s mood. You have been warned.” If they nail things down a bit more, then they will probably make things easier for themselves in the long-run than just keeping things vague.

    Plus, if the rules are not vague, then people can discuss them safely when the rules are changed. When rules are vague, people will simply be upset that moderation was sprung on them, and everything will be discussed while people are upset. My belief is that people best discuss things while calm, and not while experiencing one person having power over another.





  • Skandalakis (I can’t believe that’s actually his name) said he appointed himself to the case because every other prosecutor refused the case.

    Skandalakis was forced to either appoint himself or let the case be dismissed because there are no prosecutors.

    I’m not sure why he asked the judge to dismiss the case. Considering it already got several convictions, it seems ridiculous. Maybe Skandalakis is also corrupt. Maybe he’s scared. Maybe it’s because it’s too hard to prosecute while Trump is president.

    Regardless, I’m tired of seeing all of these criminals go unpunished. Everybody who is letting them off is a collaborator.




  • It’s true that the actual “story” is very short. 1 kB is 1000 bytes and 1 KiB is 1024 bytes. But the post is not about this, but about why calling 1024 a kilobyte always was wrong even in a historical context and even though almost everybody did that.

    Yes. But it does raise the question of why you didn’t say that in either your title:

    Why a kilobyte is 1000 and not 1024 bytes

    or your description:

    I often find myself explaining the same things in real life and online, so I recently started writing technical blog posts.

    This one is about why it was a mistake to call 1024 bytes a kilobyte. It’s about a 20min read so thank you very much in advance if you find the time to read it.

    Feedback is very much welcome. Thank you.

    The title and description were your two chances to convince people to read your article. But what they say is that it’s a 20 minute read for 10 seconds of information. There is nothing that says there will be historical context.

    I get that you might want to make the title more clickbaitey, but why write a description out if you’re not going to tell what’s actually in the article?

    So, that’s my feedback. I hope this helps.

    One other bit of closely-related feedback, for your writing, in general. Always start with the most important part. Assume that people will stop reading unless you convince them otherwise. Your title should convince people to read the article, or at least to read the description. The very first part of your description is your chance to convince people to click through to the article, but you used it to tell an anecdote about why you wrote the article.

    I’m the kind of person who often reads articles all the way through, but I have discovered that most people lose interest quickly and will stop reading.