Hacker Newsnew | past | comments | ask | show | jobs | submit | sans_souse's commentslogin

I love it until fine I'll signup and love it again but then no you pay now. My 2 cents is all I have to give.

I hear you on the friction. I’m experimenting with the 'ink' limits right now, also the ink actually regenerates. I think I need to make it more obvious in the UI

I was definitely finding it fun, responsive etc. Started to do a Simpsons-esque tag in Boston but ran out of credit. Hope to see more leeway keep up the good work

Thanks! Just increased the free ink limit. Your strokes should regenerate, come finish that Simpsons tag!

Crazy TiL as I was reading up on Pynchon and found this commection. Any zodiac sleuths want a new candidate (or two)?


Not me looking for the Honda 2009 Models


I'll take the over, here.


To me; point #3 is the big one and it is in conflict with point #1


How so? Those two together is literally agile; not as I've seen it done, but as it's intended. Learn, iterate, repeat.


Sorry in advance if this comes off as hostile, that's not my intent. I am genuinely wondering: You're in the business of advertising? And you're upset that Google isn't your golden goose anymore?


Anyone able to print this via Android? When I tap 3-dots in chrome → share→print I am getting an error


Probably because Chrome is shit, it prints fine on Android with Firefox 146.


I dig your style, you sound like my inner monologue :D


Stay tuned I have a pretty cool project I plan on launching very soon. It takes the email alias to the next level, using them as meta tags to actually allow users to trace the source of shady data exchanges. I'm working on the guide and I'm hoping to actually start a community effort here to hold companies accountable for responsible use of PII


I'm interested. How does it differ from using:

name+service@gmail.com or service@myowndomain.com

...to figure out where the spam originated?


> service@myowndomain.com

Just be aware that this may be very confusing to customer support agents: https://news.ycombinator.com/item?id=32475178


FWIW, I have been using the companyname@mydomain.com auto-alias for many years now and I've never had it challenged nor rejected by a human or a machine.


I’ve also been doing it for quite a few years, and I think I had it rejected by a machine once, and I had it questioned by a human once.

I’ve had way more problems from systems that think TLDs are two or three characters (which has never been true).


Everybody knows name+something@ maps to name@ so it’s trivial for bad actors to strip the plus part and just spam you directly, losing the per-correspondent distinction.


Which is covered by GP's second suggestion. I add short random password-like strings to these aliases to thwart spammers who might be trying obvious aliases, turning e.g paypal@example.com into paypal.nsi873g@example.com


I probably didn’t explain myself well.

On Gmail foo+bar@gmail.com is an “alias” for foo@gmail.com. So if you give someone foo+randomstring@gmail.com hoping that will help you map random string to that particular sender, you’re fucked - because anyone who sees foo+randomstring@gmail.com knows it’s an alias for foo@gmail.com, they can just email that directly and bypass your cleverness.

If you’re using a sane alias provider like you described, then it’s likely not an issue.


In the latter specifically it doesn't differ except for the specific methodology and what we do with the results.


Direct Download link if anyone needs it is https://archive.org/download/insidececot/60minutesCECOTsegme...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: