It's perhaps poorly phrased, no it will only affect that specific user.
Hiding communities outside our predefined rules (politics, porn and bot spam) isn't something we take lightly, and we are only hiding them now after several months of reoccurring reports that break our instance rules (3.4).
We will do our best to be transparent about when and why we hide a new communities, and be aware that subscribing to a hidden community will unhide it for your feed.
If you do have concerns and suggestions on how to alleviate those, please know that we are happy receive feedback.
Looking at your instance handle, I hope/assume that your comment is supposed to be in lighthearted jest. However that would only be an assumption on my part and in general it's not ok to say someone's job/work tool is for [remarks directed at sex, gender, ethnicity, orientation, disabilities, etc...] per CoC 3.5.
Please take into consideration that members on this instance may be of different backgrounds than what you're used to and interpets what you say differently. Further breaches of our Code of Conduct may lead to temporary or permament ban.
@Ategon@programming.dev might give a more precise date, but unless there is an important security update, we prefer to wait 1-2 weeks to see how the update goes.
You asked how it can be abused. This is one way it can be abused.
If it's computer, it can be hacked. Doesn't have to be the car company itself that does the spying, though considering the track record of American companies, it wouldn't surprise me. It could be you local police department, your distrustful partner, etc...
All it took for me to switch to GitLab was a larger free lfs quota which I wanted for a project. The superior webpage UI made me migrate every old project to it too.
This honestly feels like it's presented by someone with Stockholm syndrome. What major advantage is there over having multiple, more manageable repos? From the blog, it sounds like it's just extra challenges and more complicated on-boarding.
Mate, you're not John Carmack. It would be a ridiculous assumption to think their developers didn't take a serious look into optimisation before deciding to ignore the xbox ecosystem for initial launch.
A round number is a number that is the product of a considerable number of comparatively small factors (Hardy 1999, p. 48). Round numbers are very rare. As Hardy (1999, p. 48) notes, "Half the numbers are divisible by 2, one-third by 3, one-sixth by both 2 and 3, and so on. Surely, then we may expect most numbers to have a large number of factors. But the facts seem to show the opposite."
A positive integer n is sometimes said to be round (or "square root-smooth") if it has no prime factors greater than sqrt(n). The first few such numbers are 1, 4, 8, 9, 12, 16, 18, 24, 25, 27, 30, 32, ... (OEIS A048098). Using this definition, an asymptotic formula for the number of round integers less than or equal to a positive real number x is given by N(x)∼(1-ln2)x+O(x/lnx)
(Hildebrand).
https://mathworld.wolfram.com/RoundNumber.html
Alternatively, a number rounded off to a given precision in whatever numeral system you are using. E.g. ten in decimal may be round if you are dealing with small numbers in the decimal system, but it wouldn't be particularly round if you were dealing with large numbers or hexadecimal.
I don't see any compelling arguments to migrate away from GitHun honestly. MS seems to managing the service quite well.
How exactly would a federated forge guarantee the safety of your repo? With GitHub/MS you can be relatively confident that your private repos won't be leaked or that your repos won't dissappear due to server/backup issues.
Its massive user base is also conductive in getting other people to contribute to your project.
And if the safety of your repo and/or community size doesn't matter, why bother all that much where it's hosted, might as well run git locally.
And I'm saying all this as someone who migrated a few years back to GitLab due to it having a better offering for my specific needs. I personally also think their website is far superior to GitHub's messy design, but that's certainly not a compelling reason for someone to migrate either.
For the last ~2 weeks the infrastructure team have been actively investigating performance with our server and actions are currently being taken. You should expect us to post an announcement with more detailed information soon™.