I just use GitHub for the basics: repo hosting, reviews and actions - what are the "social media psyop manipulations"? I've never really paid much attention to the other features.
All the metrics based around how many commits you have made, how many stars your repo has, etc. Why is that info gamified? Its a dopamine addiction channel.
You outlined what it (and all git hosting other services) are for: repository hosting, optionally issue tracker, mandatorily pull requests (for syncing with master or other branches), Actions for automated steps on merge to a tracked branch.
But now the users who only use core functions (re: repo hosting, reviews and actions) suffer when the service is down due to overreach with feature implementation.
It's good you can isolate yourself from it. But there's plenty of cases.
Open source maintainers being harassed or being demanded work through Github's issues. Or being feed AI slop to review endlessly. Or recruiters filtering resumes via Github activity graphs or repository stars.
And obviously the side shady market of all of the above (e.g. buying/selling popularity).
Like the parent comment, I can't wait for social media to be completely obliterated from code repositories.
> Open source maintainers being harassed or being demanded work through Github's issues
This isn't "psyops". Sure, it's a bad side of social interactions, but when you interact with other people, there's always some of this - in person as well as online.
The lead-off argument here seems more like "interacting with society can be bad".
I have no argument that selling popularity is bad and filtering by stars is stupid, but I don't blame Github for any of that.
You could equally well assign the success of certain coders to YouTube because they came to attention by showing off their work in livestreams. Which I do not. They found a way to advertise their own success, but it's theirs.
> The lead-off argument here seems more like "interacting with society can be bad".
The argument is that there's no need for that much social interaction to produce quality code, quite the contrary, the more social interaction, the more focus is lost.
I know it's an unpopular opinion, but there's a reason why the Linux Kernel communication is still done through acerbic email threads.
None of this is specific to GitHub. The exact same problems will sometimes happen any time users and developers communicate, which is a basic requirement of developing useful software. I doubt GitHub issues are worse than mailing lists or any other mechanism.
They almost have to be - which users will be able to get to your issues page and which will be able to find a mailing list? You'll have a much more selective audience in the latter
Demanding work isn't really an issue. Anyone can do that, and also reject the work. Dishonest actors on the other hand would take money for someone else's work.
NPCs are Non-Player-Characters in video games, i.e. "extras". Their programming is usually kept simple, so they're kind of famous for robotically repeating the same lines or doing the same actions.
I think here it might mean getting attached to the rules for the rules' sake and forgetting the deeper reason why the rules are there in the first place - like waiting on a red light on a deserted street.
A log sink should be fast, light on resources and reliable. I'm not an AI skeptic but I can't imagine using AI to classify log data like this is going to meet those requirements.
Your readme states that caching helps here, but it doesn't describe how caching works. How effective is this for highly variable log data?
