Thanks for explaining, I thought "Show HN" was for any app/project to be demonstrated, not necessarily affiliated with the poster. I just (re)read the rules and I am sorry for this mistake, maybe @dang can amend the title?
OP here, as you said and to confirm, I am not involved with the development of Berty in any way.
My understanding is also that Berty is not fully production ready yet, however I have been following the project for a while and they seem to be going into the right direction. Other HNers might also be interested and who knows, the project might grow faster with more people involved.
Citadel and Point72 stepped in and closed the hedge fund position ($3 billion) on GME [1]. The regulators are not moving/commenting just yet, I am curious to see the repercussions of this and if Reddit crashing the markets it the new norm.
> Social Capital’s Chamath Palihapitiya jumped into the controversial name, saying in a Tuesday tweet that he bought GameStop call options betting the stock will go higher. His tweet seemed to intensify the rally in the previous session. The stock ended the day 92% higher at $147.98.
This is growing into a bigger problem. The thought of Twitter influencers (example with E. Musk / Etsy, yesterday [1]) heavily moving the value of stocks with a simple tweet is not really reassuring. The SEC should start investigating properly into it, from personal benefits to bigger company wide fraud, the regulators need to act before this is the new norm.
It is good that the UK is trying to tackle the vitamin D deficiency problem that is affecting its population. However, it should probably not be done under the "covid prevention" banner, the paper suggesting that vitamin D might protect against it recently "earned an expression of concern":
This is not really a surprise, public health varies greatly even within one country/city. In the UK, there is a similar phenomenon between certain areas of Glasgow and the rest of the country / continent, it is called the "Glasgow effect" [1]. Although the gap is not as wide, "only" 7 years, it is explained by poverty, unbalanced population, low-quality estate and pollution.
> If I want a managed service, I _want_ to pay for that. The price includes people responding to pages and fixing problems, as well as fiddling with configs.
Is this not what S3 is? You are free to use Elasticsearch and handle everything yourself, but if you want a managed service, you can use AWS. They are "attacking" the S3 offering, I still struggle to see any difference with them hosting Postgres.
> And I'd much rather be paying that money to a small (relatively) open-source company than a behemoth like AWS.
I am 100% with you on this, I do not want to defend AWS nor do I want to promote their products. The vendor lock-in situation you are in when using AWS is pretty bad and quite scary... An yes, I agree that the way they monetize open-source software is questionable.
The nice thing in this process of the oxidation of the metal, it is done with hydrogen and does not involve any emission of CO2. Effectively what they do is:
Electricity from renewables -> Hydrogen (electrolysis) -> (iron oxide to iron, in loop) -> heat -> iron oxide.
I would say this is a nice solution to the problem of storing hydrogen.
Wayland support is actually being actively worked on. It is done via "native" (no X widgets) GTK support. You can find it on:
https://github.com/masm11/emacs
The plan is to get that merged upstream at some point, you can find out more about it on the official mailing lists.
I've been doing exactly this for years with Revolut premium (and I'm sure many other "online banks" have the same service). It's like using a password manager, you don't have to worry about how your card details are stored anymore.
It is very neat although I got into strange situations a few times when I needed to prove I was the card owner for a refund or for insurance claims.
I agree that our blog post lacks of details, here are some:
- PostgreSQL 12
- 12
- No
- We ran the test using the pg_prewarm [0] module, the difference was negligible
Regarding the "toy" query, the reason we are showcasing this instead of other more complex queries is because this is a simple, easily reproducible benchmark. It provides a point of reference for performance figures.
> Database benchmarking is pretty complex (and easy to bias), and most queries do not look like this toy one.
I would say that benchmarking is very hard. We tried not to perform a biased benchmark by running something that is not time-series specific and which does not put us in advantage compared to what Postgres should do.
The takeaway from this is that configuration is important and we should expose it. The next benchmark we do will have an associated repository so people can review our config and point non optimal items if any.
Not yet but this is on the roadmap. In the meantime you could use a filesystem that supports compression such as ZFS or brtfs. The data is column orientated, this means that compression would be super efficient.
Thanks for reporting this!
This is an old link, please use https://questdb.io/docs/guide/crud instead. I am currently updating the README and removing all dead links.