@bitbrain Zeile 13 ist falsch eingerückt, oder irre ich mich? Du fügst in dem Falle ja nur den Subscriber hinzu, wenn das Event an sich noch nicht existiert?
@alexjgarrett I'm used to scripts at the bottom, since I always put scripts at the bottom which are in need of getting executed right after the DOM has been "rendered".
@simonswiss@ProTailwind Besides this: I'm using Tailwind since about 4 to 5 years (I guess), and sometimes it's the easiest solution you won't come up with. Thanks for the idea mentioned above.
@ukutaht Hello. :-) I have a technical question: why are you using a "Flat Table" in ClickHouse for events (plausible)? Isn't it too much redundancy if it comes to millions of "rows"? Are JOINs too expensive in ClickHouse?
@PlausibleHQ @thomtunes @ClickHouseDB I've read your blog entry regarding migration to Clickhouse. You have faced the exact same problem I had: "combinatorial explosion". I've tried to pre-aggregate the most common combinations and it worked... until someone wanted a custom combination...
@PlausibleHQ Hey guys. I've tried to build a tracker on my own and I just got frustrated because I've only used MySQL. Hitting 6 millions hits a day and storing them... aggregation took a while (especially real time reportings). Well... I've seen you're using Clickhouse... (1/2)
(I'm asking because such an amount of data, self hosted, can be pretty heavy and solutions - by just using MySQL - are pretty hacky and I hate hacky stuff. It's not clean... I hope to get an answer.)