Working on https://ireact.to/, basically a centralized link in bio to collect feedback, questions, urls, ideas from your community.
Saturated market riddled with alternatives, but I wasn't really able to find low friction way to collect these things that met all my needs. Most of this stuff gets lost in DMs or comment sections, which just wasnt working for me.
Also figured it would be a neat way to re-think paying for a creators attention. IE, giving the option to tip (and soon subscribe to a VIP inbox of sorts).
One possible option I have seen is to reverse the flow. Give people a code and have them email you that code to a dedicated MX end-point using a dedicated inbound-only email domain that only processes codes, discards attachments, discarding anything else beyond a string+16 digit code and does not send bounces also block outbound connections from this thing. Invalidate and prune the code after an hour or less to keep the clutter out of Redis or your DB in the event of bot-flooding-signups. Format the code in a way that cell phone users can easily copy/paste into email or perhaps use javascript for that.
id try using a captcha, not perfect but they might give up...also worth trying control the ip where those requests come from: duplicates would be suspicious, triplicates or more worth human attention
I would of thought these 'spammers' would of given up because of verification, but it seems to continue despite many of accounts not being verified yet, perhaps they think they can verify later (which makes me think a TTL on verification emails is important) or that was an oversight completely on their end.
Had a conversation about this (podcast) and was looking to get some perspective from other indie creators / founders. The article I linked is just a boiled down TLDR from a 1 hour conversation.
This is a really casual Material Science book. It's sub-title is "Exploring the marvelous materials that shape our man-made world." I am about a quarter of the way through and am really enjoying it. I really knew nothing about materials, this book served as a fun/interesting introduction to modern materials. The first chapter (my favorite thus far) was about metals. It goes into how different types of alloys are created and into sword making; what makes a good blade vs a brittle blade that will fall apart in combat(hint: it has to do with the amount of carbon in the blade. Too much and it is brittle. You want about 1% in the entire blade.)
Interestingly enough, I had a problem with ChartJS that no one seemed to be able to remedy. It was quite bizarre and at first seemed to be a cross browser issue, but after further investigation it seemed to just be some type of strange cross-machine issue. See it here http://stackoverflow.com/questions/30063762/side-effects-fro...
Given that, I had to do some hacky stuff upon every refresh. Instead of using destroy() on the canvas, I had to remove the Canvas DOM object itself, building it back up, and inserting it again. Because of this I am a bit skeptical about using ChartJS again, which is unfortunate because I do love their Charts. I feel like maybe SVG might be the better way to go for analytics.
hey nirkalimi, I'm one of the maintainers of Chart.js. I know of a previous issue where the behaviour you described occurred on devices with window.devicePixelRatio greater than 1. Your JS fiddle didn't reproduce on my machine and it appears to use v1.0.1 which was the version that fixed the bug with devicePixelRatio. Calling destroy() on the chart object should be enough to reset the canvas to it's original state. If you'd like, file an issue on github and I can have a more detailed look.
Saturated market riddled with alternatives, but I wasn't really able to find low friction way to collect these things that met all my needs. Most of this stuff gets lost in DMs or comment sections, which just wasnt working for me.
Also figured it would be a neat way to re-think paying for a creators attention. IE, giving the option to tip (and soon subscribe to a VIP inbox of sorts).