FINALLY! Hopefully this lets Google launch it’s find network

fair, my apologies, thought you were the original commentator

Alright, this doesn’t support your argument. That is a counter example that SpaceX ISN’T receiving subsidies. Anything else? I do appreciate the discourse though

It seems Starlink A) isn’t getting subsidies and SpaceX is B) providing services in exchange for payment rather than just getting free money.

On top of this, SpaceX is reportedly still profitable. I just don’t understand your argument here. No sources, no actual hard data just conjecture.

The problem is you say this with certainty but have no numbers or evidence to back it up. How do you know the revenue from subscribers can’t cover rocket launches?

can I get a source on the math for this? I haven’t heard that before

deleted by creator

SpaceX is doing just fine

but you don’t pay attention to the actual impacts the companies have. SpaceX gets bashed a lot which is hilarious. There is no argument that SpaceX is bad. Like what, ULA was better? Throwing boosters in the ocean and charging $500 million+ per flight? SpaceX is objectively an amazing achievement that we should all be proud of.

have you tried in the default lemmy ui? it might be a sync bug

lemdro.id doesn’t disable editing so I’m not sure what you mean

fyi, I replied in this thread!

Basically, the lemmy backend service for some reason marked every instance we federated with as inactive, which caused it to stop outbound federation with basically everyone. I have a few working theories on why, but not fully sure yet.

TL;DR lemmy bug, required manual database intervention to fix

This was a stressful start to a vacation!

For a more detailed working theory…

I’ve been doing a lot of infrastructure upgrades lately. Lemdro.id runs on a ton of containerized services that scale horizontally for each part of the stack globally and according to load. It’s pretty cool. But my theory is that since the backend schedules inactive checking for 24 hours from when it starts that it simply was being restarted (upgraded) before it had a chance to check activity until it was too late.

theory:

• scheduled task checks instances every 24 hours

• I updated (restarted it) more than every 24 hours

• it never had a chance to run the check

• ???

• failure

This isn’t really a great design for inactivity checking and I’ll be submitting a pull request to fix it.

test comment #3

Test comment please ignore

this assumption is only correct if EVERYBODY is using as blockers. They aren’t - so it makes sense to cut off the proverbial leeches

sick! this is awesome

Obviously I want RCS. But I’m realistic in what I have right now. And right now what I got was working group chats

not surprising, but super disappointing. Beeper Mini was a dream come true

a text message for verification from Apple confirms ownership