HN user

bismark

201 karma

[ my public key: https://keybase.io/bismark; my proof: https://keybase.io/bismark/sigs/lAMnQdw6dLzFSLASNL6LP3bPcpIcehXcvsq6VFsuuxc ]

Posts3
Comments23
View on HN

You can always create a personal Google account with your custom domain email address: still has access to everything except Gmail.

Grain | Senior Backend / Full-stack Engineer | Full-Time | REMOTE | https://grain.co

Grain is a fast-growing, well-funded startup building innovative tools for video communication. We are a fully remote team, spread across US and EU timezones.

Tech stack includes Elixir, React, Electron, AWS. Elixir experience strongly preferred, but we're also looking for folks with strong DevOps, Video, and/or ML experience.

More here: https://angel.co/company/grain-intelligence/jobs/495036-seni...

BTC -> GBP is surprisingly rare (GDAX doesn't support it). Even exchanges I've seen that appear to support it just allow you to do a EUR SEPA transfer, which for example Lloyds will charge you for...

I'd love it if Facebook and Twitter had a rolling deletion period option - everything more than six months old is shredded forever, as far as the service is concerned.

I really like this idea. The biggest benefit is that it stops people expecting these services to act like an archive. With the current system it's easy to think "Oh I can just look this photo up again on Facebook if I want to". Instead we should be treating these services as publishing platforms while we maintain separate archival versions of our data.

These are Erlang VM processes which are actually quite fast.

Re ugly: well, eye of the beholder I suppose.

I'm a happy Fastmail user but one thing I wish they would bring over from Gmail is SASL OAuth. I understand it's still in a draft extension but any improvement to the state of email authentication would be great (restricting read/write access based on IMAP folder on a token by token basis would be even better). The idea of handing out my email credentials in plain text to email SaaS products just gives me the willies.

We at spatch.co are strong believers in decentralized protocols. Email is currently the "best" we have for decentralized communication and collaboration. We are trying to change that by building a modern decentralized collaboration platform.

We don't have anything open source yet but we hope to start opening up code and specs to the community soon.

Our website is unfortunately out of date, it makes Spatch look like too much of an app (what's shown is a prototype we've built to show off some use cases). We will be updating it soon along with a jobs page.

We are well funded and hiring, based in London.

We are using Elixir to build the first server implementation of our new decentralized communication protocol.

Hit me up if that sounds interesting, we are looking to hire. Based in London/SF. ryan@spatch.co

There definitely are jobs though :)

My company is currently looking for Elixir/Erlang devs to help us build a new decentralized communication platform. Based in London/SF.

If you or anyone is interested, please ping me at ryan@spatch.co.

The wording is a bit ambiguous — “server-side email processing” refers to processing emails which are stored with an email provider, e.g. Gmail. IMAP is used to interact with the email providers because it is a mail retrieval protocol, and is widely used.

If we were doing “server-side email processing” of emails as they were sent, SMTP would have fit in.

I also find the combination of lambda and defaultdict quite useful:

  d = defaultdict(lambda: False)
or
  d = defaultdict(lambda: {'foo':set(), 'bar':False})
  d['baz']['foo'].add(1)