HNHacker News
TopNewBestAskShowJobs

kureikain

1,285 karma · joined January 23, 2010

https://mailwip.com for email forwarding

Reach out at vinh@mailwip.com

AWS EC2 price API https://ec2.shop - ec2 price api

submissionscomments
kureikain··on Building data-centric apps with a reactive relational database
anyone how what tool we can use to make those chart? It looks friendly.
kureikain··on Ask HN: What Roles/Skills Do You Struggle to Hire For?
good front-end engineer that can do 2 things:

- ui - logic

good devops engineer that can do 2 things:

- dev - ops

kureikain··on Agatha Christie could afford a maid and a nanny but not a car
off topic but in many stories of Agatha Christie why husband and wife never slept in same room?

Is that how English people in the old day live, sleep in separate room even after marriage?

kureikain··on Google requiring all ‘G Suite legacy free edition’ users to start paying
I made https://mailwip.com as an email forwarding solution for this purpose.

Simply point your MX records to our server, then email can be forward to your personal gmail/protonmail.

kureikain··on My First Impressions of Web3
The server here is actually not a centralize server in a traditional world. It's a node that connect to the network and replica state.

When running transaction, you send it to that node, that node then broadcast it to network. This node here is like a replica in a traditional database.

You can run that node, and talk to it through http, websocket.

The point about trusting server signature the author bring up is bad IMHO. Even with a database, if you install some malicious Postgres package that return fake data for example, it doesn't help you at all if you enable TLS or not.

The point about verification is that read-only data isn't important because write always get verified. If you connect to a malicious node, that change the data it returns to you on purpose, then it's fine. But when you write data to the system, it always get verify so it isn't a problem at all.

The point here is that you are the one that run that node, and you are responsible for it. Entire point of Ethereum is that anyone can run node that connect to the network to replicate its state.

If you take out all the hype(OpenSea is a massive scam here no argue), I found web3 is really amazing.

1. It's a public dataset that anyone can read data and listen to event

anyone know something like that in current web1/2? Example, when I bough a domain name on namecheap or google domain. Can anyone know that? When I change my DNS, do anyone know that?

With Ethereum when you run a WRITE method on a smart contract, when you transfer event. Everything can be emitted. And you can listen to it.

The code is almost always open source.

2. Build-in Authentication System

Many website use wallet to sign in but didn't verified a signature. In fact, that signing is very cool in deed. That signature verifcation ensure that only you can sign that data, send it to server and server can verified it with your public key, which is part of your address

3. No one can stop you

If you search hacker news, you will found many people got blocked/suspended randomly by Stripe, Paypal then what do you do?

4. Openness

This is a system that anyone can read. Think about that for a second. Anyone can read its data. Without the need of any API. Everything follow a standard, which is smart contract.

Anyone can write, if you're willing to pay.

You're pretty much can see the code of any legitimate company. Pretty much all of them published their contract on ethscan, to make it convenience for you to run directly.

If you don't like some webui, you can just write to its directly.

Literally just a `curl`, without you to even register for an account.

I know that many people like to dismiss web3, the term is broad and bad IMHO, but think about the thing that it gives us. I can think of some example how web3 is great.

1. ACL: any changes is published, if a malicious activity happen, pretty much anyone can monitor it 2. Charity Fund: we can see what happen with the fund, transfer to where, when, who made it

