112 karma · joined March 16, 2020
Gaming, Programming, Remote Work, Technology, Travel ---
I agree this can be defined as cool and very very likely someone did this on their free time/prompted Claude on the side.
We've always been open source, so I'm not sure I understand what this is about! This is linking to our `posthog-foss` repository which has been a thing for years now, it's simply the main repository without the `ee/` folder - which is not a folder we have a lot inside anyways, we've never tried hiding anything behind it intentionally.
edit: the title originally read "Posthog has been open-sourced" but it's now updated to better reflect what this is about, thanks mods!
For client: If you are using [LLM Analytics](https://posthog.com/docs/llm-analytics) you'll properly capture your tool calls to MCP servers.
For server: It's just normal code, you can instrument and call `posthog.capture` like normal
Remote: Yes
Willing to relocate: No.
Technologies: Ruby on Rails, Typescript, React, NextJS, Elixir, Phoenix, Django, PostgreSQL, Redis, AWS, Docker, etc.
Résumé/CV: https://drive.google.com/file/d/11ZWxIrmjtN0ZMCjCIMNz3IY39x7... Email: rafaeelaudibert [at] gmail [dot] com
Linkedin: https://www.linkedin.com/in/rafaeelaudibert
Github: https://github.com/rafaeelaudibert
Website: https://www.rafaaudibert.dev
Senior Full Stack Software Engineer with 7+ years of experience in various industries, ranging from seed- stage SaaS startups to growth-stage scaleups. Proven track record of working with Ruby on Rails, Python + Django, Typescript + React, and Elixir + Phoenix, building reliable and scalable software. I'm motivated by creating new and engaging customer-centric apps loved by clients.
Edit: formatting
Simply removing them in a commit isn't enough to hide them from the internet
I guess we don't need to move them because we have plenty anyway, compared to the few ones the Americans have.
I'm not sure if this is really a rewrite, or simply an adaptation. I don't think the license could have changed, be advised.
Diff data + new data definitely seem what 90% of your customers will need.
Another quick question: When you say "Job Success/Failure", what's a job?
_Full disclosure: I work at LeadSimple <https://www.leadsimple.com> and we integrate with most of these companies ourselves, and these questions were just me being interested in knowing how you solved (or intend to solve) some of the same problems we had to solve when integrating with them :)_
1. Where are the docs for Webhooks?´
2. Is there any way to get only partial data, which was updated since the last time we hit your API? Is there a way to use a date-based cursor?
3. Is the data being saved (and duplicated) in your server, or are you simply parsing the request, converting to the PMS format, hitting their API, formatting the data, and sending it back, every time?
edit: formatting
Edit: hold on, that was me being dumb. The actual bug is that if I press "Caps lock" (because I type capitalized letters by quickly typing Caps lock + Letter + Caps lock) it incorrectly counts it as a keypress.
You definetily can! We used Slate `0.47.x` at Leadsimple[0] and we went through the same hustle and decided to go with Slate again! We have both versions running in production for 3 months now, and we didn't have any problem. You can add separate versions of the same library using a feature of `yarn` which allows you to declare `"slate": "^0.47"` and `"slate-latest": "npm:slate@^0.72.0"`. Then, in your code you just need import `slate` when you want the older version, and `slate-latest` when you use the new one. We also had to inline some stuff because `yarn` isn't the smartest when solving dependencies, but it sure is possible :). It wasn't easy, but the end result is amazing, and REALLY fast, hasn't caused any problem to us.
Every common feature you need, multiplatform, and customizable