Community for posting any moments where software unpredictably malfunctions to do something it was not intended to do

Links:

• !software_gore@programming.dev
• /c/software_gore

Hey everyone! Ive been working on an event called safe crackers for instances to compete in

Im planning to hopefully run it around february so that its run 6 months apart from !canvas@toast.ooo

Essentially how it will work is each instance has a safe with a 20 digit password. Users of the instance have 100 points, and must set a 4 digit password and attempt to guess the passwords of users in other instances. If a password is guessed then they steal all of the points of the user they guessed.

To help guess passwords clues will be given which when solved will give one character of the users password. Clues will need to be solved using things like community names, post titles, etc. relating to the person

Each user only gets a certain amount of clues every so often so you would have to pool your clues with other members of your instance

If you guess a password you have a chance to get a clue for that instances 20 digit safe. If the 20 digit safe is broken into all of that instances points are stolen and that instance is eliminated

Details might differ a bit in the actual event since im still fleshing it out a bit but it should be similar

Currently thinking the top 20 instances in terms of MAU will be competing and the rest will be under a joint group for a total of 21 groups.

Ill be posting progress updates here on me constructing it and will be running a beta ahead of the actual event to test it out

Less than a month until advent of code begins https://adventofcode.com/

Ill be attempting to make this community active leading up to it and during it

Hey everyone, I just finished up a new bot for the instance called Link

This bot aims to give suggestions for other communities in the instance to post to to start populating the more specific topic communities. It currently is triggered just off of keywords it finds in post titles.

This should help people find other communities after they post to !programming@programming.dev and encourage cross-posting in the instance since thats recommended (and standard lemmy behaviour is to show crossposts as one post in the post feed)

I added some of the communities in the instance and will go through and add in the rest of them shortly

Hey everyone! I added some new taglines to the instance to more than double the amount of them we have. You should see the new ones popping up at the top of the home feed

New taglines were taken from the !quotes@programming.dev community and https://http.cat and were currently up to 96 of them

Hello everyone! I've pushed out a public alpha build to https://beta.pangora.social for people to start giving feedback on the design before it becomes more fleshed out

Feel free to check it out and say what you like or dont like in the comments here.

The UI there is currently pointing to the programming.dev instance

⚠ Warning: This is an alpha, things are still very unfinished. You cant use this as an alternative to lemmy-ui yet since things such as logging in aren't supported

⚠ Warning 2: If you attempt to use this on mobile currently it will be very broken

I constructed the UI by seeing what people liked from lemmy-ui, alexandrite, and photon and trying to match it up to how lemmy-ui is built so that it would be an easy switch between them

Main site mechanics that is different from lemmy-ui

• Comments from cross-posts show up when looking at a post (will be changed in the future to only communities that community has whitelisted to do it for once I mess around in the backend more)
• Comments and posts that have 0 or less score in terms of upvotes/downvotes will be collapsed by default
• Clicking on a post in the post feed makes it show up overlayed on top of the feed similar to alexandrite's system instead of sending you to a new page. (hitting the name of the post when in this preview state will send you to the actual page)

Images:

Hello everyone! I've pushed out a public alpha build to https://beta.pangora.social for people to start giving feedback on the design before it becomes more fleshed out

Feel free to check it out and say what you like or dont like in the comments here.

⚠ Warning: This is an alpha, things are still very unfinished. You cant use this as an alternative to lemmy-ui yet since things such as logging in aren't supported

⚠ Warning 2: If you attempt to use this on mobile currently it will be very broken

I constructed the UI by seeing what people liked from lemmy-ui, alexandrite, and photon and trying to match it up to how lemmy-ui is built so that it would be an easy switch between them

Main site mechanics that is different from lemmy-ui

• Comments from cross-posts show up when looking at a post (will be changed in the future to only communities that community has whitelisted to do it for once I mess around in the backend more)
• Comments and posts that have 0 or less score in terms of upvotes/downvotes will be collapsed by default
• Clicking on a post in the post feed makes it show up overlayed on top of the feed similar to alexandrite's system instead of sending you to a new page. (hitting the name of the post when in this preview state will send you to the actual page)

Images:

Had some more free time to work on the pangora.social site so I pushed some support for the new fediseer tagging system so that it automatically populates instances in the instance selector.

Instances will populate in it if they:

• Have more than 50 members
• Are tagged with a tag for the site
• Are not censured by programming.dev or some other instances
• Can be found when the site checks for instances every day

A list of all tags that are used on the site can be seen at https://pangora.social/tags separated into categories.

I also pushed a little fix to the site so that if theres no instances in a category that category won't show up

