Didn't expel me from university for an insensitive prank I accidentally sent to the administration instead of my friends. I discovered the university's email server was unsecured and thought it would be funny to send fake emergency alerts to my friends from the official university email. I mixed up the "from" and "to" fields though... oops.
Allowing the maintainer to prepend a comment to the top seems more sensible to me to be honest. Would make API use harder potentially, but it would avoid weird abuse like this.
github is meant for collaboration, designing it around adversarial use would be a loss for everyone. Adding a function to report absusive edits rather than an entire post would be a better choice imo.
reporting abusive edits requires moderation/arbitration. the rules can instead be changed to sidestep the issue, while maintaining the value of the feature.
Report to whom? Github, who allows the behavior and therefore doesn’t see anything wrong with it, or the repo admins who have proven they they couldn’t give a rat’s ass about the very thing you’re reporting? The well is already poisoned, there is no reason to think that they’d suddenly change their stance and cooperate.
In this case at least, github (most probably) banned this account, presumably after reports. There are also other stories for github banning accounts for pr trolling kind of behaviours. So not sure if everything is perfect, but at least there are cases such things work.
I've been messing with sandboxing using "bwrap" for random itch.io games I download to play and it isn't trivial to get it working with least privileges. I have so far been unable to get "Microlandia" to run, but other Unity games are running just fine under "bwrap". I am excited to see more Landlock tools emerge that make this task easier.
it seems to work fairly well? But I just started playing with bwrap this weekend. I do wish bwrap could be told "put the program in this pre-prepared network namespace" because accessing unsecured local dev servers could also be an issue.
I had this idea of having toolbox+custom user for each project - that way it would be "simple" to have isolated environments, but it does lead to a lot of bloat. And I do think it is a naive solution.
I think a combination of custom users + a whole bunch of sandboxing is exactly what you'd get out of systemd-nspawn if you're willing to write the config: https://wiki.archlinux.org/title/Systemd-nspawn
bwrap seems a lot easier but if you want more control (or, for instance, want to run a Ubuntu basis because that's what a lot of games are compiled against), systemd-nspawn can be quite powerful.
You can flag, but a lone flag is worthless. Not sure how many it takes to nuke a story or comment.
For myself, I only downvote/flag stuff that I consider harmful to the community.
That does not include stories or comments with which I disagree. In fact, I frequently upvote comments posted, that attack my own positions, if they do so in a reasonable manner. Groupthink sucks, and I frequently change my mind, based on orthogonal feedback.
Oh well. Uninstalled. This was my first experience doing software development guided by AI. Doesn't seem like a tool that will serve me well in the long run.
The approach I like the most is to first design a CLI that has the functionality you need. Then move that functionality to a lib and have the CLI now be a frontend for the lib. Then make a GUI frontend too.
Allows for a GUI for tasks that need that better context or hand holding. But then the CLI is there when there is a workflow the GUI doesn't support comes up. Bonus of scripting being possible with the CLI too.
Challenges this approach has is that you have to have a test suite that exercises both workflows or due diligence to make sure they both work as development continues.
Also not all programs can be done acceptably with a CLI. Real time 3d games are an easy example of a GUI only task.
reply