I have several for work that will likely never work in Linux.
So those have a nice little VM they sit on, which has been stripped bare of the nonsense. Remote desktop access enabled, and I can do what I need whenever.
Like anything else, it's good to know how to do it in many different ways, it may help you down the line.
In production in an oddball environment, I have a python script to ftp transfer to a black box with only ftp exposed as an option.
Another system rebuilds nightly only if code changes, publishing to a QC location. QC gives it a quick review (we are talking website here, QC is "text looks good and nothing looks weird"), clicks a button to approve, and it gets published the following night.
I've had hardware (again, black box system) where I was able to leverage git because it was the only command exposed. Aka, the command they forgot to lock down and are using to update their device. Their intent was to sneakernet a thumb drive over to it for updates, I believe in sneaker longevity and wanted to work around that.
So you should know how to navigate your way around in FTP, it's a good thing! But I'd also recommend learning about all the other ways as well, it can help in the future.
(This comment brought to you by "I now feel older for having written it", and "I swear I'm only in my fourties,")
Creating a bug report or feature request can be done without having to create an account, and the backend tools (including blocking instances) are being completed first.
It's not like it's forced either. You can just run it local and have no federation (once the feature is out of course, right now you wouldn't have it regardless).
For one thing, more FOSS focused. It's lighter/faster for me than a self hosted gitlab, there is nothing hidden behind a paywall, they are working on some nice activitypub integration, actions are really handy (yes it's a bit of yaml soup), codeberg is using and supporting it, a better focus on security and stability than gitea (where it forked from), the ux is clean, and that's about what I can think of off the top of my head.
If you do find it let me know, I'd love to see it! I really do have about 20 hours of training in networking I give to folks, and since it's literally 20 hours of information, I like to put in fun stuff.
Like a picture of a facemask I added during COVID with "stay at 127.0.0.1, don't 255.255.255.255". Super cheesy but at least it's a mental distraction from information overload haha
I'm on a plan that predates the plans being effected by the price increase.
My price has been the same for years. That said, the plan I'm on was also because of an issue way, way, way back (like a decade ago), and actually being responded to by someone in the c suite after making a comment on the ordeal, who then handed me off to exec customer service to get my issue addressed.
I doubt anyone is getting that sort of response and result today, but I personally have no reason to change providers - Verizon and AT&T would be just as bad, if not worse. Verizon even tried to charge me for devices I had paid in full (and I was out of contract timing) when I switched to T-Mobile.