Hey everyone, update on https://programming.dev/post/4613085

We did some changes in the database and it seems like outbound federation is working again. If you run into any more problems with it let us know.

Im pinning this post for around a day to let everyone know since we had the last post pinned for a bit

Any posts or comments made while it was broken still wont be federated but new ones should be. The instance essentially marked all other instances as dead which meant it thought it didn't have to send things to them

Hey everyone. Currently the instance is being affected by a bug that prevents outbound federation. This seems to have started when the instance upgraded to 0.18.5

Im pinning this post in the instance while it is affected by the bug so everyone is aware as this affects everyone in the instance

Theres an open issue on the lemmy github repository and we are attempting to track down why this is happening and fix it

https://github.com/LemmyNet/lemmy/issues/4039

What the bug means is essentially

• We still get all posts and comments around the fediverse like normal (so youll see posts made in other communities populate the feeds like normal)
• Posts and comments made by users in programming.dev are not visible outside programming.dev

Hopefully itll be resolved soon. If anyones able to get some info that would be helpful towards resolving the bug throw it here or in the github issue

Hey everyone! I'm back from doing things for Ludum Dare and am starting work back up on Pangora.

Spent a bit setting up a backend so I can start implementing some backend features such as flairs and started some progress on the admin settings in Pangora-UI

My current plan is to add two new features onto the backend and then clean up and add everything from lemmy-ui that hasnt been added already to get it ready to be publicly tested. After which will be aimed for a first release

Flairs

The first feature being added is going to be flairs which is the main thing that ive noticed has been lacking when interacting with lemmy.

Flairs are split up into four different types

• instance flairs
• community flairs
• post flairs
• user flairs

Instance Flairs

Instance flairs are flairs set on the instance/site level to show what kind of content your instance contains. For example for programming.dev we can instance tag ourself with programming and mander can tag themselves with science. This can then be shown in the site sidebar and to categorize instances in sites such as https://pangora.social .

The instance flairs available will be the same across instances so that a consistent instance flair naming system can be enforced but people can freely request new flairs from the repo if theres one thats missing.

Community Flairs

Community flairs are set on communities to show what kind of content that community contains. These can be created by instance admins and set on a community by community mods

A community flair for programming.dev might be gamedev (to put on godot, unreal_engine, gamedev_news, play_my_game, etc.)

Post Flairs

Post flairs can be set on posts to categorize posts in a community. In a community about godot some posts may be tagged as help if its a help request, or news if its something such as news from the godot blog.

These flairs can be created by community mods and have a setting to make them either only able to be set by mods or be able to be set by both mods and users.

User Flairs

User flairs are community-specific and can be set on a user in that community. People might add a flair onto themselves if theyre an official developer for a software, or for more cosmetic reasons to theme themselves around the community

Admin Permissions

Second thing I want to add is different permission levels for admins. Currently adding an admin to your site gives them access to basically everything on the site. This can cause issues if you for example only want to add someone who can accept applications but dont want to give them access to causing chaos with your site information.

Entering a new permission system for admins. How this is going to work is new roles are going to be able to be created in the site and set to have different permissions. You can create an accepter role that can only accept applications, an emoji master role that is able to create and delete emojis on the site, an admin trainee role that is able to do most things in the site that can easily be reversed, and a standard admin role that is able to do everything.

Permissions are going to be all booleans and able to be stored in one variable length integer per role with one bit per permission (with the bit set to 1 if that permission is given, and 0 if not)

Admins with the role managing permission are going to be able to create and manage roles below them to add some new ones to the site. Instance owners have every permission by default and are at the highest level in the role chain and this cannot be changed without transferring the site ownership.

Ending Note

Thanks everyone for joining and watching the progress here on pangora! If youre interested in helping out feel free to join the matrix and I can help get you set up with the codebase. https://matrix.to/#/#pangora:matrix.org . Backend is in rust and frontend is using Next.js with TypeScript

This is something I'm currently working on part time with most of my time going to university (and some time going to gamedev) but as progress is concentrated on a couple features it still should be getting some good amount of development done. Its also downstream from lemmy so any updates and bug fixes the lemmy devs make will also be merged into Pangora to help keep the two as close as possible (and ill be making pull requests into lemmy once flairs and admin permissions are stable for them to accept or not. )

For transparency on who I am. I'm a computer science student in Canada currently mostly doing work in gamedev and webdev. I try to run AMAs every so often here in !iama@programming.dev and should be doing another one soon if anyone wants to ask me some questions there. Ive been mostly doing work on managing communities here in the instance but ive been onboarding some new admins and will start mostly working on development of Pangora in the future.