Show HN: Kinda like posterous?
So after 2 days of coding, it's here and works. It's not pretty, but it's really neat & kinda addicting.
Anyone can email or text anything to _ _ _ _ _ _@inboxi.us and it immediately creates a public page and an email address. For example, say you wanted to create a page for coding errors called fmlcodesucks, you could just text or email it to fmlcodesucks@inboxi.us and it instantly posts your picture to that page and lets anyone contribute by sending pictures to fmlcodesuskcs@inboxi.us.
This is just an example and you can come up with any name you want, no account registration or any of that BS. Right now we only support pictures, but plan to support other stuff.Would love your feedback and see if you think there are any legs here to keep working on it.
39 comments
[ 3.7 ms ] story [ 102 ms ] threadFront page trending/newest links don't all work.
One more thing I wanted to find out about. How do you handle email signatures? When someone comments on a task in BaseCamp (via email) the entire email is posted to the thread, including their signature and whatever little images they included (photograph, or Facebook/Twitter icons). Is there anything you can do about that? Gmail seems to be pretty good at detecting the boilerplate part of a message -- possibly only after having seen one message from the user. This would be an important thing to nail.
Edit: What if you want to lock a page down so that only you or a select few may email updates? I would probably want that for at least one of the pages. Now that I'm thinking about it, the lack of registration is possibly due to how hard it would be to authenticate a user via easily-spoofed email. You might be able to come up with a sort of "secret key" that you add anywhere in the email but I could see that not working out for your average user.
As for handling spam, yes it is a challenge but something we plan on doing to prevent spam is sending automatic authentication links to accounts we believe are posting a high volume in a short period of time. The authentication link will lead them back to a page that requires them to fill out a different captcha for each link.
Finally with regards to signatures, there is definitely OER software that exists that we can test out handling signatures and images inside the email itself.
The authentication link is a good idea. They can still post non-automated messages (and automated messages if they find the right lib for breaking captchas) but at the very least it will give you a way to keep a close eye on suspicious activity. Someone starts triggering the captcha? Take a look at what they do.
[20:39:25] ESMTP> MAIL FROM:<my@address.com> SIZE=18028
[20:39:25] SMTP< 250 2.1.0 Ok
[20:39:25] SMTP> RCPT TO:<hello@inboxi.us>
[20:39:25] SMTP< 554 5.7.1 <hello@inboxi.us>: Relay access denied
error occurred on SMTP session
* Error occurred while sending the message:
554 5.7.1 <hello@inboxi.us>: Relay access denied
I assume these are coming.
2) Of the 8 trending/new items, only 2 are linked.
3) On @knobreak, there are 20 photos, but the top says 166.
4) What will you do when @childporn begins to trend?
5) You don't have a TOS, which is awesome, because I hate censorship. Can I assume that you will eventually install the standard one, which forbids pretty much everything, depending on interpretation at your sole discretion?
1. Interesting idea
2. We are rebuilding the home page, should have something far better soon.
3. What browser are you using? It's possible there is a bug, however on Firefox and Chrome latest editions there are 166 photos and 91 people.
4. To prevent porn from trending we will have community reporting features. I also believe we would handle this quite similar to how twitter, facebook, or flickr handle this.
5. We don't have a TOS because we threw the project up very quickly but plan on having one soon. Our TOS will aim to protect the greater good of the community.
4) That almost guarantees that I won't be using your service. Effectively having "Report this image for abuse." everywhere, is one of the most egregious enablers of today's online censorship. I don't expect you to solve this problem, but you should at least attempt something different.
5) What do my private pages have to do with the community? If you provide private pages, then only a subset of the TOS should apply to them.