> But I also understand that any large platform must use automation to handle spam.
They do not. Certainly not the kind of automation that shadowbans accounts of long-term users without any kind of manual review. Stop making excuses for this kind of shit.
I’ve been saying for years, the only reason these kinds of online businesses are viable is because they are foregoing all the “human” services that they should be providing, and they can get away with it just by hiding everything behind machines and automation.
Why hire an army of humans to investigate and deal with spam when you can just auto-ban anyone your shitty algorithm says is suspect? And the only way they can get any recourse is to make a shitstorm on social media.
This is concerning. The possibility that a company’s livelihood could disappear, only rebuildable by reassembling the bits found on developers’ local Git clones. And then having to spin up new Git infra, rebuild all the pipelines, etc..
Pipelines should be simple, if you have all the logic in scripts/whatever as part of the repo.
But rebuilding on another host is not the hard part. Rebuilding the community (and issue tracking etc.) is much harder. Especially since github pretty much dominates that aspect.
After now getting time to read the thread. Don't take my sentences as any negativity towards the dev in the thread, it is meant more generally.
Please keep backups of your data, your backup does not need to be full git history etc... Even just a zip export of the current state every now and then although just a full dump of the repo is small enough for most repos.
For anyone reading this and wants a web3 100% uptime and uncesorable/un-deleteable data please hit me up (not free but not a scam... also less than 3 dollars a month for 100 gygabYtes of storage...)...
> Nope. It's outrageous but 20 days after creating the ticket, support has yet to answer it. I'll definitely move ship next week.
Doesn't surprise me one bit. GitHub's support was pretty much non-existent even long before Microsoft's acquisition. My memory may be a bit foggy, but about a decade ago the only way I was able to resolve my issue was by literally interviewing someone from GitHub for an article and mentioning my issue to the person I was interviewing.
Readit News
It's sort of sad that small developers cannot get any help unless they go viral on social media.
But I also understand that any large platform must use automation to handle spam.
They do not. Certainly not the kind of automation that shadowbans accounts of long-term users without any kind of manual review. Stop making excuses for this kind of shit.
Why hire an army of humans to investigate and deal with spam when you can just auto-ban anyone your shitty algorithm says is suspect? And the only way they can get any recourse is to make a shitstorm on social media.
Welcome to the future.
But rebuilding on another host is not the hard part. Rebuilding the community (and issue tracking etc.) is much harder. Especially since github pretty much dominates that aspect.
Deleted Comment
Please keep backups of all your data, source code included.
If your company fails because {{online service}} lost all your data it is your fault not theirs.
Please keep backups of your data, your backup does not need to be full git history etc... Even just a zip export of the current state every now and then although just a full dump of the repo is small enough for most repos.
No. It is your fault because it is expected and preventable but that shouldn't let the online service provider get off the hook. It's their fault too.
> Nope. It's outrageous but 20 days after creating the ticket, support has yet to answer it. I'll definitely move ship next week.
Doesn't surprise me one bit. GitHub's support was pretty much non-existent even long before Microsoft's acquisition. My memory may be a bit foggy, but about a decade ago the only way I was able to resolve my issue was by literally interviewing someone from GitHub for an article and mentioning my issue to the person I was interviewing.