I prefer the SemVer Major.Minor.Patch approach so I can tell at a glance if the update breaks compatibility or is just bug fixes. Technically the Patch part can be any number as long as it increases each update of that same Minor version, so one could write the versions as AA.BB.YYMMXX where AA is the Major version, BB is the Minor, YY is the two digit year, MM is the month, and XX is just an incrementing number.
I think this approach has the best of both systems.
I always remember the difference by imagining them as lines on a graph. Forward slash is the line with positive slope and backslash is the one with negative slope.
The most convenient userscript for me is this one that automatically likes YouTube videos. It’s configurable to be able to: like the video after a specified watch percentage, ignore already disliked videos, only like videos from subscribed channels, and ignore livestreams. I like it enough that I’ve made a few pull requests to fix it when YouTube changes their UI.
When I have the time, I work on an in-progress local version to implement a few new features including: (1) Support for the YouTube shorts UI. (2) An option for a notification/toast to appear when the video has been liked. (3) An option to check the watch percentage continuously (mutation observer) instead of a user-defined poll rate which sometimes misses liking very short videos in playlists. Eventually I’d like to port something like this as a YouTube ReVanced patch.
End time zones. Instead of converting what time it is somewhere else, I’d rather convert what time dawn/mid-day/dusk is.
Wow, 18 years old. Born as a result of puppy milling, then put into a shelter after the mill was shut down. I would not expect a dog born in those circumstances to be as healthy as to live for that long. The owner obviously took very good care of them and I’m sure they lived a very happy life.
What about the other 98?
deleted by creator
Bah-weep-Graaaaagnah wheep ni ni bong!
I remember someone porting Mario 64 movement to Minecraft a few years ago. The original is outdated, but here are a few mods I just found for version 1.20.1. Note that I haven’t tested these yet.
Obviously vanilla Minecraft wasn’t balanced around these movement techniques, but they certainly can’t be any more overpowered than elytra+rockets.
I would rarely choose to fast travel if I had engaging and interesting means of travel like bunny hopping and strafe jumping in Quake, or wall-riding like Lucio in Overwatch. This assumes the world was built to facilitate this kind of movement and there were challenging obsticles, enemies, treasures, secrets, and other points of interest scattered among a variety of paths for the player to choose. Obviously much easier said than done; Super Mario Oddessy and Sonic Frontiers tried to do something like this on a smaller scale (relative to the large open worlds of other games) with varying levels of success.
Exploration was fun in the BotW and TotK Zelda games, but I found myself relying on fast travel by the midpoint of each of those entries because the enemy camps and treasures just weren’t worth the time nor effort. Dashing on horses wasn’t mechanically deep enough and Ultra Handing vehicles was either too inconvient or resulted in “path of least resistance” designs that led me to hoverbike to new locations very cheaply and easily.
Flipping a coin two times and reading the result as binary gang. (Don’t actually do this, coins aren’t as fair)
This is worded better than what I said. The second round isn’t 1/2 because the door you initially picked was 1/100.
I was stubborn about this for so long, and I’m still not entirely sure I understand it, but here is a perspective that made me doubt my belief.
Imagine the Monty Hall Problem, but with 100 doors and only one grand prize. You pick one; it obviously has a 1/100 chance of being a grand prize. Then Monty reveals 98 doors without grand prizes in them such that the only doors left are the one you chose and one that Monty left unopened. Monty obviously arranged for one of those two doors to have the grand prize behind it. The “choice to switch” is really just a second round of the game, but with a 1/2 chance of winning (wrong, your odds change only if you “participate” in round two).
If you stick with your door, you are relying on your initial 1/100 chance of winning. If you switch, you are getting the 1/2 odds of the “second round”.
Apparently with three doors, switching gives you a 2/3 chance of winning, but I don’t understand the math of how to get that answer and I wouldn’t be able to calculate the odds of the 100 door version. I just know intuitivey that switching is better.
deleted by creator
I’ll know the Fediverse is mainstream when I inevitably see this post and comments in a top 10 list or being read by an AI voice and posted to a video sharing site as part of an automated content farm.
Annoying normies with protest until they leave is like the politics inverse of campaigns softening their messages to appeal to suburban mothers.
That’s Captain John Oliver!
r/pics was forced to reopen but they complied maliciously by limiting themselves to pics of John Oliver. If there are any sympathetic mods left, maybe r/piracy could be limited to pictures of pirates? I deleted both of my reddit accounts so I wouldn’t be able to vote if there was a poll.
Yes, especially for applications, and especially for Firefox. The Major version in SemVer increases with any interface change public or private (or it’s supposed to). This is important to communicate to users who rely on any 3rd party plugins, or who need to open files created with prior versions of the software, including configuration profiles.
Using Firefox as an example, I use the Firefox UI Fix. If Firefox changes their browser userchrome/layout, this mod breaks. But it is nice that I can tell at a glance when a new Minor version or Patch version releases that it contains no changes that break this mod. Any breaking changes in these versions are bugs in Firefox.
As for higher number versioning. I’m not advocating that Firefox restarts their Major versioning number back to 0. They could skip Major versions and call the next Major version 200 for all I care. The only thing my comment advocated for was including the date in the patch version number.