sirffuzzylogik

Thank you, I contacted dang, sorry again for the issue.

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.

[1] https://www.cnbc.com/2021/01/27/hedge-fund-targeted-by-reddi...

EDIT: My bad, the hedge fund was not closed, just its GME short position. I amended this.

> 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.

[1] https://edition.cnn.com/2021/01/26/investing/elon-musk-etsy-...

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":

https://retractionwatch.com/2020/10/26/paper-suggesting-vita...

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.

[1] https://en.wikipedia.org/wiki/Glasgow_effect

> 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.

EDIT: Source, the publication: https://www.sciencedirect.com/science/article/pii/S036012851...

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.

You should try to use the "sync" command, this is exactly what it solves.

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.

[0]: https://www.postgresql.org/docs/9.4/pgprewarm.html

This is on the roadmap, we will work on integrating with https://github.com/timescale/tsbs, TSBS has Victoria Metrics support too.

Thanks Jan!

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.

I tried with the same setup and it works fine. I tried to disable JS too and it's OK. Could it be a rogue extension?

What browser are you using?

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.

j1897 is referring to https://questdb.io/blog/2020/04/02/using-simd-to-aggregate-b...

I have not tried to benchmark Atlas but I am not sure the result would be meaningful. Atlas is an in-memory database, QuestDB persists to disk, the 2 are not very comparable.

PostgREST is an interesting project, thanks! I will check how good is our support for them. It really depends on how tailored to Postgres they are, if they only rely on the Wire protocol then it should be fine!

Thank you for your thoughts!

1. We do plan to support full SQL functionalities, we have a pretty good subset already [1]. I think that what we do is more than "naive memory bandwidth bench code", however I am happy to listen and when the time is right implement functionalities/features that you think we are missing.

2. "Can you hold such statement in the title when you enable reading from persistent disk?" We already persist to disk, the numbers you see imply reading from disk. We do this by using memory mapped files [2].

[1] https://questdb.io/docs/sqlExecutionOrder

[2] https://questdb.io/docs/storageModel

EDIT: fix typos

We already support the Postgres Wire protocol, it is still in alpha though. You can check the documentation here: https://questdb.io/docs/guidePSQL/

We do not implement 100% of the protocol yet, but the plan it to do so or at least implement all the features that people need.

I have mixed feelings about this feature actually. It's super handy and nice when browsing the Web while going through a lot of pages in a short amount of time. When using proper Web apps it's a total pain + sometimes the history API is not supported correctly so you lose the context entirely (which means you have to start from scratch in whatever app you are using).

Gestures in general should be something standard, cross platform / cross browser with a nice API exposed to JavaScript. However, I understand why it's not, they were a mess on Linux until very recently, it's all over the place on Windows, support depends on the hardware, they are not very intuitive, etc.

Sorry for the frustration guys, this was not meant to be "something to lock people in". The rationale for doing this was to prevent macOS users from going back when scrolling the grid horizontally. I submitted a PR to remove this for now, in the future, we will implement a better solution that does not mess with the History API.

Thanks for the feedback. A PR was created to fix this :) : https://github.com/questdb/questdb/pull/434

The numbers are impressive, especially because it is against kdb. q/kdb is mostly finance focused and closed source so not really flexible. questdb has an advantage on this, it might be a bit of a tangent but I wonder if this could be used to replace redis, I can see how having SQL as a querying language could be a big plus.

How does it compare to kdb performance wise?