abe94

When I (bengali speaker) visited Bhutan where they speak a language that is 50% mutually intelligble with Tibetan I didn't understand anything. I was surprised because I thought they might use a number of buddhist loan words, but even the words for dharma, karma, etc. sound completely different in tibetan

One thing I was surprised by was the number of survivors and also that there was at least one person who survived both bombs [1]

[1] https://en.m.wikipedia.org/wiki/Tsutomu_Yamaguchi

I listen to quite a variety but a lot of house, and afrobeats while programming

The main learnings for me were

1. To get my data to speak to me I had to find the right cut. Instead of plotting my data on a daily basis I found the Year - Month - Week basis to be way more clear. 2. My Sleep Consistency was/is crap 3. Listening to music while programming may be making me deaf over time

Of course if creating things makes you happy go for it, but don't expect to be able to live off of that.

I am sympathetic to the idea that the revenue share isn't great, and I also agree that there are anti-competitive practices, and the market would do well with more competition. But i do think its the wrong starting point to believe views or listens on these platforms should be enough to sustain a creative career for most artists.

As you alluded too, even amongst the most well known musicians they make a lot of their income from touring, my perspective here is that these platforms when well used give you exposure, then with a linktree / beacons link an artist can develop a relationship with some of their audience that provides further opportunities to fund themselves.

Its a great question to ask when the "exposure" benefits the artists more, and when it benefits the platform more, i'd personally love to see some quantitative analysis of that. My suspicion is for most small artists with audience sizes of less than 100k people (in the west, the calculus is probably different in the rest of the world) the benefit to the artist is really great. For someone like Taylor swift it benefits the platform more, but at that point she can negotiate directly

For the other platforms, yes you need to a do a little more work to make it a living, but the broader point is its much easier today for a much wider range of artists to get exposure than it was before, yes there are vagaries of the algorithm and yes some content will not be favoured, that doesnt mean it isnt a better situation today than before

As for "working for free" this is a very reductionist view. The relationship can provide value for both parties, you may disagree about the split of value and who benefits more but there are plenty of artists who have become popular without paying for ads.

For a lot of people this is a better alternative than the old gatekeepers of yore, small or local magazine editors and tastemakers who may for whatever reason hold you back

Here are some local NYC artists/groups i follow in order of followers:

https://www.instagram.com/secret_riso_club/ https://www.instagram.com/sahanabanana/?hl=en https://www.instagram.com/naomi.basu/?hl=en

We needed features like job priorities, and complex routing logic and on top of that our software needs to send millions of messages a minute. What we miss is a nice UI to see the state of jobs, and monitor for problems more easily like: https://taskforce.sh/

laudspeaker (open source firebase cloud messaging/customer engagment) - https://github.com/laudspeaker/laudspeaker

panopticon (short story on encryption and espionage) - https://docs.google.com/document/d/1VRI4X5fCUpwurUDvKmvzJpT7...

For those interested in a good overview David Reich's book is still excellent - https://en.wikipedia.org/wiki/Who_We_Are_and_How_We_Got_Here

And if you're interested in an in-depth ancestry analysis of your dna you can use commercial options like https://illustrativedna.com/ or analyse your dna yourself with qpadm https://uqrmaie1.github.io/admixtools/articles/qpadm.html

- Operating in a regulated industry, we have customers who cannot send customer data to 3rd party services (in financial services, healthcare) and need to self host for that reason

- Existing solutions are too expensive for their business model, we have Kenyan, Brazilian and Mexican consumer focused companies from other countries spin up and use the self-hosted solution

- Cost savings and Philosophy, believe it or not there are some companies which like to self host software if possible, and have dedicated dev ops resources already maintaining software and spinning up another solution is not that much incremental work.

Beyond that there are other reasons to want to open source a solution like this. Anyone can add communication channels and integrations for example. And lastly its fun to work on an open code base!

We are trying to find a pricing model that can work for consumer facing apps/sites and companies, as well as B2B!

