[–] 3 points 19 hours ago

It was the deal breaker for me. The end of my 21 year relationship with steam. I don't give a shit that they've let me through because of the account age, the fact that they locked it down briefly and may do so again in the future means they can fuck right off

  • source
  • parent
  • context
  • [–] 16 points 1 week ago (1 child)

    All fixed. We had an issue where one of our servers reports space in use that isn't being used, and nothing short of a restart will fix it. We've done that, cleared up the space and upgraded piefed at the same time (and by we, I mean Kaity)

  • source
  • [–] 44 points 3 weeks ago (1 child)

    Admin hat on here.

    You need to be very careful about how you phrase topics like this. It's ok to express your opinion. It's ok to say that surgery is not for you and to be open about why.

    What's not ok is telling people that surgery, or any other aspect of folk living life authentically on their own terms isn't isn't for them either.

    You can talk about your own experiences and perspectives, but don't push them on to others

  • source
  • [–] 3 points 1 month ago* (last edited 1 month ago) (6 children)

    Aside from the name stub, which I understand your issue with, the things you mentioned are not the "lore" of that community. The stub itself unfortunately, can't be changed, but there is a reason community is called "Transfem" and not "MTF". The opening sentence of the sidebar is "This is a supportive community for all transfeminine or questioning people" for a reason.

    I've defederated entire instances and banned countless accounts over their exclusion of gender diversity outside of the binary and bigotry against otherkin.

    There are undoubtedly folk in the existing community that hold binarist views, and there are undoubtedly folk in there that hold cisnormative views, but that is the same of every trans community on lemmy including this new one. What matters is the response to those views being expressed, and that should look like education and awareness, which is I hope, how it will manifest in this community. Exclusive language steeped in transmedicalist perspectives is steeped in our history, because it was forced on us by cis gatekeepers, and that's impossible to completely escape from as long as people who lived through that experience are part of the community. And whilst that's history in some parts of the world, in many others, it's still a requirement to access care and support, and that harmful perspective that is forced on us, shapes many peoples internal view of themselves and their community.

    We can't make that go away with rules or a ban hammer though. It needs to be met with support example setting. If someone refers to their own experience in terms that lean on exclusionary language, a good response isn't telling them how they have to refer to themselves, but instead, showing them by example that there are more inclusive, open ways of thinking about their own experiences in the way you talk about your own experiences. Change comes from giving folk room to grown and showing them empathy whilst they navigate the unpacking of enforced binary and transmedicalist perspectives.

    Where it crosses the line is if people start to use that language to deny the experiences of others, if they double down on using language for other folk that other beings have said makes them uncomfortable, it's time for a moderator to step in.

    And that's what I'm saying to you or to anyone else reading this. If you do see exclusive language being pushed on to others, flag it, because it has no place in any community on blahaj.zone.

  • source
  • parent
  • context
  •  

    Firstly, apologies to everyone for the extended downtime. Unfortunately, it was for a pretty bad reason. We were hacked.

    The bad news is that it was a comprehensive attack, and the attackers had privileged access to our database system, across all of our services (except for writefreely, which doesn't use postgres). From what we can tell, the attacker did not do anything with that access, so we don't believe any user data was accessed, but we can't be certain of that. For lemmy, the impact of this should be minimal. If you registered with a real email address, they may have that. User passwords are encrypted in the database, so if you were using a secure, non trivial password, it should be safe, but you should still change it. You should also reset your 2 factor authentication if you had it enabled, as the seeds for these are not encrypted.

    Our understanding is that the attacker used a peertube exploit, then a postgres exploit and then a kernel exploit to systematically gain access to different layers of our database server. A side effect of the hack was that it filled up our database servers hard drive, and caused it to fail over to our backup, which we believe mitigated some of the potential fall out.

    We have had to reset activitypub keypairs for every account and community on lemmy, so there may be some federation hicoughs for a day or so, until remote servers have dropped any cached copies of our users public keys. This is uncharted territory though, so hopefully it's as smooth as we think it will be, but we can't be sure!

    As stated earlier, our writefreely instance is still up and running as it wasn't impacted by this attack. Vernissage (our pixelfed replacement) has been brought back online, as has our matrix server.

    We will be bringing up Sharkey, and then Piefed hopefully later today, but we have to rotate keypairs on those services too, which is also uncharted territory, so the timelines are hopes, not guarantees. At this point in time, we don't plan on bringing pixelfed back online, as it was slated for shutdown in August in any case. If people still need access to pixelfed to export data, we can spin it up briefly if needed, so please reach out if this is you. We also won't be bringing peertube back up at this point. It was not heavily utilised, and it was the source of the attack, so Kaity is a bit gun shy about spinning it back up on shared database infrastructure. If there is a strong desire to bring peertube back, we can consider doing that on isolated hardware, but at the current utilisation level, it doesn't seem worth the cost/effort to run it isolated.

    in any case, you can read a fuller explanation of the attack by Kaity here https://pen.blahaj.zone/supakaity/weve-been-hacked

     

    Edit - We're back!

    We've had an issue with our databases. One of our fast database servers ran out of space, and then the second fast server ran out of space whilst replicating to the first.

    As a result, we have fallen over to our backup database server, which runs on spinny disks rather than SSDs. Spinny disks means that it's got plenty of space to spare, but it's not fast. The backup DB server is currently replicating to our two main servers to get things back up and running again, but whilst that's happening, all of our services are running slow.

    The good news is, we'll be back up and running as if nothing happened because our backup server saved the day. The bad news is, it may take another 24 hours or so, because the backup server is reliable but not fast!

     

    We've been getting a few of these types of posts recently, so this is just a reminder. There are plenty of places we can find endless bad news. This is not meant to be one of them. Bad news has a place here, but only when it's part of a discussion that helps people move forward despite the negative.

     

    For those quick off the mark, you may already have seen her name appear in the list of lemmy admins! We've brought Jorunn on board, as she's already staff on our piefed instance, and she has been helping moderate lemmy via our admin bot, which can approve signups, delete spam etc. So, she now has her own keys to the castle to make her life easier!

    You can reach out to her for issues around community/instance moderation, regarding our lbz users etc. Kaity and I are still the best contacts for sys-admin related issues however.

    Anyway, welcome aboard Jorunn and thank you for taking this on. I certainly appreciate it :)

     

    Cross-posted from "Tawny Frogmouth (Podargus strigoides)" by @ada@piefed.blahaj.zone in !birding@lemmy.world


    This was taken in near total darkness, with a hand held, 300mm 1 second exposure. I love this camera and lens!

    And thank you to the Tawny, who was happy staying perfectly still for my long exposure :)

    #frogmouth #TawnyFrogmouth #brisbane #meanjin #bird #urbanbirdphotography #australianbirds

    Tawny Frogmouth (Not technically an owl, so don't tell the mods :P)
    view more: next ›