• 2 Posts
  • 40 Comments
Joined 10 months ago
cake
Cake day: July 3rd, 2025

help-circle


  • I understand. But with how downvotes are sometimes, but often IMO, used - a vote on agree/disagree, in a way that feature becomes “I don’t want to see opinions of people that disagree with me”. It does make it exotic
    So the chances that it will be developed and tested is rather low, chances that there will be enough social support for having it is rather low


  • The problem with that is then instead of having 15 downvotes and two comments with a bunch of upvotes you will end up with 15 (probably less but just to portray my point) comments all saying more or less the same. And since (IIRC) Lemmy does not have notifications one could enable on other comments, you would be discussing the same thing in 15 separate threads because your interlocutors won’t see your responses in the other threads




  • people downvote instead of shouting back. OK fine. Except, for whatever reason, I personally don’t feel this overwhelming need to stamp aggressively on other people’s “wrong” opinions

    So for you downvoting is aggressive but shouting back is not?

    IMO the truth is mostly pretty simple: it means “Muh! Me no like!”. Which is completely uninteresting as well as (I argue) toxic

    Apart from votes meaning not being set in stone, I think they do serve a very important role. You can’t realistically be having 5/10/50 simultaneous threads, especially if the points are the same. Someone upvoting can be a signal “I agree with that take”, without essentially spamming the discussion with such comments. Someone downvoting can mean “I don’t agree”. Someone downvoting one comment and upvoting a response is essentialy taking part in discussion - “I don’t agree with you, that other person is right”. Without muddying the exchange. It’s a mechanic to have a social discussion without it looking like a chat during hype-train.
    When we gather IRL and there is, let’s say, 50 of us, we will be using claps, murmurs, whistling, maybe short shouts. But for sure it would be impossible to discuss a thing if everyone in the room would form as little as one sentence. That’s what votes sometimes are - room temperature of the audience


  • having the visibility of my content pushed down

    I might be wrong, but I think most use “New” sort, and I just checked, the default algo on .world is “Active”. So downvotes won’t push posts down

    telling me with the downvote button that my contribution is worthless

    The definition of downvote is not set in stone, a lot of people define and use it differently. For some it’s “I don’t agree”, for some “it’s wrong but I’m not going to report” and for some… I have suspicion that for some it’s “I’ve seen the title, I’m not interested”. The fact that people don’t agree with you does not mean they see your point as worthless. They just don’t agree. And I suspect, most often people would just downvote and move on, the cross between those who downvote and comment will be much smaller. And actually the fact that they commented means that they decided it’s worthwhile to spend time on disagreeing with you



  • Going to Beehiv or Blahaj-whatsit is not a solution, because the communities I’m interested in are not there

    As long as the instances are not defederated, you can interact with the communities from other instances. And AFAIK on instances that have downvotes disabled, the vote numbers will also be only from upvotes - I mean, those not only hide the downvote button, but also don’t federate in the downvote actions


  • I’m too noob to understand it all but the way I see it, the core is not about using Some instead of iter::slice but what is inside.

    I understand this all is in context of Intel Software Guard Extensions about which I know nothing at all, and “UserRef states that userspace may always write to backing memory at any time, and that even &mut UserRef<T> is not exclusive”. So it seems that the design of UserRef is basically against Rust principles (“userspace may always write to backing memory”). So when the iterator is just a wrapper over slice::Iter, the code in next() relies on Rust’s principles which don’t align with how UserRef is supposed to behave. The proposal is to walk over ptr “manually” and return it (cast to UserRef) instead of constructing new UserRef from what slice::Iter would return in that next().map(|e| UserRef::from_ptr(e)).

    But does

    +pub struct Iter<'a, T: 'a + UserSafe> {
    +    ptr: *const T,
    

    really mean that one can happily cast that ptr to UserRef?
    What is PhantomData and how/why using it makes any difference, when it’s not being changed during iteration?
    Is the UserRefdesign sound or was only a workaround some problem?








  • There’s a lot more to what destroyed hanging out in the pub than scheduling

    For sure but even if you switch out computer games to board games, that is still not the same. People moved, a lot of games need space and hauling the box, etc

    In school we used to have breaks, we were hanging out just because of that. Now most often we don’t even work together anymore. Unless one has a job that forces them to come to the office or is one of that ~1% of the workforce that prefers to, and can have a chat at the water stand, I think for many people the reality is that if not for online games, they wouldn’t hang out with anyone anymore


  • You know where there term “AAA” comes from, right?

    Games used to be a niche - made by gamers for gamers. Now it’s gotten more mainstream so we have more industry around it. Good games aren’t gone, just don’t get advertised, same as everything else that is worthwhile

    As for social aspects of the games, I don’t agree with your take. We don’t have time to be hanging out in pubs every weekend anymore. Hopping in VC to do some “base building” requires less scheduling