Earlier quoted context omitted.
I see, I assumed by ftp you also meant sftp.
Depending on your hardware (SBC), FTP can also be several times faster than SFTP for transferring files over a LAN. Though I'll admit to having used other protocols like torrents for large files that had bad transfers or other issues (low-quality connection issues causing dropped connections, etc).
Moving from GitHub to Codeberg, for lazy people
361–370 of 385 posts
Re: Moving from GitHub to Codeberg, for lazy people
#362Earlier quoted context omitted.
That FAQ snippet is insane to me. Maybe it's a cultural thing but I'd never do business with a company that has implicit threats in their ToS based on something so completely arbitrary.
The worst part is really the unclear procedure. If they set out terms that say they'll give me 4 weeks to migrate projects they don't like off the platform, with n email reminders in between, then that's not ideal but fine. As it is, I'd be worried I'll wake up to data loss if they get 'unhappy'. I have the same problem with sourcehut, actually, with their content policy.
> you may receive a polite email from GitHub Support suggesting strategies[… such as, and including] moving to a different hosting service that might better fit your needs
GitHub Pages has never been a free-for-all. The acceptable use policy makes it clear:
> the primary focus of the Content posted in or through your Account to the Service should not be advertising or promotional[…] You may include static images, links, and promotional text in the README documents or project description sections associated with your Account, but they must be related to the project you are hosting on GitHub
Re: Moving from GitHub to Codeberg, for lazy people
#363Earlier quoted context omitted.
There isn't much advantage that can be taken from O/S users and perms anyway, at least as far as git is concerned. When using a shared-filesystem repository over SSH (or NFS etc.), the actually usable access levels are: full, including the abilities to rewrite history, forge commits from other users, and corrupt/erase the repo; read-only; and none.
Git was build to be decentralized with everyone having its own copy. If it's an organization someone trusted will hold the key to the canonical version. If you need to discuss and review patches, you use a communication medium (email, forums, IRC, shared folder,...)
Re: Moving from GitHub to Codeberg, for lazy people
#364Earlier quoted context omitted.
There isn't much advantage that can be taken from O/S users and perms anyway, at least as far as git is concerned. When using a shared-filesystem repository over SSH (or NFS etc.), the actually usable access levels are: full, including the abilities to rewrite history, forge commits from other users, and corrupt/erase the repo; read-only; and none.
Git was build to be decentralized with everyone having its own copy. If it's an organization someone trusted will hold the key to the canonical version. If you need to discuss and review patches, you use a communication medium (email, forums, IRC, shared folder,...)
Re: Moving from GitHub to Codeberg, for lazy people
#365Earlier quoted context omitted.
Maybe decades ago. My current one doesn't.
I just checked, I’m not using the feature but my current ISP still offers it: https://assistance.free.fr/articles/631 (10 GB FTP storage tied to the ISP-specific e-mail address).
Re: Moving from GitHub to Codeberg, for lazy people
#366Earlier quoted context omitted.
Ok, that solves like 20% of the problem. How (and where) are you provisioning these VMs? How are you managing what versions of what are installed on them, and is that process reproducible? None of this is hard, exactly, but you do have to put in the legwork of doing it, and it's mostly only the big players who've done so.
A lot of VM managers allows to clone from a disk. And some even allows for an overlay layer on top of a read-only disk. Creating a build machine is not rocket science.
Re: Moving from GitHub to Codeberg, for lazy people
#367Earlier quoted context omitted.
Companies like Microsoft should not be given "incentives to exist" anywhere (at least as they exist currently). They are corrosive to the public good.
Are you sure? Enumerate all the competition and associated technilogy this has enabled for decades: tooling, software, etc. I am not sure how someone should be entitled to prevent others from enjoying thr benefits of better technology. If you do not like it, just skip it, as I do.
Re: Moving from GitHub to Codeberg, for lazy people
#368Earlier quoted context omitted.
This doesn't work in when a market is run by oligopolies, you have to regulate to restore some sort of normalcy and competition.
Oligopolies are the result of overregulation. Just fix the right things, not the wrong ones.
Re: Moving from GitHub to Codeberg, for lazy people
#369Earlier quoted context omitted.
Are you sure? Enumerate all the competition and associated technilogy this has enabled for decades: tooling, software, etc. I am not sure how someone should be entitled to prevent others from enjoying thr benefits of better technology. If you do not like it, just skip it, as I do.
Are you seriously trying to pitch the flaming garbage heap that is Microsoft Windows as "better technology"? Microsoft is a predator, they offer licenses to schools at a knock-down rate in order to nurture a dependency on their product. The volume of cash that has been extracted from the general populace in this way is obscene. To top it off they have gone out of their way to sabotage free and open competitors, limit…
Because you will scare all of them.
Re: Moving from GitHub to Codeberg, for lazy people
#370Earlier quoted context omitted.
I think both of you are misunderstanding what I proposed. You just need a single VM with an ssh server. Literally no web service needed, if all you want to do is host some code remotely.
I didn't misunderstand. Sshd is a web service. Most folks don't already know how and don't want to set up a machine that is always on, that will restart on power loss, that will have a static IP or dynDNS, with a domain name and proper routing and open ports and certs and enough bandwidth and that's before you even worry about actual security and not just what is needed to work.... It's actually a big annoyance if yo…