Jesus guys, I get that people have issues with msft but github's policies haven't even changed yet. Just chill for like 30 seconds. That or start tweeting if changes were made so we all know. The "msft touched it quick jump ship" rhetoric is getting a bit irritating.
-
-
This Tweet is unavailable.
-
Replying to @alexis_v_l
The bandwagon effect on this is fucking nuts.
1 reply 0 retweets 3 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
You mean the
@gitlab which until recently was running entirely on Azure, which they did only because they got a sweet free deal from MS? And which caused them significant reliability issues because Azure sucks?1 reply 0 retweets 3 likes -
Dude don't add oil to an already overwhelming trash fire. I know it's hard not to but the last thing I want is a flamewar on top of a bandwagon.
1 reply 0 retweets 2 likes -
Replying to @hedgeberg @gitlab
I'm just amused that they of all people would be spamming about people jumping ship away from MS. Me, I realized self-hosted Gitea is the way for private repos. As for public GitHub repos, I couldn't care less. The data is largely portable. I'll jump ship if and when it goes bad
2 replies 0 retweets 6 likes -
Yeah all the licenses are still valid and it's not like they have the rights or abilities to change those. Just download a local copy for just-in-case purposes I guess.
1 reply 0 retweets 3 likes
They aren't going to lock things down or disable access (and GitHub was already quick to bend over for DMCA reqs so I doubt that part will change). If anything they'll just start introducing stupid policies or messing up the interface or account system. Plenty of time to switch.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.