Fair enough. I was more just trying to say that dogpiling on the guy wouldn’t change anything.

As far as them showing their ass again, I’m pretty sure that by the time you made this comment, they had already made their “public statement”. And doubled down.

They claim that the targeting of trans/queer places was due to the violent rhetoric they saw going on in the spaces. Surely it’s against deserving targets, but this guy feels that calling for the death of people isn’t ok no matter the target. Theoretically if there had been spaces not allowing that, they wouldn’t have blocked those ones.

We won’t know because the spaces that do exist do also allow it. Personally I think that people should be able to express those extreme emotions, and that other people shouldn’t be forced to see it if they don’t want to. Personal filters, potentially based off crowd-sourced lists are what makes sense to me. My issue with this whole thing is that they did it secretly, and did not actually give users options to opt-out. Then at that point there’s not even a point about arguing what the motivations were.

But as it stands, the guy’s an ass. And confirmed it in less than 12 hours.

As of around 7 hours ago, there’s a closed issue on the repo’s tracker from someone upset they were on the secret list, and the maintainer closed the issue stating that they’d make an official statement once everyone cooled off. Also that the issue tracker wasn’t the right place for that discussion.

This indicates that they are aware of the threads about this stuff here on Lemmy.

Please don’t dogpile the issue tracker, and give an opportunity for cooler heads to prevail. Trust that if they’re a piece of shit it won’t take long for them to confirm it (again) loud and clear. Not saying this isn’t a whole big bunch of bullshit, just that they should at least get a small opportunity to respond with their side.

If you hand someone a shovel and they use it to dig their hole deeper instead of filling it in, it’s even more fun to watch them fall in.

Yeah, I really wanted to believe this was just a personal filter list that got included accidentally, but there’s no fucking shot. The way it’s implemented and intentionally obfuscated means there’s no way in hell this isn’t entirely intentional.

People can work around a horrifying amount of mess for a dizzying amount of time before it all comes crumbling down due the wrong thing occurring at the right time.

All of these examples are from finance companies, mostly banks. Not all my stories, these include stuff from friends in the field.

I know a place that had no documentation on access revocation for >30 third party systems.

Another with no Identity and Access Management policy until the pandemic. Service accounts with god level access? Go ahead and set an 8 character password with no expiration date, and never change it after 20+ employees who know it leave.

One place with software that sits installed on computers within reach of the public where every client copy includes a password decryption function in a file that you can copy out of the client install and then just call it from whatever program you write. Yeah, you still need read access to the user database’s password field, but this was software that employees used to interact with bank accounts. With trivially reversible decryption.

That last software was slated to retire over a decade ago, and last I heard was being kept alive by the finance company paying for source code access and maintaining their own edited version themselves. The last time my friend talked about it a year or two ago, the software was just shedding its reliance on Internet Explorer and shifting to Edge.

Some federal processes and laws still require fax communications for various financial shit behind the scenes.

Do what you can to steer out and away, keep your hands off it/don’t perpetuate it, have a threshold for “fuck it, not my problem to fix”, have another threshold for “fuck it, let it burn or they won’t learn”, have a third for “fuck it, I’m running before this eats me”, and always always always cover your ass. In writing, hard copy somewhere you control and work doesn’t.

Ultimately, remember that companies don’t reward heroics. Unless you can quantify your improvements in manager-speak, it won’t even register to them. They don’t give awards out for burning yourself alive to keep the engines running for another day. They give out penalties when your changes result in temporary setbacks during adjustments to the new normal.

There are many, many, many people in management and elsewhere that do not learn until they’ve been bit in the ass (if they are capable of learning at all). If you eliminate the friction before they feel it, they won’t know you’ve done anything at all. You want to look good, that’s how you move up. Let some things fall. Let some things break, especially when you know the fix is relatively easy and no one wants to take responsibility to ok it before SHTF.

A ton of this job is managing people, at least as much as it is managing complex systems. Not to be sociopathic, never forget the people are people, but start looking at corporate interactions and politics like you might look at a complicated system with no or little documentation.

Most 365 mail admin work doesn’t end up touching the routing stuff, domains, or DNS records too often, so I’m by no means an expert. Last year I got rid of the last on-prem exchange servers in our environment. Here are my thoughts anyway, for what its worth.

At my workplace, domain as internal relay was used as part of our hybrid exchange setup, where we still had an on-prem exchange server largely for recipient management (for stuff connected to AD objects and thus mastered on-prem instead of in the cloud) and for a mail relay for internal recipients so that automated emails coming from legacy systems bypassed all filtering. I’m not familiar with other use cases.

Stuff that may not apply (minimize the lift)

I would approach this by using it as an opportunity to raze those hundreds of redirects. Surely the recieving systems have other ways to categorize incoming email than destination address. Stuff like system to system you could probably add shit in the body text and change the filters on the recieving end. So each external system would only have one destination address. That’s ideal world though and probably touches a lot of shit outside your control.

Second thing is that I would look into setting the destination email addresses directly in the sending system. It takes management out of your hands, but why does any of this need to hit your infra in the first place? Again, that’s ideal world and also probably touches shit you don’t control.

Point is, I’d look to minimize how many of these things you actually have to deal with, because they’ll just keep being a problem and a pain in the ass to manage forever otherwise. That’s the real underlying problem, if you can do anything about it.

Stuff that more directly lines up with your ask:

