Audiogalaxy dev here. That was my favorite part of the design.
One of my other favorite parts was that prioritized matches based on how similar their domain name was to yours, so a lot of times you would end up grabbing files from someone in the same dorm or city (cable modem IPs had hostnames back then had the city in the name).
Remember what the Luddites actually did? They sabotaged the machines that were disrupting their livelihoods. If AI is as disruptive to large numbers of workers as some people think it will be, keep in mind it's a lot easier to destroy a GPU that's stored on earth than one in space.
Anyone planning expenditures as large as a modern data center thinks about all kinds of risks (earthquakes, climate, power, etc), and so perhaps there is a premium for GPUs that are out of the reach of your median angry unemployed guy.
(yes, this is nuts, but I can easily imagine some fever-dream pitch meeting where Musk is talking about it)
Just curious, what's your background in batteries? From my understanding, sodium based batteries are safer than lithium, but I would defer to anyone with real expertise in the subject.
Yes, 100% agree. We've spent so much time chasing down what makes our build slow. Obviously that is less important now, but hopefully they've laid the foundation for when our code base grows another 10x.
This is amazing. Everyone that picked TS for a big project was effectively betting that someone would do this at some point, so it's incredible to see it finally happen. Thanks to everyone involved!
Where does the uncertainty (1%) come from? For example, is it more from our ability to precisely determine the orbit based on limited observations, or is it because orbits for objects like this just aren't predictable years out, or something else?
The only announcement I want from AWS about databases is that the price for RDS is going down. Not that they have new chip that is more expensive but offers better price/performance, but that my bill is actually going to drop.
I don't trust them enough to use non-portable technology like this until they give me confidence they are committed to lowering prices.
Early on in a community, there often aren't enough data points to cover other possible metrics. With that in mind, starting somewhere is better than not starting at all — measuring engagement is a useful way to begin understanding what's resonating in your community. As you continue building your community, there are many different angles that you should use to evaluate its health.
Measuring engagement then becomes one piece of data that's valuable, but shouldn't be the only piece. When engagement data is combined with qualitative community surveys, enthusiasm from members to contribute to a community, clear and timely responsiveness to community needs, membership growth over time and geographies, depth of member interactions (whether across community channels or within specific channels), what's topically important to members and why, and overall sentiment and change in sentiment over time - that's when community builders can begin to better understand the health of their communities and their impact on their business.
Engagement is an important piece, but just one of the pieces, that helps paint the full picture.
Disclaimer: I’m a co-founder of Common Room [1] and a we’ve invested a lot of energy in solving for this exact problem. You’re welcome to check out the product (it’s free to sign up) and would love to hear of ideas or feedback.
Oh, this is a great writeup. I co-host a podcast on outages, and over and over we see cases where circular dependencies end up making recovery much harder. Also, not using a staged deployment is a recipe for disaster!
We just wrapped up the first season, but I'm going to put this on the list of episodes for the second season: https://downtimeproject.com.
I'm not sure there is quite enough detail in this post to make a whole episode, but if any more details about the bug come out we will definitely cover it.
One of my other favorite parts was that prioritized matches based on how similar their domain name was to yours, so a lot of times you would end up grabbing files from someone in the same dorm or city (cable modem IPs had hostnames back then had the city in the name).