Mildly Infuriating
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.
view the rest of the comments
Friendly reminder: If you know how to use Docker, you can self host Invidious on your PC and have an experience better tgan YouTube for free.
Invidious alone has been working quite badly this year (stopped working for months until inv-sig-helper was invented, etc), but combined with FreeTube it almost always works; can recommend.
I've done this for about 6 months, I've had a very mixed experience with Invidious, mostly with YouTube constantly making changes without notice or the video stream not really supporting resuming if the connection breaks briefly.
This isn't a comment on the Herculean effort the contributors are taking on, but new users should be aware that they need a very reliable connection, update the container regularly, and exercise patience in the current state of Invidious.
YouTube has litterally attacked it by blacklisting all know cloud IPs world wide when tmaccessing YouTube.
Self-hosting is the only reliable way. Sometimes, YouTube breaks something, but after a few hours, Invidious pushes a fix...
But if you target the latest tag of all relevant images, itms just:
docker compose pull; docker compose down; docker compose up
Yeah, anything to make that line go up on YouTube's end.
The latest tag still doesn't support multiple audio tracks, which might sound niche, but YouTube just rolled out AI dubbed audio tracks, and so Invidious can just play the wrong track and you can't do anything about it and it's been this way for about a month.
That being said, it seems that the team's plan is to put more dev time into changing the back end to video.js so they don't have to brunt the video retrieval workload, and video.js supports multiple audio tracks as far as I know. I look forward to when that happens, but in the meantime the latest tag is not 100% usable :(