Hacker Newsnew | past | comments | ask | show | jobs | submit | leafac's commentslogin

I too love how simple the infrastructure can get using Go’s tools. At the same time, I prefer Node.js for the libraries & bigger community. So I developed a tool called caxa which brings the best of both worlds, packaging any Node.js into a single binary. Check it out at https://github.com/leafac/caxa


It’s a nice surprise to check HN and have my project featured on the front page.

Thanks polm23 for posting and everyone else for the nice words!


Thank you for creating this!

I'm an avid user of RSS and Atom, and I absolutely loathe email subscriptions (although I understand why many groups use them), so a tool to remove that friction for admittedly rare people like me is wonderful. Thank you for running this service, I intend to use it quite a lot!


Seems it'd take significant costs to run it, how do you still manage to do that?


The most significant cost has been my time, but that’s my pet project in which I get to experiment with new technologies, so it pays off nicely.

Also, you can support me: Recurring (Patreon): https://patreon.com/leafac / One-time (PayPal): https://paypal.me/LeandroFacchinetti

In terms of server costs, it all runs smoothly on a $6/month DigialOcean droplet. Even when I end up on the front-page of HN (it’s the second time this happens). And there’s also the ~$10/year for the domain.

There’s actually a fun story behind this: The biggest constraint is bandwidth (~500GB/month). I was using S3 and at some point that’d amount to $50/month. But DigitalOcean droplets give you 1TB/month, so to save money I rearchitected the whole thing to just use the filesystem. It turned out to be simpler and nicer to maintain, too. Fewer moving parts.

Fun stuff…


Shameless self-promotion: I’ve been in a similar journey of learning DSP and I’ve been sharing my findings as well: https://youtube.com/channel/UC_R-6HcHW5V9_FlZe30tnGA


Subscribed. Shameless FOSS promulgation: how about a video or two on making an LV2 plugin? Maybe check out DPF and #lad / #lv2 on freenode.

https://github.com/lv2/lv2/wiki


Thanks for the suggestion. I’ll check it out.


A JavaScript & TypeScript package with collections like JavaScript’s native Maps and Sets, but using value equality (deep-equal) instead of reference equality.


Hi all,

Author of Kill the Newsletter! here. First, thank you ProfDreamer for finding my service and posting it here. Thanks too to everyone that took interest in Kill the Newsletter! and commented or wrote me emails. I appreciate the kind words and testimonials that the tool was useful to some of you. I also appreciate the suggestions for improvements, I’ll try to implement them in the near future.

Kill the Newsletter! ended up on an LifeHacker article: https://lifehacker.com/kill-the-newsletter-converts-newslett... As a long-time reader of the website, I’m flattered.

Finally, I want to say a word about the name of the service. The copy on the website starts with “I love newsletters …” This is true, otherwise I wouldn’t have created the tool. So don’t really mean to extinguish the newsletters. I understand RSS users are a small niche when compared to email users. I also understand the business reasons to prefer mailing lists. The comments on this thread had some very interesting arguments on that topic. I certainly learned a lot by reading them.

The name Kill the Newsletter! was supposed to be whimsical. But I understand death and specially killing are sensitive topics to some people and I apologize if I offended them with my joke.

Still, I hope everyone can enjoy Kill the Newsletter! if they ever need to convert that mailing list into an RSS feed.


Great service, but you might be encouraging more annoying newsletters. Before, they just lost out an audience who wouldn't stand for annoying automated email ;)


Hi ommunist,

Author of Kill the Newsletter! here. Thank you for your comment. I think it’s cool that you’re using an email reader that doesn’t require any clicks :)

But, seriously, of course the tool I developed is for a niche. In particular, I had only my own use case in mind. I know the benefits of newsletters. So much so that Kill the Newsletter! starts with copy saying “I love newsletters …”.

The name Kill the Newsletter! is only a joke. I’m sorry that you seemed not to appreciate it. After all, joking with death and killing is not exactly G-rated. So the joke is actually on me and I apologize if it caused you any inconvenience.

I hope you can still consider Kill the Newsletter! an option if you ever run in the inteded use case.


Hi sincostan,

Author of Kill the Newsletter! here. Thank you for your comment. I tried the tool you mentioned before creating Kill the Newsletter! Of course, I was trying same work :)

Unfortunately, I ruled it out for two reasons. First, it required a Google account, thus binding my identity with my reading preferences. Second, I set up a throwaway Google account just to test the service and it didn’t work. I can’t remember exactly why, though.

It was definetly an inspiration for Kill the Newsletter! It gave me an indication that the project was feasible.


Hi ourcat,

Author of Kill the Newsletter! here. Thank you for your comment. Indeed, the tool generates Atom feeds instead of RSS. It is a better format. But RSS is a more popular term, so I went it. It’s like the TLS vs. SSL: I only use the term TLS with highly technical audience.


Hi akamaozu,

Author of Kill the Newsletter! here. First, thank you for your interest. Nothing technically prevents you from using the tool in the way you propose. But I ask you not to, if you can. See https://news.ycombinator.com/item?id=12957555.


Hi norswap,

Author of Kill the Newsletter! here. That is a valid concern, thanks for bringing it up. I worry about this myself, being the #1 user of the tool. Do you have any idea how to fix it, though? I thought of a dead man’s switch kind of thing, in which I would periodically add an “everything is still working” for low-volume feeds, but I didn’t do it because I would consider such entries spam. What do you think?


I don't really have a better suggestion. Ideally, making sure that the feeds would raise some kind of error condition in all feed readers, but I doubt there's something universal like that.

Maybe the "still working" message is good enough, it wouldn't bother me too much, personally.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: