I've been writing PowerShell code for almost 10 years now, and I love it when I come across someone who uses interesting techniques and patterns that I haven't seen before.

Do any of you have a list of users in the community from which you've taken inspiration in your own code? Who are they? I'd like to follow them :-)

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

I started a project to interact with Lemmy via PowerShell. The current code was built off the Lemmy API documentation. This is a very alpha release, so please create issues in GitHub for anything you find. If anyone wants to help contribute to it please let me know.

Not OC

To kick off the new community here is a link to the month PowerShell call and the archive of past calls.

Come in, introduce yourself, and say hello to others. Hoping to build a friendly and helpful community