Location: MA, USA
Remote: Yes
Willing to relocate: No
Technologies: Elixir / Phoeniex (PETAL), Ruby on Rails, microservices, APIs (GraphQL / OpenAPI), kubernetes, OAuth2
Résumé/CV: https://drive.google.com/file/d/1tDv2Dck66y-uIrmOobm3-fGWiJtLaZlj/view?usp=sharing
Email: yetanothersullivan AT gmail.com
Sr. Architect and Elixir developer with entrepreneurial experience. My startup idea wasn't successful, likely because I enjoy being a developer too much. I'm looking to join a team where my skills will be useful and I can continue to learn.
I think it was the book called Blitzscaling that talked about the fact that some kind of "unfair advantage" with regards to access to market should be built in to your product. They mentioned LinkedIn and their "import address book" feature
You can change your phone number though. What if you change it so frequently that it's no longer a key identifier? Why not have a system where you can receive phone calls without a phone number? I believe some of the solution here is to stop having globally unique identifiers.
Burner numbers are close, but if you use the same one for all your contacts it still becomes an identifier, even if you rotate it. An alternative is a proxy service where you get issued a unique pin for each person-to-person connection, so the same phone number gets used by multiple parties. Those both use the existing phone network in better ways. With a VoIP system you don't need numbers, you just don't want to trade them for usernames or some other global identifier. I implemented one approach with Severus, but I'm also looking for alternatives that increase privacy.
Disclaimer: I'm new to SEO so I might have done something wrong
I submitted a sitemap to Google Search Console and they indexed all my blog articles... except for the one about using Plausible instead of Google Analytics
How about an OAuth system where you can add conditions like, the user has validated an address in a certain town, or worked for a certain company? What part of the identity would you scope by?
OpenID, the original OpenID was built for bloggers: your blog address was your login. It mostly only ever verified that you were also (likely) a blogger and what that address was. It built a unique web of commenters who were also bloggers. It was something of a shining golden age of blog commenting when OpenID was just about everywhere.
OAuth and (shudder) "OpenID Connect" moved on to be nothing like that original OpenID and its vision. I think the death of the original OpenID is tied in part to the death of comment areas on blogs. It wasn't the only reason, but it was a factor in tide of them.
Hi HN,
I've been working on this website for far too long. There's still a long way to go, but I think it's at the MVP stage. It can be used to share contact data and have 1-1 chats. I'll be posting more blogs on the privacy model and technical details, but for now I'd appreciate any feedback. Thank you
Fine. I'm starting Severus, which actually deals with "contacts, business cards, email addresses", but with some interesting privacy mechanisms. I haven't quite launched yet, but I've seen this topic come up frequently on HN, and I never talk about it. I need to get out of my comfort zone and talk about it.
Okay, here you go. I have an amazing day job. But I always wanted to build some software utility that others found value in. So I shipped a forum platform. Because I can’t bring myself to share this with my friends and professionals network, it has no users: https://discoflip.com/
I deployed my company website / blog with fly.io
It's a simple phoenix app w/o a DB, and it was trivially easy to set up. After having used K8S for Rails and Phoenix hosting before, their product is definitely something to keep in mind.