kureikain··on Why might you run your own DNS server?
I found one of challenge when running a public dns resolver(and authoritative name server if we're being target) is DNS Backscatter. Up till nowsaday I don't really know how people solve this problem.

Anyone can lighten me up on how to defend this kind of attack? I really want to run my own dns server

kureikain··on Ask HN: How do I deal with not being able to build products
The only hack that made my finally shipped my product is having a weekly sync with some friend and just talk about what I do. Make it a routine. It forces me to build.

This is my thread https://news.ycombinator.com/item?id=25911355

I launched it very early with lot of "hacky" feature(and still nowsadays).

Few thing to help you shipped:

- Choose something you are super and very familiar. This is your product, not your play ground to experiment - Have your friend use it from day one. It forces you to roll up your sleeve and fix bugs - Weekly sync

If you want, hit me up at vinh@mailwip.com and I can do a weekly sync 15mins with you.

kureikain··on Best practices for writing code comments
IMHO those aren't best practice at all. It's just a vague list pick for the sake of writing these article.

To me, the most important is that comment isn't the code. Then what it's and why we write it. Now, common becomes normal writing.

So the rule is? Know your audience.

Just think who you write this comment for and explain that to them. It helps a lot to guide people through what the code do. Especially in even driven code.

Imagine this pseudo code:

send_event({name: 'a', {props: name: 'a"}})

Why do name show up twice there? Without comment noone know why except people have business visbility. Because apparently some down the life consumer need the name in `props` and it cannot access the root of the object.

So. my best practice is know your audience when writing code comment.

kureikain··on List of 4,248 open source programming languages
Want to plug in my favourite https://github.com/kanaka/mal basically make a lisp in lot of language.

Really give you ther idea of what is needed in build a programming language. Soemthing won't quite obvious. until you I down and write code. Example the ability to rewind, go back to a few earlier token.

kureikain··on Running your own email is increasingly an artisanal choice, not a practical one
I ran an email forwarding service https://mailwip.com (former hanami.run) that also support SMTP and IMAP.

IMHO, gmail is the best company out there that can accept your emails. The most common issue with gmail is email land in spam but they learn quickly and very rare just outrage reject IP. as in, gmail won't relying solely on reputation of IP but based o sender domain or so.

Compare with hotmail or icloud or some random email hosting service, they will reject your IP just outright.

I would say it's definetely tough and stressful to run an email services for everyone, but if you run it for yourself only(so you know you're good and won't send out random spam), I will say it ins't that bad.

kureikain··on Ask HN: Those making $500/month on side projects in 2021 – Show and tell
I run an https://hanami.run email forwarding service with advanced features:

- SMTP - Maillog: which can eanble you to use IMAP - API integration to read email as JSON - WebHook - Complex routing with regex and custom rule from header - Sieve filter

Note: We're re-branding to https://mailwip.com due to nameconflict with hanamirb.org

kureikain··on Ask HN: Great tools for solo SaaS founders?
I found https://hanami.run (soon to be mailwip.com due to name conflict with hanamirb.org) to setup email forwarding and a simple blog platform by "email to post" and webhook.

Use it you can consolidate emails from multiple domains to forward to the same inbox. And you can add webhook/slack notification too.

kureikain··on From macOS to Arch Linux
I used Fedora/Ubuntu at works and Arch Linux at home exclusively to 2012 when I started to get into Ios dev.

Nowadays I used Mac exclusively for all of my work + personal setup(except Server of course).

And I'm convince that the only reason for me to use it is due to iOS dev. If I can get away with it I will go back to Linux. Some points:

- No more dealing with homebrew and its bizarre upgrade policies. You don't know when a package will be break. You run `brew install python` and every thing broken.

- No more dealing with the weirdo of its disk image and the locked of system volume

- No more dealing with junks stuff in a few place such as `/Library` or `/System/Library` and `~/Library`

- No longer has to run docker in a VM

- Fuse just works

- No more buggy file watchers. For some reasons the file watcher (fsnotify package I belive) on Mac sometime works, sometime not and sometime just had CPU up to 100%

- No more custom syntax to work with fslimit

- No more plist file that also gzip and encrypt

- No more installing software by going to a website and download a stupid xip file.

- No more reverse engineering how a certain thing works and script it out.

But due to iOS works, not just iOS development I also help with CI/CD for mobile app and having access to a mac locally is handy, I have to keep using it.

kureikain··on On autoloading
This is where Python shine I belive. Its import system is amazing. We can import the whole file or just particular funcion/method in that file. We can import relative with `.` and `..` and even `...`

And we can "import as" to avoid name conflict.

Using import together Mock library we can even swap out(Mock) particular imported item during unit test.

If one thing I would love to see is having that import system in Python ported to Ruby.

Granted that the way Ruby currently works also expose a few functionality for doing DSL easiser.

kureikain··on Truth about ProtonMail
You can look into mine (https://hanami.run) very fast to sign up and have a few cool features about webhook or smtp.

Also, improvmx.com is a great product as well.

If you like open source, https://maddy.email/ is a single binary deployment that can handle everything even IMAP.

https://mailcow.github.io/mailcow-dockerized-docs/ is a dockerize solution with super detail document as well.

kureikain··on Truth about ProtonMail
I think we all know encryption in term of emails is hard to read. Take encryption.Example, when an email failed to deliver and sit in retry queue, where is it on? on Redis, on disk? Is it encrypted or now? If it's encrypted how the search works?

One thing that I really appreciate is that I can reach ProtonMail support to asked why they flagged my email as spam.

I build an email forwarding service https://hanami.run and when we first rolled out I reached out to them, they explain to me my entire email looks good and problem is probably by the age of domains. A few weeks later our emails are no longer flagged as spam. I couldn't get that kind of support from gmail or outlook.

They also maintain https://github.com/openpgpjs/openpgpjs so I think ProtonMail still deserve some credits

kureikain··on Betrayal
I listen to this podcast a lot and it looks like Jeff is banned from Twitter/Facebook.

His podcasts help me learn English, I listen to it all the time 7 years ago because i's the only podcast in tech that has a daily volume.

I post it here to help him gain exposure to the world and no one can de-platform Jeff.

kureikain··on How to Create a SaaS and Compete with the Big Players as a Solo Founder
Hey,

Thanks for your kind words Codazoda. Much appreciate :-)

kureikain··on How to Create a SaaS and Compete with the Big Players as a Solo Founder
If you want to compete with the big players, you have to solve the most important pain point and work upward from that small use base.

My case: I work on https://hanami.run (will soon move to https://mailwip.com due to hanamirb.org conflict) and email forwarding is very competitive. Big and old players are all over the place because at the end of day, setting up email forwarding isn't hard and many open source project did it, heck you can spin up AWS lambda for incoming email in no time.

The pain point is: email will drop sometime, time to time no matter how good an email forwarding service is because they have to scan spam, have false positive, or because of strict DMARC/SPF rule. And I have no tools available to help me out there. So I focus strongly on my maillog features with many level of privacy:

- no log at all: defaut

- only log spam email: give you another chance to read email on our UI

- log meta data

- log meta data + subject

- log whole email

Then, next steps is regex forwarding. Again, I learned this from reddit, forum search of those use base.

Basically I focus on those small features that big player doesn't have.

Then I was able to obtain a very small user base who has issues with big providers. Then I work upward from there to spin out given now that I had a working and good product that people are willing to pay for.

The rest is just iteration.

kureikain··on Ask HN: How to work effectively at a typing-based job after breaking my wrist?
I'm in similar situation, not as bad as you but I have to use one hand at some points.

Here are the tricks:

1. Use split keyboards

2. Use two monitors: with 2 hand I can do alt+tab all day long but now It's harder

3. Assign hotkey to a certain applications/shortcuts

Then just consitently force yourself to do that everyday. It's terrible at first but you will get use to it.

kureikain··on Esbuild – An extremely fast JavaScript bundler
My project is small and it's amazing fast to me as well. It's basically just outsource its job to another cli. I used esbuild-plugin-sass

This is the gist https://gist.github.com/v9n/c40a6ad2078d09dd86117924b415b7fb

As far as I know, esbuild has no intention to integrate with CSS and will outsorce it to plugin.

I used

kureikain··on Esbuild – An extremely fast JavaScript bundler
esbuild is fast but it has a lot of place you have to figure out yourself and get into your way of doing thing.

1. dev server: you have to write a bit of code for this server to act as webpack dev server 2. scss: need to install plugin, and plugin cannot use from command line then you need to write a bit of JavaScript 3. global function: if you do `process.env` now you need to inject into build script 4. node package: if the package use node stuff you have to define thing like `fs/stream` into package.json

very quickly it get into your way of doing thing.

However, once you get past that base line, the cost is constant, the complexity just stop right there and not adding up.

Plus, the speed is amazing.

kureikain··on How not to migrate an email domain
We gotta give Mailgun some empathy here. It's tough to run an email service and keep reputation of it. If some bad actor got in, they can send large spam email and dilute the reputation.

Of course, this is just a mistake and after explaining Mailgun shouldn't charge $1358 for clean service. But as a customer, you should take some responsibility when doing something wrong as well. For example, if the account is old, and this is the first time this happen, and once we explain the mistake, Mailgun should waive that fee.

On AWS SES if the bounce rate >10%, your account is temporarily suspended.

If the exact samething happen with any mail provider, where a large of emails volume are bounced. They would need to pause/restrict your account in some way.

I would suggest look into AWS SES and started to write code to handle bounce email yourself to get a sense of it.

kureikain··on Ask HN: Solo-preneurs, how do you DevOps to save time?
I divided my infrastructure into two part.

1. Tricky and unfrequent changes: - mail server, load balancer, database etc: for this I just write bootstrap.sh, rsync to server and run. - It's literally just a for server in `foor bar`; scp ; ssh ` done

2. Deployment/Frequent changes: - docker-compose to spin up everything. It's super nice. Again, the deployment is done with a `rsync` then `docker-compose up -f docker-compose-prod.yml`

Eventually when deployment changes very frequent and need scale/ha I added in Kubernetes. K8S is way easiser to setup than you think and it handle all other suff(load balancer, environment variable etc).

And my deploy now become: `kubectl apply -f`

One trick I used is to use `sed` or `envsubst` to replace the image hash.

For backedup, I again, literally setup cronjob from an external server, `ssh` into database and run `pgdump`.

I also have a nice NFS server to centralize config and sync back to our git repo.

I used this whole setup to operate https://hanami.run an email forwarding service for the first 3 months before I added Kubernetes.

kureikain··on Cloudflare's Disruption
oh, ic.

To me, my biggest pain points is I cannot set NS record for a sub domain.

My use case is this: I had a certain subdomains where I want to use LetsEncrypt DNS with DNS validation. I don't want to give the whole domain to the auto renewal script. With another DNS provider, AWS Route53 for example, I can easily create another zone for that subdomain say blog.domain.com and set NS record on blog to that zone. Then create an API key with only privileges to manage that sub zone. I cannot do that with CloudFlare though.

Agree on Cname flattening. It cause some issue for my email forward service in the past.

So we have customer use githb page and set CNAME on apex domain. Then they add a MX record for apex domain. CloudFlare UI allow them to do that. But upon resolving won't return MX records for the apex. So my customer aren't able to finish setup. Eventually we have to set the A Record on Apex to an IP.

kureikain··on Cloudflare's Disruption
Here is my use case: I have a static site to process form and referral. It used to run on AWS Lambda. I migrated them to Cloudflare workers. Deployment, code editing etc is much easier.

And no, it's fully act as a standalone app. I define the route to to route a part of traffic to the worker, other parts to our pages app.

For me, it works great and replace my aws lambda usage.

kureikain··on Cloudflare's Disruption
Cloudflare is truly amazing.

They almost compete with everyone now.

DNS: They eat simpledns lunch Pages: They eat Netlify lunch Worker: They eat serverless/lambda as in AWS/GCP lunch R2: They eat AWS Lunch

And finally

Email Forwarding: They eat ... my own lunch (I'm founder of hanami.run an email forwarding service)

That's being said, from a user perspective, if my domain is already on CloudFlare, I can just host everything on it.

Right now, cloudflare workers is pretty great to add some dynamic stuff. And pages is great for static site.

kureikain··on When users never use the features they asked for
So I want to share a story about user asking for a feature then not using it.

I run an email forwarding services(https://hanami.run) basically you add your domains in and add some records.

We had this one heavy users who has like hundreds of domains. So our UI isn't design for that. Who has hundreds of domains? So they approach and asked us for a way to organize those domains into a hierarchy structure.

All good.

They are paid our highest tier ($30 per month) so we prioritize the requests and work on it.

2 days later that same user downgrade to the lowest plan and delete all of their hundred of domains...

That complicated features remain unused to nowadays...

kureikain··on Proposal to Merge YJIT into Ruby
I'm still learn about JIT but what happen if we JIT everything as in every single line of a Ruby app? Will it be way faster? So we don't have to wait for the JIT to compile during production?
kureikain··on Easily creating and routing email addresses with Cloudflare Email Routing
Yes, I was confused as well because without rewriting SMTP MAIL FROM(or Return Path or Envelop) then SPF will definetely fail.

However, even if SPF failed, and DKIM is passed, it can still be trust worthy. Also, if the mail server support ARC(which gmail, for example, does) we can append our ARC so mail provider can look into it to investigate email forwarding chain.

← PreviousPage 3 of 17Next →