Enthusiastic sh.it.head

  • 13 Posts
  • 203 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle


  • I’d love to write a really good acid western. So far all I have are daydreams about being a badass old west drifter to the music of Spindrift.

    Edit: I suppose there’s also what I started when I tried (and failed) NaNoWriMo, which was a horror story about a pathogen that made people deranged killers of a spectacular nature. There was a fight in a stained glass factory, that was kinda cool. Should see if the laptop with the draft still boots…

    (If I recall the movie correctly, it was basically The Crazies, but more violent and written before the 2010 version came out [never saw the 1973 version])





  • Thing is, it’s not that uncommon to do this, and it’s not like the cashier is going to report you as suspicious to the relevant tax authority. Sometimes people don’t have the full value for groceries in their bank account, or are right at the tip of their credit limit - but do have cash on hand to cover the rest.

    The point is to have a paper trail/transaction history of lesser value for the tax man. Two transactions in one visit is just as valid as two different visits using different payment methods.

    Comes down to whether you feel awkward doing the first one I guess (cashiers generally won’t think twice about it, aside from maybe mild annoyance). It is a classic “Things aren’t going great for me rn” move - but who cares, you know the truth.

    (Ignore all of this and pay your taxes, people)







  • So far, that’s it in a nutshell - barring one account of potential cybersecurity risks coming out of that, which still makes some assumptions re: motivations I’m not 100% convinced on.

    I think there’s people on the ‘perhaps defed’ side who would want to argue it on points 4 from your immediate defed list, or 1 on the call to vote list - but personally, I’m not convinced the evidence is strong enough to do so compellingly.

    Regardless of the current discussion, it’d be wise for us to revisit your proposed policy as a group and see if we can make that official (with any relevant revisions from pre-vote scrutiny). I stand by what I said back then - it’s a solid list, and IMO worth being made official and saved somewhere broadly visible for later reference.




  • Gotta chime in here - part of why I made this post was exactly this reason. Apologies in advance for length.

    As someone who doesn’t participate in communities where political discussions are the norm, I haven’t had issues with lemmy.ml moderators or users. I know others have, but was uncertain how many other users on this instance experienced this, and if they felt the experience was bad/pressing enough that defederation should be seriously considered.

    As a personal aside, so far I’ve seen some very useful perspectives, but not enough evidence to seriously support defederation. The only elements that give me pause are Socsa’s concerns, but even then I don’t think the evidence is rock solid at this stage (though defed or not, warrant further consideration). This is just me though, I can’t speak for anyone else.

    I think imaqtpie’s POV is valid, though perhaps not phrased the best way (‘antagonize’ carries some connotations that might be distracting). The problems occur when engaging lemmy.ml on topics their mods are, IMO, overly and inappropriately sensitive about. It usually happens in communities where politically-focused discussion is expected. When this happens, they engage in what can reasonably be described as mod abuse. I think we can agree on that.

    Is this problem, and its downstream effects, such that all of lemmy.ml - all users without regard to political affiliations/interests/participation levels/whatever, all communities, etc. - should be cut off from sh.itjust.works entirely? If not, are there other approaches this instance should take to mitigate the problems that exist for its users [e.g. coordinating with other groups to migrate key communities off of .ml and support adoption? Community block lists that folks can use, that are one step below blocking a whole instance? Other things I can’t think of?]

    Ultimately, we cannot control how lemmy.ml manages their instance/communities hosted there. What exactly are the problems that causes here, what options are reasonable to address them, and how do users of sh.itjust.works want to deal with that. This is what I was aiming to suss out in opening up this discussion.

    Another aside: I see you are based at another instance (which is totally fine, all perspectives are welcome at the discussion stage). First question: Do you guys have a similar governance model to sh.itjust.works, and is defed from .ml under consideration? More important second question: if sh.itjust.works continues to be federated with .ml, would you feel it’s warranted for your instance to defed from us?



  • Edit: Added an additional choice - block whole instance at user level - to ‘option’ list. If you, nahuse, or anyone else have ideas for options f through zz, feel free to say so!

    Thanks for joining the discussion, nahuse! I appreciate the specifics you’ve provided.

    As an aside, you and a few others raise an interesting point re: archiving of deleted comments, particularly when there’s evidence of those comments getting removed from the modlog intentionally (I’m not claiming that this is objectively true - I don’t know, but it is one of the common claims in the broader discussion here and on similar posts). Seems like a worthwhile project for someone with the interest, skills, and time to develop. But anyway.

    Your experience does echo that of other politically engaged sh.it.heads* in this thread. I would ask - given the choice between
    a) blocking lemmy.ml communities with evidence of ideologically motivated moderation (either on a case by case basis, or as part of a community-sourced blocklist - something I mentioned here before but do not know can be implemented), and using alternatives for ‘controversial’ topics;
    b) blocking lemmy.ml at the instance level, as a user;
    c) joining an instance which is not federated with lemmy.ml;
    d) having sh.itjust.works defederate from lemmy.ml as a whole; or
    e) keeping things as they currently are, in terms of your engagement and ‘positioning’ [eg. Instance of choice, community engagement, etc.] - retaining the ability to try and engage on lemmy.ml communities with the same risk of ban/blanket ban, and talk about it there while enfranchised and elsewhere in the Threadiverse during ban periods.

    which makes the most sense to you/would be preferable?

    The dynamics of Lemmy instances are kind of interesting, as each can have very different approaches to moderation. An instance admin may simply have a policy of “Please just don’t post anything that’s going to make CSIS or the RCMP knock on my door” (Canada bias here), and individual community moderators either a) apply an even hand with that edict in mind, or b) apply and enforce more restrictive policies. Others may have a more consistent throughline based in interests, political beliefs, and so on - which seems to be the case for lemmy.ml and is why we see these blanket community bans over innocuous comments.

    I’d like to touch on that ‘innocuous’ point - what I’ve personally seen results in bans/deletion looks like fairly bog standard internet political discourse (alongside legitimately not cool stuff, but that’s not in scope at the moment to tease out). You present a point, you get a counterpoint, things get a little heated - with the difference that the person with the heated ‘not our flavour of far-left discourse’ comment has a much higher risk of getting ban hammered.

    I don’t think this is ok - but at the same time, this is a moderation choice of a specific group using a specifically allocated set of resources. Alternative communities exist, and can be used, that may not have this problem (though someone will always find something to complain about re: moderation practices, tale as old as the internet)

    There is, of course, the stickier point of lemmy.ml being not necessarily the main instance (see imaqtpie’s post, makes some good points), but the Lemmy dev’s instance. I don’t think the problems people have with lemmy.ml (usually in global events and political discussion communities - unfortunately resulting in blanket bans from unrelated communities on the instance in some cases) extend to the tool/protocol itself [see: exploding-heads, all of the more distasteful instances that exist], but this may be a concern for some [see Socsa’s comments here]. It may raise concerns/doubts about Lemmy as a whole. It sucks - I love this thing - but it shouldn’t be unacknowledged.

    *If you haven’t seen this term before, it’s what I like to call users of this instance (much to the chagrin of some :) ). Think Deadheads - enthusiasts of sh.itjust.works. A little cheeky, but ultimately good natured and fun - which kind of sums up my feelings about this place. We love sh.it.heads - not to be confused with shitheads.



  • Lol, fair. I’m still not well versed in inter-service ActivityPub stuff. I don’t know if you’ll see this or see any of the parent comments here on Lemmy.

    Contingency plans if IA loses the appeal about the library stuff, or in general has something happen that puts IA’s collections at risk of being lost. Any thoughts on the matter? Also cool if it’s not something you want to talk about, I know you don’t speak for the whole org.

    How do we archive the archive?