> The way our system works is that each bot will emit a BotEvent as it progresses through its lifecycle. One for when the underlying server is ready, one for when the bot is in_waiting_room, and one for when it is joining_call. BotEvents are their own table, but through a trigger they update a status field on the bot, which is indexed as we frequently want to query bots based on where they are in their lifecycle.
This causes a change to the Bot index, so we suddenly need to alter and extend every corresponding index.
....
Why not remove the trigger and put the status field in its own seperate table
> I don't understand the huge upside for Starlink outside of Africa or India, where they have <.1% the money to spend on such things.
Starlink has a Military arm called Starshield. If strategically important to US military and other militaries who are partners of the USA, that will be many millions/billions.
> "SpaceX has told the FCC that the Gen3 network is intended to serve not only consumers and enterprises but also government customers and "billions of AI-powered devices worldwide,"
The Starlink satellites last 5 years and then drop and disintegrate. Don't think a billion AI devices will exist in 5 years! Unless by Ai devices they mean phones.
> "While SpaceX hasn't announced rates for its new Gen3 service, I expect it to be at least $200 a month, and I won't be surprised if it ends up being $300 a month."
Not sure that is affordable for most of the world population.
Speaking from the UK, the state controls the media.
There are rules that a few select channels like BBC have to be prominently placed (I.e. Channel 1-4 reserved for them) which means any rival News service is disadvantaged.
And presently they are passing new laws to force Youtube and similar to change algorithm's to also make certain UK content providers prominent.
UK Media know what they can and cannot talk about- for example Judicial Corruption.
This causes a change to the Bot index, so we suddenly need to alter and extend every corresponding index.
....
Why not remove the trigger and put the status field in its own seperate table