Post AbgWCzAXWDGuDfIfzs by kkarhan@mstdn.social
(DIR) More posts by kkarhan@mstdn.social
(DIR) Post #AbgPBvki2Kj1eclgRc by rysiek@mstdn.social
2023-11-08T23:32:25Z
0 likes, 0 repeats
🤡 > Just as GitHub was founded on Git, today we are re-founded on Copilot. 🤖 See how GitHub’s AI-powered platform vision evolved into a new reality for the world’s developers, and find out everything we announced at this year’s #GitHubUniverse.https://nitter.net/github/status/1722309261680607674?s=20For years I've been saying that using Microsoft GitHub to host #FLOSS code is dangerous and would backfire. :blobcatcoffee: "But it's so convenient!" 🤣#Copilot #CopilotHub #Microsoft #GitHub
(DIR) Post #AbgPBwWDBiis1wzcUC by PiTau@mstdn.social
2023-11-08T23:59:21Z
0 likes, 0 repeats
@rysiek I remember when I told few of my friends that I don't trust GitHub under Microsoft. They laughed it off and asked what would happen? I told them two things:1. Microsoft does not love open source. Microsoft loves outsourcing via permissive licensing.2. Microsoft will fuck you over once the opportunity manifests.Now let's hope legal actions will render this tech incomercializable.
(DIR) Post #AbgPBxarBw25MeAqMi by kkarhan@mstdn.social
2023-11-09T00:15:12Z
0 likes, 0 repeats
@PiTau @rysiek Sadly I've yet to see a better option that does scale and isn't maintained by Stallmanists...I'd consider migrating away from #GitHub if it provides actual benefits and not just being a pain in the ass to do and basically shift said repos to be slaves.In terms of #GithubCopilot / #Copilot, @senficon already said everything that needs to be said:https://felixreda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/
(DIR) Post #AbgPByVvljgcDesQKG by rysiek@mstdn.social
2023-11-09T00:23:59Z
1 likes, 0 repeats
@kkarhan @PiTau yeah those "Stallmanists" are the *real* problem, right? Good to have priorities straight! 🙄
(DIR) Post #AbgPBzXjwUjBPYjNmi by kkarhan@mstdn.social
2023-11-09T01:04:38Z
0 likes, 0 repeats
@PiTau @rysiek @senficon My personal TLDR:There are very finite ways to do a function to perform X in any languague that isn't purposefully obfuscated and unreadable code.Just like all wheels are necessarily point-symmetrical rotational ellipsoids, certain things will inevitably be the same and not changeable unless one specifically works around the quirks of doing it different for the sake of difference...https://www.youtube.com/watch?v=PX3A7GLtFqM
(DIR) Post #AbgSHBSHNhnbfLLP1M by shironeko@fedi.tesaguri.club
2023-11-11T03:05:10.698820Z
0 likes, 0 repeats
@kkarhan @PiTau @rysiek @senficon so far sr.ht seems to be the best of the bunch
(DIR) Post #AbgWCzAXWDGuDfIfzs by kkarhan@mstdn.social
2023-11-11T03:08:26Z
1 likes, 0 repeats
@shironeko @PiTau @rysiek @senficon my core problem is that some of my projects may face #DDoS attacks because I pissed off KiwiFarms fans...https://github.com/greyhat-academy/lists.d
(DIR) Post #AjhCav5siTCD4AX2uG by kkarhan@mstdn.social
2023-11-09T01:55:37Z
0 likes, 0 repeats
@rysiek @PiTau They are a problem because people like RMS are why shit's stagnating and regressing!He's a sexist POS and all he does is saying "why [insert anything] is bad" on his 1999 Homepage yet doesn't even bother to point to better alternatives (okay, paywalling toilets is just evil, just don't but that's not the point here)...https://www.youtube.com/watch?v=R2SKenHRhMg
(DIR) Post #AjhCaw5uzoosAZYabQ by lispi314@udongein.xyz
2023-11-09T03:47:51.433755Z
2 likes, 0 repeats
@kkarhan @PiTau @rysiek He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.Also, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a lot of unix-brained regression that needs to be addressed before blaming any other party.(And Microsoft dropped the last hope for common & good sense to prevail in their ecosystem back in 2015 so that's the end of the line for them too.)We're still writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.The entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.The realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. I2P is 20 years old. And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a lot of countries.And right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general completely ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic Asynchronous Communication is a basic requirement and paradigm to build around, because infrastructure capable of lending itself to low-latency communication cannot be meaningfully assumed anywhere.(By the way, neither Fidonet nor Usenet made such assumptions about infrastructure. We've regressed a lot.)We've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.So yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.
(DIR) Post #AjhCaxSHw8J8OF1y6q by kkarhan@mstdn.social
2023-11-09T02:00:01Z
0 likes, 0 repeats
@rysiek @PiTau A good example are some projects like this one maintained by me:https://github.com/greyhat-academy/lists.dShure I could spin up a #GitLab but then try to find some Hoster that is willing to deal with #KiwiFarms apologists #DDoS'ing it offline or harrassing staff of said hoster.I know #Microsoft - like #AllGafamsAreEvil and they are a #PRISM collaborator, but I've yet to see a better option that doesn't cost me €€€€€, cuz my projects have literally ZERO funding.
(DIR) Post #AjhCazycYtMKD6Aome by kkarhan@mstdn.social
2023-11-09T02:02:06Z
0 likes, 0 repeats
@rysiek @PiTau The domains I use (i.e. https://os1337.com ) are fully on me and I do bear the costs of those - just like my time - and I could migrate then with a few clicks within minutes...At worst, I can migrate the stuff, but so far #GitHub's staff have been just nice to me and not given me a reason to yeet...Now requiring a #Microsoft Account would be a "no-go" and that's the reason I don't have #Minecraft...
(DIR) Post #AjhCb24ilBQWib2iZM by kkarhan@mstdn.social
2023-11-09T02:04:39Z
0 likes, 0 repeats
@rysiek @PiTau So yeah, I do have the right priorities...Do you?https://mstdn.social/@rysiek/111377739921124892
(DIR) Post #AkYWrDb8ys8oBDKLUO by fluffykittycat@furry.engineer
2023-12-09T06:03:13Z
1 likes, 0 repeats
@lispi314@udongein.xyz @kkarhan@mstdn.social @PiTau @rysiek I'm glad to see I'm not the only one who's been thinking most of these ideas. I'm cursed with enough foresight to see one or two problems ahead with bad architectures
(DIR) Post #AkYWtbtLd2dq6WyyPY by lispi314@udongein.xyz
2023-11-09T03:25:30.417316Z
1 likes, 0 repeats
@kkarhan @senficon @rysiek @PiTau If used properly, none of it *needs* to scale because git is meant to be distributed. Simply put a few different "well-known" mirrors in indexes.As for authentication that it is legitimate, we *finally* (after far too long) have the ability to use sha256 with git, so signatures are safe.And if you either use git-bug or public-inbox, then you can also have distributed issue management too.What concerns me a lot more is how many of the current options expect you to keep services backed by C libraries exposed to the internet.Maliciously-crafted messages causing security problems in git implementations has been a thing in the past and most likely will be in the future too.
(DIR) Post #AkYWuRDIobuHHBi85w by cstanhope@social.coop
2023-11-09T00:42:46Z
0 likes, 0 repeats
@rysiek I was reading the blog post and this stuck out at me:"Every day, the world’s developers balance an unsustainable demand to both modernize the legacy code of yesterday and build our digital tomorrow."Unsustainable... That word choice is fitting in more than just one way in this context. :/
(DIR) Post #AkYWuRkGq2HIvR8STw by rysiek@mstdn.social
2023-11-09T00:45:58Z
0 likes, 0 repeats
@cstanhope totally. Also, churning out more code faster will not fix the issue with legacy code.
(DIR) Post #AkYWuSIemBmee5Dv4y by lispi314@udongein.xyz
2023-11-09T03:29:12.267328Z
1 likes, 0 repeats
@rysiek @cstanhope At least, insofar as you want to keep compatibility with the legacy code.If you're willing to hard break compatibility? It can, by replacing the whole codebase.