[-] patrick@lemmy.bestiver.se 4 points 3 days ago

I fully agree that nixos moving off GitHub is a nonstarter for technical reasons. The nixpkgs repo is enormous and has caused loads of infrastructure problems at GitHub over the years.

But the NixOS foundation currently has over 300K Euros in their open collective account. They get free sponsorship from GitHub for the repo and free sponsorships covering the very expensive build and caching services too.

https://opencollective.com/nixos

[-] patrick@lemmy.bestiver.se 27 points 5 months ago

I too fixed performance problems in that repo a few years back and did a write up on it - https://jackson.dev/post/rust-coreutils-dd/

I'm glad this project is getting some more attention, maybe even getting funding from Ubuntu since they're using it? Last time I touched it most of the code was still pretty clearly written by Rust beginners and non-systems programmers so it likely had/has many such issues to uncover. Ubuntu putting it into their distro should hopefully get more experienced (and actually paid!) devs taking a closer look.

64
[-] patrick@lemmy.bestiver.se 21 points 8 months ago

Because that’s where all contributors are.

Personally I’ve been moving towards dual hosting everything on GitHub + Codeberg. It’s pretty easy to setup CI to keep them in sync, and I’m open to dealing with the annoyances of managing multiple issue trackers.

[-] patrick@lemmy.bestiver.se 21 points 1 year ago

This was a potential explanation as to why Bezos did that https://lemmy.haley.io/post/1058450

[-] patrick@lemmy.bestiver.se 12 points 1 year ago

Are you willing to bet the stability of an entire language's dependency ecosystem on that? Just so that we can write "crates.io" instead of "crates.rust-lang.org"?

That's really the question. I do agree that there's almost no chance it goes away as too many places and too much money depends on it.

[-] patrick@lemmy.bestiver.se 9 points 1 year ago

I doubt they will too, but it's still dumb that an entire package ecosystem now has to hope that ICANN will make another exception and special case .io

ICANN tried to phase out .su, the only reason they didn't was because Russia was big enough to tell them no.

[-] patrick@lemmy.bestiver.se 18 points 1 year ago

Forgot to mention .sh, which is also a ccTLD for a tiny island nation, and also shouldn't be used for hosting anything that is difficult to move.

https://en.wikipedia.org/wiki/.sh

50

It's possible that the .io cctld is going to go away [0]. Does crates.io have a backup plan at all? Does anyone know what problems it would end up causing?

I imagine the package registry having to move domains is going to cause a ton of problems.

Frankly, it's concerning to me that so much of the Rust ecosystem has chosen to standardize on shaky ccTLDs. The Indian Ocean Territory (.io) is a small island territory whose only inhabitants are a single military base, it is crazy to use that domain for something important. Serbia (.rs) is more stable, but they could still cut off access for non-Serbians if they wanted to.

[0] - https://en.wikipedia.org/wiki/.io#Phasing_Out

[-] patrick@lemmy.bestiver.se 12 points 1 year ago

On the feature side, according to Mastodons recent 4.3 release post development is only 4 full time employees and a budget of under $500k annually. That is basically nothing in the realm of social media companies.

Improving Mastodons features requires money and resources, but Mastodons users are unwilling to pay for instances and unwillingly to fund development. Hell, the .world folks host a bunch of instances for collectively hundreds of thousands of users and they take in about $1k a month in donations. I’m surprised that even covers hosting costs.

So…it’s no wonder that it isn’t going to be as polished as other social media in ways that would reduce the attrition.

[-] patrick@lemmy.bestiver.se 18 points 1 year ago* (last edited 1 year ago)

It’s definitely instance dependent. I run the servers for my instance at the closest Hetzner data center to myself (west coast USA) for latency reduction and over-size/engineer it for better perf.

My instance is open for registration too, if anybody reading here would find that useful.

[-] patrick@lemmy.bestiver.se 11 points 1 year ago

That’s somewhat similar to the plot of the movie Plan 75.

“In a dystopian alternate reality, the Japanese government creates a program called "Plan 75" that offers free euthanasia services to all Japanese citizens 75 and older in order to deal with its rapidly aging population.”

[-] patrick@lemmy.bestiver.se 11 points 1 year ago

You realize Nikocado has over 4 million subscribers, plus another million on his second channel? It’s not like there’s just a small handful of people who engage with this person.

[-] patrick@lemmy.bestiver.se 18 points 1 year ago

Looking at just the hosting costs is actually a really bad indicator of total costs. The unpaid volunteer time just to run/manage the instance are likely going to be significantly more than the hosting costs if they were compensated even at minimum wage.

Each of the stacks for XXXiver.se and Bestiver.se (Mastodon + Lemmy + Static Site (+ Linkstack/Wiki for XXXiver.se premium)) are shoved into a Hetzner server at ~$13/month, and backed by R2 Object storage.

My current total hosting costs are ~$30/month to host 2xMastodon, 2xLemmy, 2xStatic Site, 1xLinkstack and 1xWiki. This is basically the minimum cost for me to host all of that on their own infra. I have approximately 0 users other than myself yet, so there's not really a useful cost/user and I can't really provide info on scaling.

Unlike most others here I'm seeing if I can make hosting into more of a job by selling the full suite of services to communities (e.g. get your own Mastodon + Lemmy + others) or by up-selling to premium accounts. I highly doubt that it will actually make any useful amount of money but I'm curious enough to try.

view more: next ›

patrick

joined 1 year ago
MODERATOR OF