Admin of lemmy.blahaj.zone
I can also be found on the microblog fediverse at @ada@blahaj.zone or on matrix at @ada:chat.blahaj.zone
@lemmy.blahaj.zone
Admin of lemmy.blahaj.zone
I can also be found on the microblog fediverse at @ada@blahaj.zone or on matrix at @ada:chat.blahaj.zone
I had no idea Olympus/OM gear was hard to find in Australia, I wonder why?
I mean, that was decades ago. Digital wasn't the only camera market, and Olympus was a small part of the larger camera market, so it was a niche within a niche. We could get lenses, but they took a long time to arrive, were over priced, and sometimes simply weren't stocked.
These days, they're harder to find simply because Olympus/OM is a small player in the digital camera market. There's still plenty to go around, but sometimes, only in small numbers, because of the limited market for them. But online ordering is easier now, so it's pretty much a non issue overall.
For what it's worth, I absolutely want to see duplicate communities across multiple instances. Even if it's a backup community, folks shouldn't be left without a space if an instance goes offline, or if an admin goes rogue. I want to see more communities for vulnerable folk across more instances.
I wish there were more queer first instances too, and hopefully, this incident pushes someone in to spinning one up!
She doesn't care about maths. She cares about making the bigots feel confident enough to express their bigotry. She wants her voter base to feel powerful and also persecuted, so she'll switch frames of reference as needed.
It looks like IP addresses are stored in the DB in lemmy. It's possible that the attacker had access to those IPs, but we don't believe they accessed them.
This is the sort of thing we would turn off if we could :\
We run our instances across multiple servers, but the postgres databases are all hosted together on a single server, though technically not a single server, as, at the time of the attack, we also hosted a backup database server, which was spec'd to backup our instances, but not serve them. Their access was limited to the main postgres server, but that server holds the databases for all of our instances. It looks like the script they used in the postgres exploit to give them local access interfered with the cleanup/backup process, so WOL files would get written, but not deleted, which filled up the disk on the main machine, and ultimately, caused it to fail over to the backup machine.
In theory, they could have used the same script/exploit on the backup machine, but because it wasn't spec'd to serve all of our instances at once, everything fell over at this point. That is what alerted us to the issue, and also limited the attackers available time in the system.
That was kinda my feel as to what happened as well. It feels like if it was someone targeting us specifically with a multi layered attack, they'd have done something more overtly hostile. Deleted our data, defaced our site, or something. But the fact they don't seem to have done much of anything after getting in there, and the fact that there wasn't much in there of much use in the first place felt at odds with the sophistication of the attack. Which is why I am leaning towards it being driven by an LLM
We just ran out of time to get Piefed back yesterday (Australian time). We're also navigating around moving house and the Kaity's day job. It will be up as soon as we can today (It's currently 7am here)
It's useful for smaller servers. Basically, the only remote content that a fediverse instance sees is content produced by a remote account that a local account is subscribed too. So the more users subscribing to remote content, the more content that everyone sees. But in small servers, without a huge amount of incoming content, it can be hard to get a broader view of the fediverse.
This is a way for people on smaller fediverse instances to pull in broader content, because anything that tags.pub sees with the hashtag, gets pushed to your local server.
When I first got in to photography (just when digital was gaining ground over film), I pretty much fell in love with the Olympus approach, because they were doing things no one else was doing. I moved to Canon because it was just too hard to find Olympus lenses in Australia. I never loved Canon stuff though. So I was glad to return to Olympus (or OM Systems) and find that they still scratched the itch they had back when I first started. And the lenses are easier to find now (though still harder to find that Canon, Nikon etc)
Because stirring up hate against vulnerable minorities, by positioning them as a threat is a well tested and effective technique for the power hungry to gain and retain power. And it's effective, because it works by pulling people in and making all of the conversation about whether or not it's right to hate on the group they're targeting.
I thought this was meant to be on good terms? What about your post is fostering good will? It's nothing but trashing on me...
To be clear, every post and user I removed was due to queerphobia, transphobia, trolling or spam, issues that broke the instances rules. Some of that bigotry was was implicit rather than explicit, like dog whistles, tone policing etc. Some of it was the "just asking questions" transphobia that pervades most corporate owned social media spaces.
This is the way I have moderated this instance from before the time I handed this community to moss. When lemmy was just taking off, I asked for people to mod the 196 community after it was abandoned by its original creators, and passed it over to moss when she raised her hand.
So if the goal is for this to be civil, maybe don't paint me as the bad guy for moderating in a way I have done from before your community was created here. What feels like "moderating by vibes" to you, is lengthy experience with community development, and a decade navigating queer and gender diverse communities, and knowing what I want from them. As moss said, this is ideological differences in how low grade transphobia and queerphobia should be dealt with. moss is ok with community pushback for the low grade stuff rather than moderation, whereas I'll just remove it.
That's what I wouldn't compromise on, and that has been the way the instance has run for years now.
It feels like every time I extend 196 a hand, you bite it. I gave the community to moss and started this whole thing. I told another instance admin no when they asked 196 to remove their banner. moss then went and leaked the DMs from said admin, forcing me to remove the post, and then had a public complaint session about me for removing the post.
I have asked 196 for years now to have an active blahaj.zone mod so that someone can deal with the blahaj.zone reports that constantly come through and build up, but still, the best we got were mods with alt accounts that get checked every couple of days, leaving me to deal with the build up of reports on 196. Sometimes they would hang around there for days while I waited for a 196 mod to log in and look at them. And because you don't like the way I deal with them, you drag me over the coals for my moderation style, despite no one from 196 stepping up to deal with those reports on a regular basis.
I was told that you were thinking about moving to another instance. I offered my support if you decided to stay or to leave. And that was the last I heard of it, until one of your mods (possibly you if I remember correctly) told the community you were organising something with lemmy.world, and I had to hear that second hand. And then, when things were finalised and the decision to move was locked in, once more, I heard about it second hand, after your team made a public post, because no one from 196 could be bothered to tell me before posting.
So no, you don't get to paint me as the unreasonable admin who moderates by "vibes". If you want to point the finger at me, at least own your own mistakes, rather than asking for good will and civility and then dumping on me when the chance presents itself.
thanks for using Leebra!
go to feed...