We offer enterprise level support for self-hosting users in the paid plan, and they can use future features in our ee (enterprise) folder (which is empty right now)

Chatwoot is a great tool, but is more in the customer support space. It offers a chat widget in your saas app / website and a shared interface to respond, which can then get routed via email, sms etc to the person who asked the question.

Laudspeaker is more of tool to send 1) one off messages (informational, promotional) to segments of users you define, 2) automate message sends like a drip campaign, 3) trigger automatic real-time messages based on specific activity users take in your app or site, eg on add to cart, or on sign up

The users of chatwoot would be customer support / success, the users of Laudspeaker would be growth, marketing, product

The architecture of both applications are quite different. Laudspeaker needs to be able to quickly message millions of users, ingest real time events, and create references to large sets (millions) of users.

We actually used chatwoot for support a while back, and have a customer who uses both Laudspeaker and chatwoot in production!

One thing that stood out to me was the graph of the sentiment analysis over time, I hadn't seen something like that before and it was interesting to see it for Rust. What were the most positive topics over time? And were there topics that saw very sudden drops?

I also found this sentence interesting, as it rings true to me about social media "there seems to be a lot of negative sentiment on HN in general." It would be cool to see a comparison of sentiment across social media platforms and across time!

Laudspeaker | Remote| Full Time | Senior Software Eng / Founding Eng

We posted on hacker news a few days ago - you can see the whole post here (https://news.ycombinator.com/item?id=39836316)

Summary below:

We are building a new, open source suite of software tools to completely handle the "customer journey". You can see our repo here: https://github.com/laudspeaker/laudspeaker

We are a small team of 3, had a successful launch on HN a year ago, are backed by YC, and and are now starting to close large companies deploying our software to touch millions of users.

Who You Are: - You are a very strong senior engineer (5+ years of industry experience) who can work autonomously and can deal with ambiguity - You are comfortable working at all levels of the stack, from creating new endpoints, and components to deploying our app - You have great knowledge of working with AWS, Docker, and Kubernetes - You have great proficiency in TypeScript and NodeJs

Bonus: - Have worked in the product analytics or customer engagement spaces before - Have taken a SaaS product from 10 to 1000 customers - Has hacked on mobile sdks before - Has worked remotely before

About the interview:

Between one and two rounds of phone screens followed by a one month (paid) contracting period. You'll be paid full salary and will be doing the same job as what you would when working with us full time. Contracting can be terminated early if either party feels its not going well.

If this interests you please reach out to the founders, at hey [at] laudspeaker [dot] com

Some differences:

a) We have explicitly decided against a DAG approach [2] for our visual editor and use state machines as our model, so you can explicitly create things like loops, and customize journey logic more.

b) Our cloud pricing is not user based, but right now follows a pay as you go model for usage with sliding discounts for larger message volumes [3]. While the mechanics may change we are most likely going to avoid user based pricing models.

c) We support different channels at the moment (email, sms, firebase push, slack, in app modals) and we integrate with databases/ warehouses as well as product analytics services like posthog [4] and CDPs like rudderstack. I'm sure with time we will converge on the same channels/integrations.

d) We think journey versioning / testing is a great idea, and don't yet have that but are rolling out our own.

Some similarities:

a) We also use clickhouse, and at some point will use temporal (our project is supported by one of their executives)

b) We also have a visual editor, segments and templates

c) We can be self-hosted (A few users are self hosting today)

For others checking this out there are also older projects like Mautic [5]. And customer engagement is a large enough category that it includes projects like Chatwoot [6] that focuses more on customer support.

[1] https://github.com/laudspeaker/laudspeaker

[2] https://laudspeaker.com/docs/engineering-blog/finite-state-m...

[3] https://laudspeaker.com/pricing

[4] https://posthog.com/tutorials/laudspeaker-posthog

[5] https://www.mautic.org/

[6] https://www.chatwoot.com/