If you can script routing rules you can probably figure out scripting the creation of contact objects in 365, and export of them to csv for verification.

PowerShell is going to be your friend with Exchange Online/365, and most things Microsoft. Exchange Online has a dedicated module (think library if you’re used to terminology for other languages).

You can make a csv with the internal email address, external destination address, internal contact name, display name, and whether or not it’s hidden from the address book (do end users need to send to it?). I’d reccomend using some clear prefix in the internal name to keep them obvious compared to any other contacts not related to this fuckery.

You could use full mailboxes and forwarding rules on each one but that increases complexity significantly.

In PowerShell, you’d connect to exchange, import the csv, then foreach over the csv contents throwing the values from it into New-MailContact.

If you want to be fancy you could wrap New-MailContact in a try/catch to spit failed ones out into an array and export that back to csv at the end for review.

Not really well, at least to my knowledge. Neither of the options I’m aware of work with mobile apps for lemmy.

There was some site that would attempt to auto redirect to a person’s home instance, and there are a few userscripts for browsers that try to do the same thing with normal instance specific links like yours.

There is a lemmy redirector app for android that tried to work like the userscripts, and maybe I’m not using it right, but I’ve never gotten it to work on my phone alongside lemmy apps.

This came out a day or two ago, which removes that hurdle: https://lemvotes.org/

Just paste the permalink in. Works on posts, comments, and users.

It was only a matter of time.

If I understand it right, each real piefed account gets an associated “shadow account” used for voting and the piefed instance admin that the account is from can correlate the two if needed.

I think you should post this over to !fedigrow@lemmy.zip or one of the other communities for growing lemmy and helping new joiners. You are likely duplicating effort.

We can filter out NSFW work

[citation needed]

I have that turned on, and I heavily lean on blocking communities and users, and I still get NSFW shit fairly regularly.

Maybe make use of the existing blocking features, and use a client that has keyword filtering?

I’ve been able to get my experience pretty damn close to as filtered as I want it just with community, instance, and user blocking.

Who decides what is “without a doubt”?

Everyone’s personal barometer is going to vary on that wildly.

If each instance decides on their own usage, then it no longer becomes a useful filter. We already see this with the NSFW tag (god forbid I ask for it to be put on a post showing the business end of a fleshlight hanging out the rear end of a stuffed animal dog, that isn’t nsfw apparently because it’s not real nudity or something).

From one coder to another: This is classic coder overconfidence. The complexity isn’t in the hypothetical code but in the people and how the feature may or may not be used.

Explodingheads is going to have a distinctly different idea of “political” than Lemmygrad.

The Fediverse has few enough daily users that you can block political communities and the people who post overwhelmingly political content outside of those communities.

You can also use one of the handful of clients that allow keyword filtering.

Don’t let the perfect be the enemy of the good. That said, it’s vanishingly rare that I’ve regretted designing something for long term use rather than just hacking it together.

Taking the extra time to document stuff, to add guard rails/error handling, to make a piece of script easier to re-use, to actually plan something rather than building it as you go… almost always a good use of time.

More features for our employee account lifecycle automations. The coding isn’t as much the hard part as keeping track of all the different moving pieces and how it all interacts.

For example, when using Azure Enterprise App user provisioning to sync data into AD from an HR system, it can only set the Name (separate from DisplayName) property when creating a new user. This limitation isn’t documented anywhere I can find, and it doesn’t even show as an error in the logs when it tries to update an existing one and fails.

It’s the curse of “one man army”: this shit is too complicated to keep it all in my head at one time, and also too complicated to bring anyone up to speed in a reasonable time frame. So I’ll continue soldiering on with it on my own. Thankfully the end is in sight.

Don’t do this sort of shit for any boss that isn’t worth it. Mine has no overtime expectations, is very obviously training me to move upward within the team, and each of the last two years I’ve gotten >10% raises.

Yeah, that’s the big issue with Kodi. Good luck getting any legitimate streaming services to work at more than 720p at best. And you can forget about library integration with those legit streaming service addons too.

The best user experience is trying to find the most trustworthy pre-packaged/configured pirate “version”, and optionally paying for realdebrid.

Yep, and don’t just state the what, but the why in your docs.

The why really helps with knowing if a step is still important, or if it no longer applies. This is especially important with anything cloud based, as I’ve seen weird workarounds become no longer needed due to updates, and I would never have caught it without my notes on why we had the weird workaround to begin with.

Outlook has “rules” you can configure to route incoming mail into different folders and mark as read (if you have access to their web client, configure the rules there so they run even when the desktop client is closed).

I know Google’s web interface has similar features. If it’s not built into Thunderbird then I’d be shocked if there wasn’t an extension for it.

This is the norm. They have settings in Group Policy for a lot of this (sans the teams opening in edge, that is absolutely utter horseshit).

The regedit you did (and most regedits to “fix” stupid default settings) is a manual version of the GP setting to just disable web search in the start menu.

If you don’t use Windows with a Pro license, and you stay with Windows, next time buy a Pro license from a bulk OEM Pro License seller for cheap (or look up the latest way to spoof licensing and get it for free), and get access to Group Policy. It’s effectively Control Panel/Settings menu on steroids for corporate sysadmins.

I swear that 80% of peoples complaints with Windows can be handled with Group Policy. Shit that it’s locked away from the average user, but the average user literally can’t tell the difference between web browsers if you make the shortcuts have the same icon.