Hey! Maybe mfreed could answer this but how does this affect users of Timescale as part of Azure's Managed Posgres service, is this something that will still continue to be available?
Azure Postgres offers the Apache-2 Edition of TimescaleDB, not the Community Edition (which the TSL applies to). Same with DigitalOcean, Rackspace, Scaleways, Alibaba, etc.
So they can continue to offer the Apache-2 Edition, but could not before, and still can't, offer the Community Edition.
Community is where a lot of our more advanced features lie: multi-node, columnar compression, continuous and real-time aggregates, automation, advanced analytics, etc.
fwiw, I've spent 10 minutes scouring the timescale.com but I can't find any information about the difference between the Apache-2 Edition or the Community edition. Links from your GitHub readme suggest that such information used to be there, but now it's all "cloud" vs "software" - if I choose "software", which of the two editions do I get?
I assume this is still a WIP since the recent licensing / business model changes likely also warranted website changes, hence my feedback.
Congrats on the move btw, and fantastic that Timescale Cloud is working so well as a business model. Are you considering adding other clouds? I ask for selfish reasons as we're currently on Digital Ocean and quite happily so. If Timescale Cloud would exist for DO we'd likely become a customer.
In fact, if your business model succeeds and gets adopted by other open source vendors, supporting a wide range of clouds and hosting providers might very well help directly undermine the current effective oligopoly that is AWS/GCP/Azure! That'd be just splendid. Sorry for rambling a bit :-)
The "Software" column of product page [0], which I assume you are referring to, corresponds to our Community Edition, as least from a feature-set edition.
But thanks for the feedback. Always a balance between making things easily understandable and too much "in the weeds." We used to separately show "Community" and "Apache-2" on our feature matrix on product page, but frankly, it was too confusing / too much information for visitors that were just coming to TimescaleDB for the first time. Especially given that the vast, vast majority of deployments are indeed the Community edition.
For a detailed comparison, our docs should explicitly label all community features as "Community Edition". Otherwise, they are Apache-2. For example, see the labelling with compression [1], continuous aggregates [2], etc.
And we continue to provide binary packages for the Apache-2 edition of the TimescaleDB, which you can similarly find through our installation instructions (eg [3]).
It is Apache version of TimescaleDB there (right?), which stays the same. While, those, who are using TimescaleDB under Timescale license, e.g., on premise, have now right to repair, for example.
Does this need some License information adding to your repo? Something that protects you from someone taking this and running their own paid hosted version :) I take it it isn't MIT!
We open-sourced it under Apache 2.0 which we find quite permissive and OS-community friendly. You're welcome to run a hosted version. We actually have it running on dstack.ai (it's free currently but we of course plan to have paid features if there is such a need).
Hey, please do! Onboarding new people and teaching skills is fun, and learning them while working on a project people actually use for day-to-day work is even more fun.
I idle in #haiku on Freenode, so ping me there and I'll usually reply soon enough. :)
Can the SEC really do this given the content of this tweet? Surely they can’t seek approval for every tweet about Tesla? What if he says he’s driving home from “the Tesla factory”. Does this count as a breach if he didn’t seek approval?
Musk and his lawyers agreed to the terms of the settlement.
The only reason he had to settle in the first place was because he tweeted false, market-moving information via twitter. Maybe Elon should have considered the consequences then.
Why didn’t he just hand over his twitter password to a social media manager and stop tweeting once he lost millions of dollars over the last tweet?
The former work for him, and he controls the latter. The "independent" board member Tesla added after signing the agreement was non other than Larry Ellison
Tesla formally said in 2013 that Musk's personal Twitter account was one of the ways "we announce material information to the public about our company, products and services and other issues."
Its about tweeting material information or disinformation about the company.
If he's saying he's driving home from the Tesla factory, that isn't material information. Him tweeting that Tesla is going to make 500k vehicles is material information and needs to be vetted by the agreed upon process per the settlement.
Elon specified that this Twitter account is a place to find official Tesla announcements. He could have said it was his private opinions but once he said it was official hes bound by those rules
It's only for tweets that are "materially relevant" to Tesla's investors. I don't know if the CEO visiting the factory qualifies as relevant to investors, but any comments about production rates certainly would, since ramping up production seems to be one of Tesla's biggest struggles. The fact that he said something untrue about production rates (overstating previous predictions by 25%) certainly doesn't help.
The order was to get approval for tweets that would have "material consequences for investors", so presumably just mentioning Tesla as part of his day to day routine would be fine.
But honestly, its not like its that hard to just not tweet about Tesla.
His tweet would be more like “I am driving home from factory that is still open at 20:00 and all workers are there”, when it closed at 18:30. Moreover, given his history I am absolutely seeing why a single tweet is enough to start a litigation against him.
https://www.newscientist.com/article/dn3232-first-speed-of-g...