I would much rather pay for a year at a time, then about a month before the next payment is due, I get an e-mail reminder that payment is due by X date at Y time in Z timezone.
But if you’re in a place where that payment plan works for you, both of them were great places to host things over the years. I liked Linode a little more than I liked Digital Ocean, but your experience could be the opposite.
(1) #Twitter has millions of users. There is no #ActivityPub nor #OStatus implementation in which an instance hosted on a $5/mo #DigitalOcean / #Linode / #Vultr #VPS could handle the volume of a seamless connection with #Twitter. If they adopted AP OStatus, #Diaspora, or any other current open federation protocol, instances that didn't use firewall blocking would topple once the two userbases had sufficient interconnections (within a few hours or a few days after they started federating).
(2) Twitter's business model is to push ads disguised as tweets. If their users could escape those and still interact with all the same contacts, they would. I'm certain that Twitter's management know this. They also turn all links into tracking links, and sell access to media (images, video, audio) uploads of important news events to news organizations.
(3) Most Fediverse instances are financed out of the admin's pocket. Some have financial contributors, but nothing like Twitter's revenue. As the largest and best-financed instance, they would immediately have to start implementing modifications to make AP or other existing federation protocols useful to them, and those modifications would (as Mastodon's currently do) become unofficially mandatory in order to be compatible.
(4) This isn't the first time that Twitter has considered federation, though this may be the first time they openly discussed it. Back when Identica was still a happening place (during Twitter's fail-whale days), Twitter considered federating. They didn't do it then, and I honestly do not believe they will do it now.
(5) I'd say that Twitter's #BlueSky initiative is more meant to try to get bidirectional connections across #Facebook's moat and wall than it is to surround Twitter with a cloud of #Fediverse instances.
@1iceloops123 I’ve never had any site taken down over content, but if you anticipate posting things that would be subject to take-downs, you’ll have to ask someone else where to host it.
From what I’ve experienced, the $5-$10/month tier of #vultr or #digitalocean or #linode should be fine for a small instance. But again, that does not account for content-related take-downs.
@amic Cool. :) What backend stuff do you think you'll use? I'm likely going to use #Python and #Django, start out by running that at #PythonAnywhere, and then annoy Walt with questions about using #Linode. :) @lnxw48a1
Somehow, I am truly almost done migrating things from this #Linode into #Ansible and onto new hosts. Gitea and Drone CI really gave this years-long effort a kick in the pants these past few weeks.
Somehow, I am truly almost done migrating things from this #Linode info #Ansible and onto new hosts. Gitea and Drone CI really gave this years-long effort a kick in the pants these past few weeks.
@moonman If you're on #Digital_Ocean, my experience is that something about their droplets' default configuration hindered both #MySQL / #MariaDB and #PostgeSQL performance. A smaller resource #VPS on #Linode runs them much better than DO.
.
I may try one on #Vultr soon.
@tregeagle I had it penciled in for this week, as I've been consolidating my last two #Linode servers into one. Been scaling new sections of the learning curve, as #Apache config has changed slightly and #drush now depends on #Composer. Neeeearly ready to look into it…