onassar

Hi all - This is a proof-of-concept I built. When you make a call to this API, it will keep track of the URL you pass in, and then request _that_ URL after a time delay.

For example, if a user signs up to your app, and you want to email them 24 hours later through your own server (instead of using a MailChimp of Campaign Monitor drip), you can simply make a call to the following URL:

https://aws-api.416.io/boomerang/v1/track/in-24-hours/https:...

24 hours later (the "in-24-hours" part), a request will be made to https://your-url-here.com/.

I find crons frustrating (for various reasons), and not ideal in certain situations. I built this some time ago and use it in production environments. I wanted to share it here incase others found it useful :)

Thanks for clarifying. I think there are better ways to ask a question like that (eg. "what differentiates x from y.."). It's also built on an assumption: looking at those two sites side by side, there's nothing glaringly obvious that one is "much better designed" than the other.

One thing I try to remember is that this site is probably something someone loves and takes pride in. It's fine to offer a critique and constructive crits, but I try to remember that a sharp comment like that (without much seemingly obvious interest in an answer) can be super tough for the designer.

Jeez you created an account just to throw shade on this site? Come on..

Really gr8. Clever idea :)

Looks like a cool service :)

;)

Could be seen as ironic, but I frame it more in the light of being critical of something, yet also understanding the value it can bring.

I may be critical of industrial farming, large corporate environmental policies and/or Facebook, but I still might buy corn, own a Toyota and use Facebook to keep up with friends overseas.

I think it can be super hard to take an ideological position at the expense of functionality (obviously depends on how strongly you hold your views, and what the cost of forgoing engagement with that company/person is).

Hey! Very possible; would need an API source for that data though :(

Yep very possible. Decided to make it an extension for now tho

Hi all -

Pigeon is a Chrome extension I built that allows you to get the contact info about your elected officials right from within Gmail.

I wanted a quick-and-easy way to click a button, see my official, and then click to open a new compose window.

I use two different APIs (one for American, one for Canadian) to access elected official data, based on your location.

Happy to answer any questions :)

Hi @nikolay

Feel free to email me: oliver@zenlogin.co

Happy to try and work something out for a non-profit :)

Thanks! Def reach out when you do. Happy to help with any questions or integration :)

Hi HN -

My partner and I just launched Zenlogin. It's a super-straightforward security API that you can integrate into your login flow, whereby if/when we detect a suspicious login (via things like IP and User Agent), we'll send off an email to notify that user of the login action.

While we were building out this security functionality for another app, we realized it's pretty tricky to get right. We had consider VPNs, Bots, dynamic IP addresses, etc.

A simple use-case is: a user logs into your app from Toronto, and then a few hours later logs in via Atlanta. In that case, we'll send off a (v nice looking) email that includes a Google Map and details on the login. Something like:

https://zenlogin.co/preview

Happy to answer any questions :)

Also: https://iconduck.com/search?query=duck

They've got a gr8 collection of ducks

Yep that all makes sense. I'm sure it's a tough job. For some context, our front end manages just 7 different libraries, but it's a pain to deal with so many edge cases. The worst and trickiest one was definitely ad blocking. We deal with a lot of edge cases whereby we're loading external resources that are not ads, but depending on browser/extension settings, were getting blocked.

This would naturally cause bugs due to our assumptions. So centralizing this logic, I think, could have a direct correlation to revenue.

eg. Stripe JS getting blocked, without us realizing it was for a small % of users.

Dope idea! Over 7-years, our third-party vendors/services architecture has gotten really complex, and was rebuilt multiple times. It's hard to get right, especially when considering versioning, ad blockers, conditional loading, etc.

For me, this is the kind of "Duhhhh, why didn't I think of that?" idea. I'm sure a challenge will be getting buy-in early enough, since more established code-bases won't make a switch like this casually. But if you're able to prove the value (like Segment) to early-stage products, I'm sure the stickiness and LTV will be super-duper high.

Congrats! Really great idea!

