I have seen a lot of calls around Lemmy for more moderation tools. I have been working on Lemmy PowerShell module for a few weeks now, and I went ahead and released a preview version with multiple moderation tools now available. The module has the ability to perform the following tasks using a simple command line tool:

• Search posts and comments
• Remove a post
• Remove a comment
• Lock and unlock posts
• Add and remove moderators
• Create new posts and comments

You can get started now by installing the module through the PowerShell gallery.

Install-Module Lemmy-preview
Import-Module Lemmy-preview

If you are not familiar with PowerShell, I've include detailed instruction in the GitHub repo with lots of example. https://github.com/mdowst/Lemmy-PowerShell

If you run into any issues please let me know either here or by submitting an Issue to the repo.

I have seen a lot of calls around Lemmy for more moderation tools. I have been working on Lemmy PowerShell module for a few weeks now, and I went ahead and released a preview version with multiple moderation tools now available. The module has the ability to perform the following tasks using a simple command line tool:

• Search posts and comments
• Remove a post
• Remove a comment
• Lock and unlock posts
• Add and remove moderators
• Create new posts and comments

You can get started now by installing the module through the PowerShell gallery.

Install-Module Lemmy-preview
Import-Module Lemmy-preview

If you are not familiar with PowerShell, I've include detailed instruction in the GitHub repo with lots of example. https://github.com/mdowst/Lemmy-PowerShell

If you run into any issues please let me know either here or by submitting an Issue to the repo.

This is a pretty neat tool that allows you to use regular git commands, but captures the output as a PowerShell objects. This allows you to use the power of PowerShell pipelines to enhance your git experience.

A couple of examples:

# Count logs by author
git log |
        Group-Object GitUserEmail -NoElement |
        Sort-Object Count -Descending

# Delete all branches except the current and main
git branch | 
        Where-Object -Not IsCurrentBranch | 
        Where-Object BranchName -NotIn 'main', 'master' | 
        git branch -d

What happens to PowerShell scripts using Azure AD, Azure AD-Preview, or MS Online modules on June 30, 2023?

There will be no impact to PowerShell scripts using these legacy modules on or after June 30, 2023. They will continue to function and be supported until deprecation announcement.

What happens to PowerShell scripts using Azure AD, Azure AD-Preview, or MS Online modules after March 30, 2024?

We plan to deprecate Azure AD, Azure AD-Preview, and MS Online PowerShell modules on March 30, 2024. After this date, the only support offered for these PowerShell modules will be support in migrating to Microsoft Graph PowerShell SDK. Only security fixes will be offered for these PowerShell modules after deprecation is announced. Once these modules are deprecated, they will continue to work for a minimum of six (6) months before being retired.

PowerShell Weekly is a hand curated list of PowerShell news, blogs, scripts, etc. that I discover each week and feel are worth passing on. In other words it is not just me reporting everything with a PowerShell hashtag.

There is nothing to sign-up for and there are no ads. It's just my little way of giving back to the community. I also do not accept any sponsored content, but I do take recommendations and suggestions from the community, so feel free to send things my way.

I try to get it published by 9 am US central time (2 pm UTC) each and every Friday. (Expect for the week between Christmas and New Years, I give myself that week off)

It has been going strong for 4 years now and the entire back catalog is searchable and tagged with categories, authors, and timeframes.

I want to make this a place that everyone can get the most out of. So, I've been working on a list of guidelines/rules for this community. Instead of just posting them in the sidebar, I thought I would post my proposed rules here first to provide everyone a change to provide feedback.

So, please let me know if you have any thoughts or suggestions.

Rules:

• Be civil (aka don’t be a jerk). Remember there are people from all walks of life, all with different levels of expertise. You can disagree with someone, but please be civil when doing so.
• Adhere to the Lemmy Code of Conduct
• Follow all programming.dev rules
• Posts must relate to PowerShell or the PowerShell ecosystem.
• Use code blocks to make things easier to read.
• Memes and humorous posts are allowed but try not over do it. And keep them relevant to PowerShell
• No discussion about piracy or hacking.
• If someone provides an answer that solves your problem, please reply, so others know what the solution was. ^And^ ^so^ ^the^ ^person^ ^who^ ^suggested^ ^it^ ^gets^ ^that^ ^oh^ ^so^ ^sweet^ ^shot^ ^of^ ^dopamine.^
• If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!

Self-promotion rules:

• Self-promotion content must be marked as [OC]
• Do not SPAM. Content must be PowerShell related.
• Only 10% of your contributions can be self-promotion. In other words, 90% of your contribution must not be self-promotion.
• Personal blogs are not considered self-promotion, at this time, as long as they are free to access and relevant. Please do not abuse this.

Also, let me know if you are interested in helping moderate this community.

tl;dr the upcoming replacement for PowerShellGet