Live data from Hacker News

Show HN: Tampon - an open source Buffer app

tamponapp.com

61–70 of 87 posts

Re: Show HN: Tampon - an open source Buffer app

#61

Earlier quoted context omitted.

I think it's more for people with a sense of humor More accurately: "for tone-deaf people with a seventh-grade sense of humor"

"seventh-grade sense of humor" Even if this would be the case: is this a bad thing? Why so serious?

A seventh-grade sense of humor is fine, when you're in seventh grade. I'm not ashamed to say I'm more sophisticated than that.

If you want me to make me laugh OR take you at all seriously, you're going to have to step up your game. I love humor and levity. Github and Zappos are both great examples of companies that don't take themselves too seriously without being juvenile.

Re: Show HN: Tampon - an open source Buffer app

#62

Terrible name, you should definitely change it. It might get you attention and have some shock value at the start but it's going to look stupid eventually (if it doesn't already). Same goes for the logo. I understand it's 'buffer' in French but major companies go out of their way to ensure their product name translates well in the major languages. You should too. Apart from that, it seems like a good product. EDIT: A…

As stated some place else: it's an open source project, so let's just have fun with names! :)

Naming is hard, and I appreciate the desire to have fun with a name. It's pretty clear from the responses that this particular joke doesn't work.

Looking past the name, it looks like a well-constructed useful app and you should be proud of it.

Re: Show HN: Tampon - an open source Buffer app

#63
post #51

Earlier quoted context omitted.

As stated some place else: it's an open source project, so let's just have fun with names! :)

You have a right to name it what you want. If you have goals related to other people using, forking, improving, etc, then this name will make that harder. For example, in Showing to HN, you probably wanted some frank feedback. Your name is working against that as all you are getting is discussion of the name. If that's what you wanted -- well, mission accomplished.

As a meta-comment, the obvious should be pointed out: by creating shock value, the name creates discussions, which create upvotes, which drives more traffic to the post hence leads to more feedback.

Call it "growth hacking" if you want, but the name is quite smart in that respect.

Re: Show HN: Tampon - an open source Buffer app

#64
post #12

Earlier quoted context omitted.

40 or so lines? I'm sorry, what? https://github.com/julien-c/Tampon/tree/master/api Also, I don't think this counts as security: if (strlen($id) == 24) { // Looks like a valid MongoId Edit: this looks bad too: $post = json_decode(file_get_contents('php://input'), true);

Wait... why would it be bad?

NoSQL injection ? If such a thing exists ?

Re: Show HN: Tampon - an open source Buffer app

#65

Earlier quoted context omitted.

I wouldn't have batted an eye if it were called Jock Strap or something inherently male in nature Really? I would totally cringe at something called "Jock Strap" or "scrotum" or "foreskin". Tampon isn't just a feminine word like "flower" or "butterfly", it's biological and personal . "Anal Probe" is gender-neutral neutral term that also feels inappropriate because of its personal and biological nature.

Am I the only one that checked to see if analprobe.com was registered?

I wouldn't bother, but if you're willing to use two-letter country code domains, you might be able to get http://analprob.es

Re: Show HN: Tampon - an open source Buffer app

#66
post #35

Earlier quoted context omitted.

There is nothing wrong with either of those two lines of code provided that they are not the only layers of security. Checking to see if an ID is of the right length is a good way to filter out miss formated ID's early. And the JSON decoding statement is a pretty standard way to get the JSON body out of the request and into an associative array. Of course you will need to validate that it has the right format now, pr…

Looks to me like they just insert the JSON body directly into Mongo without any sort of further validation: $m->tampon->queue->insert($post);

Ooh yeah that isn't very good. They should really be using a JSON schema validation library to verify that someone isn't storing extra fields in the database, and that all the fields are of the right format and type.

Re: Show HN: Tampon - an open source Buffer app

#67
post #35

Earlier quoted context omitted.

Looks to me like they just insert the JSON body directly into Mongo without any sort of further validation: $m->tampon->queue->insert($post);

Ooh yeah that isn't very good. They should really be using a JSON schema validation library to verify that someone isn't storing extra fields in the database, and that all the fields are of the right format and type.

You're right. But the worst thing that can happen is someone POSTs large fake objects and tries to flood my server's hard drive. Which, given the max size of a POST's data will take quite some time :)

The API only allows querying posts on the current user (with now user input) so there's no risk of "NoSQL injection": https://github.com/julien-c/Tampon/blob/master/api/posts.php

Re: Show HN: Tampon - an open source Buffer app

#68

Earlier quoted context omitted.

Ooh yeah that isn't very good. They should really be using a JSON schema validation library to verify that someone isn't storing extra fields in the database, and that all the fields are of the right format and type.

You're right. But the worst thing that can happen is someone POSTs large fake objects and tries to flood my server's hard drive. Which, given the max size of a POST's data will take quite some time :) The API only allows querying posts on the current user (with now user input) so there's no risk of "NoSQL injection": https://github.com/julien-c/Tampon/blob/master/api/posts.php

I see. I would still recommend JSON schema, though. It is great for debugging and ideal if you plan to open the API up to third party developers, because it makes it easy to ensure that all NoSQL data adheres to a proper schema, and it also provides meaningful error messages if a third party developer accidentally sends badly structured JSON to your service, or even if you accidentally send badly structured JSON to your service due to a front end bug.

I use this JSON Schema validator with great success: http://packagist.org/packages/hasbridge/json-schema-validato...

Re: Show HN: Tampon - an open source Buffer app

#69
post #63
post #51

Earlier quoted context omitted.

You have a right to name it what you want. If you have goals related to other people using, forking, improving, etc, then this name will make that harder. For example, in Showing to HN, you probably wanted some frank feedback. Your name is working against that as all you are getting is discussion of the name. If that's what you wanted -- well, mission accomplished.

As a meta-comment, the obvious should be pointed out: by creating shock value, the name creates discussions, which create upvotes, which drives more traffic to the post hence leads to more feedback. Call it "growth hacking" if you want, but the name is quite smart in that respect.

I only see evidence of one kind of feedback, which, I hope, was expected, so it's not very useful.

It's not growth hacking if you don't grow something you care about (e.g. users not "naming" discussions).

Re: Show HN: Tampon - an open source Buffer app

#70
post #55
post #41

What is sad is the fact that this is a pretty useful app, yet most of the discussion is about the name. I would like to see more discussion about the app itself, but that could be just me.

Sure, it's useful -- in fact, I really need to schedule tweets, but have been procrastinating in finding one. This post made me do the 3 second google search and I chose http://twuffer.com -- not a great name, but free, easy and has the features I need. There are a ton of products (free and commercial) that do this -- but only one had a name that made me not even want to find out if it would be useful to me. No comme…

Thanks for the link, I haven't really looked into it too much, I appreciate you sharing your findings.
Post reply on HN