3 ms·
I’ve wanted to do the same kind of thing. My business partner who handles the backend, and may be more sensible than me, suggests not wasting my time. Hanging o
by dahart 8y ago
I’ve wanted to do the same kind of thing. My business partner who handles the backend, and may be more sensible than me, suggests not wasting my time. Hanging onto the socket is potentially DOSing yourself. You could have a server for it, but it’s a server you could be using for other things. In the bigger picture, spending time on this is a form of DOSing yourself. You could be working on features or customer service or spending time away from work or, perhaps, implementing two factor auth for customers, if you don’t already have it. As much fun as it still sounds to me, I think my co-founder’s advice is best: do make sure you’re locked down but don’t try to get them back, since it’s time & resource consuming, and not very likely to work anyway.
- amelius 8y agoBut if everybody did something like this, it could make a difference. Maybe we could use a library/service specifically designed for this purpose. It could keep itself up to date, and other than setting it up, you wouldn't need to spend time on it.
- beart 8y agoBlue Frog tried something like this over a decade ago. https://en.wikipedia.org/wiki/Blue_Frog https://en.wikipedia.org/wiki/Blue_Frog It didn't work out so well.
- spc476 8y agoYears and years ago I ran a tar pit [1], and it could handle a tremendous amount of connections with very little overhead. This could be easily done with a 301 redirect to such a system. [1] http://labrea.sourceforge.net/labrea-info.html http://labrea.sourceforge.net/labrea-info.html