It wasn't for nothing.
Think of the skills you gained and the experience.
this post was submitted on 30 Jun 2023
118 points (94.7% liked)
Mildly Infuriating
35595 readers
975 users here now
Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
founded 2 years ago
MODERATORS
And a chance to post it here!
And all the larma to gain!
Larma^ That's how I'm calling it now
Winamp. It really whips the Larma's ass! Baaah
At least you got yourself into the contributing mindset. Tackle the next issue!
It be like that sometimes
Hey, if not this one then the next one. Onto the next bug!
Lesson learned, always pull and branch from main.
Actually I was working on the main and that's where I saw it being fixed :D
I have another bug which is bothering me. When the site settings are set to "Registration Mode": "Close Registration", the Sign Up link still shows up and the route still sends you to the Sign Up form. You can fill in everything there but then will get a infinite spinner.
I wanted to at least remove the link at the top when sign up is closed. But obviously it's not as easy as changing a static HTML as in the other bug.
Plenty more bugs to fix, don't give up being a contributor!
My process is:
- Check for an issue that describes the bug you're seeing.
- If there isn't one, create one.
- If you feel like it'll be snapped up because it's a relatively easy fix, comment on the issue saying you'll give it a go.
- Fix it!
There is still a chance someone might swoop in and fix it but this lowers the chances and it's good to get into the habit of creating and linking Issues to your PRs.
That’s why you should always search for or file a bug report before trying to create a fix.
If it's a nice and easy bug, better just make a bug report out of it.
It's already fixed, no need for more paper.
You can just build a time machine and commit it before the other one. Problem solved.
I had this exact thing with Mastodon a few days ago. Couldn't find a way to get the local server's post-ID for a federated post if you had the original URL, so I thought "screw it, I'll do it myself".
Downloaded the source, set up a local instance, added extra space to my server so I could run ElasticSearch, went to the file where I wanted to add my "uri:" search prefix, and I find (to paraphrase)...
Send
resolve=trueto fetch remote instances and return their local ID
Been there for years.
That type of bug is what is called "low hanging fruit". With lots of active contributors, such bugs will get fixed pretty quickly.