I think I'd reply to this with a "yes and no" kinda thing. For us, maintaining anything requires time and $$. This is, in part, because technology changes. Even in a vacuum with no new active development, money and $$ is required to ensure everything stays up and running.

eg. as our use base has grown, so too has our database. And so while the optics of it from the end-user POV is that the product has remain unchanged, we've had to invest in database and scaling services in order to continue to meet the initial offerings.

It's not as simple as that, but you probably get the gist of it.

A more relevant example might be a web service that emails you once a week. If the mailing service that powers this requires DNS or integration changes to help fight spam, over time that will require time (and perhaps $$).

If I'm misunderstanding your point, let me know :)

I generally agree. We've always taken the "grand-fathering" approach, but it can get a bit more complicated as your product and offerings grow. If someone was paying $XX /mo for your initial offering, and a few years later, you're able to provide a number of new features within that product, I don't think you necessarily need to continue providing those extra features simply because someone signed up earlier.

To your point, you may face a backlash. But it also costs a lot of time and $$ to support new development and features. Therefore, having some backlash may still be the right decision in the medium/long term. Can be hard to weather that storm initially, though.

Haha wow I love that idea. The first thing that comes up is that back in the day, I was taught git concepts and commands by a few different people, but it wouldn't "stick". But then I met this one engineer, and his teaching approach worked _super_ well for me.

So I like the idea that a bunch of different people could teach the same material, and you could be the platform to help people discover it.

Off the top of my head, here are some things I'd love help with (sorry if it's too specific haha):

- imagemagick CLI concepts

- Better understanding bash

- Better understanding different types of joins in sql (15 years later, I still can't grock that)

Thanks for the reply and stats! Yeh I actually just got off a call with a couple people I met because of that post, so that's always fun and different :)

Any plans to make something similar to vim.so but for different platforms?

(this didn't fit into the original post due to character-limits)

- 22 different favicon/icon file requests. I thought this one was funny. There were 22 different unique favicon/icon requests, which I presume speaks to the wide variety of devices and operating systems out there. For example, the standard favicon.ico, but then also so many different variations of files like: apple-touch-icon-57x57.png, apple-touch-icon-114x114.png, touch-icon-iphone.png, apple-touch-icon-72x72-precomposed.png

- 3 different bot scripts kicking in. I noticed a ton of requests within a few hours that were scraping the site

Obviously the context around the submission is key to the stats and descriptions above (eg. time of day, period of week, what other submissions there were, how widely the submission appeals to the HN audience, etc), but I thought it may be useful to read a follow up on what a front-page position led to.

If anyone has any questions on other stats, let me know and I’ll do my best to get them. Thanks for reading, and for the enjoyable (and panicky) Friday & Saturday

Hahahah v good point. I'll see what I can do about that ;)

Thanks for the context and background. I believe one of the founders has commented in this thread, so I'll let them respond directly to that feedback.

I think you're right, though, regarding side-stepping things. I'd really love for this to be a long term OSS project that could pull in a bunch of developers and designers. I don't mind contributing my time and some hardware to help w/ the problem.

Thanks for the context. I assume the original question was meant theoretically. My response in based, in part, on the fact that I really love Noun Project. They're an amazing company, have a great product, and have some phenomenal support. We've (a different product) been a customer of their API for 5+ years now.

I remember reading a little while ago about scraping and what is/isn't allowed. I find the legal/theory of it pretty interesting, but also irrelevant for Iconduck: I like icons and want to spend time bringing together as many open source ones as I can, while practicing some of my design skills.

Appreciate you checking is out. Flaticon is a gr8 product.

Yep that's a good idea. I do some internal tagging when something is a brand logo, so I could use that data to put a little notice in the Preview modal that it's likely trademarked :)

Whoops I intro'd a bug a few minutes earlier. Should be fixed now. If still happening, do a hard refresh and it'll work again :)

Could you email me: onassar@gmail.com Want to try and debug the issue with you

Yep I got it!

Thanks. Send any feedback my way: onassar@gmail.com :)

Haha fair enough. I like ducks, and thought it was a memorable name that had the domain available :)