We use them to pay online, of course. But the payment mechanism is different because most of the time they're debit accounts not credit.
Most online places are now aware of Revolut's disposable CC numbers and reject them. They haven't worked for at least a year now. They're basically useless.
I like the way Bunny.net does paid DNS, 20M monthly queries for $1 and $0.1/M after that. With an API included, ofc. Now that's the kind of pricing I can get into as a self-hoster, not $20/mo.
GoDaddy advertises a lot, basically. So whenever a person who's never owned a domain before searches for "get a new domain" they're gonna get GoDaddy, NameCheap and (ironically) Google Domains as the top results. That's pretty much all there is to it.
But you don't have to develop anything. There are plenty of ready-made excellent tools you can just drop-in. The main fallacy is that what Github does is actually useful, or that the pieces it integrates are useful. 90% of Github is subpar for any given purpose. Consider all the possible types of software being developed and all the different release flows and support/issue flows, how could they possibly be shoehorned into a one-size-fits-all? Yet people try their damnest to do exactly that.
To do software development you need (A) issue tracking, (B) a clear release flow, and (C) a deploy mechanism that's easy to use. A is a drop-in tool with lots of alternatives, B is unrestricted since Git is very flexible in this regard, and C is typically included with any cloud infrastructure, unless you're doing on premise in which case there are also drop-in tools.
A, B, C are three distinct, orthogonal topics that can and should be handled separately. There's no logical reason to shape any of them after the other. They have to work together, sure, but the design considerations of one must not affect the others.
It depends a lot on the setup you have, how many people, release flow etc. Issue tracking depends on the kind of software you do and whether you want a programmer-only flow or a full support flow.
Deploy pipelines will usually depend on the infrastructure, cloud solutions usually can integrate with several and there's also common solutions and even FOSS ones, like Terraform vs OpenTofu.
Git frontends are a very mixed bag, generally speaking their main purpose is to hide Git as much as possible and allow programmers to contribute changes upstream without knowing much beyond the nebulous "PR" concept. Basically they're mostly useless other than enabling people to remain dumb. A good Git tutorial and a good history visualization tool (git happens to include one called gitk
out of the box) will do so much more to teach people Git, and there's really no substitute for communication – using annotations to discuss pros and cons for a PR is badly inadequate.
These are ancient holdovers. Nowadays DNS hosting with API is a dime a dozen. You may have to pay for it occasionally but it's not going to be even close to $20/mo.
They're expensive for the US too. The reason so many people can afford iPhones is thanks to carrier subsidies.
It doesn't sound like he's doing anything fancy. Does KMail not have filtering rules?
Again, like OP said, those are typically distinct functionality: issue tracking, source control, deployment etc. GitHub bringing everything into one platform is atypical and obviously done for the goal of centralization. The more stuff you add to a platform the harder it makes it to leave or replicate.
But no, technically speaking you don't need to have all of it in one place. There's no reason for which you must manage everything together.
I don't even understand why people like GitHub so much, its source management sucks. The fact it still doesn't have a decent history visualization to this day is mind-boggling.
Look for ways to do things separately and you will find much better tools. GitHub's "one size fits all" approach is terrible and only holds because people are too lazy to look for any alternative.
Time travel? It never stopped. Agriculture was always rife with legal child labor. Now it's just seeping into other industries.
https://en.m.wikipedia.org/wiki/Child_labor_in_the_United_States#21st_century
What does "old network" and "new network" mean? What are they, LAN setup? Docker setup? Describe them better (netmasks, routing etc.)
Yeah most distros should have the droidcam module available as DKMS module, meaning you don't have to prepare it yourself.