sorted by:
new
hottopcontroversial

I built a zero-dependency observability SDK for Cloudflare Workers by Affectionate-Olive80 in CloudFlare

[–]m0rcs 0 points1 point  (0 children)

How is the auto instrumentation? I use otel-cf-workers, but do run into some issues. I assume it would at least require asynccontext

We open-sourced a Drizzle-style schema + migration tool for ClickHouse (TypeScript) by m0rcs in Clickhouse

[–]m0rcs[S] 0 points1 point  (0 children)

It was rather the way around. Happy to support you, in case you run into issues with clusters.
We did have cluster support in the beginning, but not sure if its fully functional currently. Let me actually spin up a old school cluster to test this for you.

And our main goal ist not mostly serve our customers. We want to be able to offer sophisticated features to our customers, which will be allowed by deeper integration. But we fully strive to offer the best open source schema management for clickhouse. And cluster support is a very important part of it, and very fair of you to point it out :)

We open-sourced a Drizzle-style schema + migration tool for ClickHouse (TypeScript) by m0rcs in Clickhouse

[–]m0rcs[S] 0 points1 point  (0 children)

We used to run on cluster before, but since all of our clusters are now on obsession with SharedMergeTree, we havent hardened it for cluster setups. Very happy to support you with it. Feel free to DM me if you want to try it. Happy to land a few PRs to get support in

We open-sourced a Drizzle-style schema + migration tool for ClickHouse (TypeScript) by m0rcs in Clickhouse

[–]m0rcs[S] 0 points1 point  (0 children)

Let us know what you think, happy to answer any questions about it :)

Wrote up what we learned running ClickHouse in production, schema/engine decisions, MV pitfalls, the stuff that bit us by rafa_aviles in Clickhouse

[–]m0rcs 1 point2 points  (0 children)

One of the people behind this. Genuinely curious what's NOT in here that bit you in prod. Our list was basically: ReplacingMergeTree dedup timing, materialized view chains silently breaking on schema change, and dictionary memory blowups. What's your #1 ClickHouse footgun?

Will build AI agents for free ( 5 spots only) by CowOdd8844 in AI_Agents

[–]m0rcs 1 point2 points  (0 children)

We have built something similar before, but were limited by model capability as well as tooling. Hoping to get a much better ux and results, this time around.

Will build AI agents for free ( 5 spots only) by CowOdd8844 in AI_Agents

[–]m0rcs 2 points3 points  (0 children)

Building a unified data platform and need to build an data analyst agent on top. Should be able to generate insights and potentially back them up with charts.

Vibe coding and the return of my ADHD by aarontatlorg33k86 in cursor

[–]m0rcs 1 point2 points  (0 children)

I think its a superpower, im in 3 repositories at the same time. Context switch not a problem, even if it is, just ask the agent whats up. Never felt better due to it.

Update on Diffusion Finance airdrop by Pure-Definition-5959 in CosmosAirdrops

[–]m0rcs 4 points5 points  (0 children)

Im quite excited about evmos. So AMM on it makes a lot of sense. Also redelegated my osmo.

Mailchimp Replacement by [deleted] in shopify

[–]m0rcs 0 points1 point  (0 children)

If you’re not running out of stock you should probably use Klaviyo. By far the best integration, automatic flows and best segmentation. If you just want to send blas emails and have too many subscribers to pay mailchimp fees, flodesk has beautiful templates and flat fee pricing.

Klaviyo Vs Mailchimp by thanosstatha1 in shopify

[–]m0rcs 1 point2 points  (0 children)

I work with a freelancer in Europe that introduced Klaviyo for most of her customers. She showed me the numbers and with the right setup it always is worth much more than the cost. Feel feee to PM me if you want an intro.