Evil Post
Pages: 12
My current post number is 666. I've spent a good portion of my day working on the "clean" part of my cleanchat iPhone app. I don't often swear (read never) and I had to come up with a list of words to block. I felt quite uncomfortable with the whole process, and I thought that the 666 thing was an interesting addition =]
moving on
On another note, I suppose that several members of this forum are uncomfortable downloading straight executables, and I'm wondering, how could I improve your trust, should I make a website?
Add the projects to a big download site, like Cnet?
Do you want me to make a video showing every part of the source and how it's not malicious?
Would you rather take the time to compile the project yourself?
How can I gain the trust of end users?
moving on
On another note, I suppose that several members of this forum are uncomfortable downloading straight executables, and I'm wondering, how could I improve your trust, should I make a website?
Add the projects to a big download site, like Cnet?
Do you want me to make a video showing every part of the source and how it's not malicious?
Would you rather take the time to compile the project yourself?
How can I gain the trust of end users?
Last edited on
Best way to gain trust is through building reputation. (imo) word of mouth spreads your reputation quickly so the more popular your software becomes among users, the quicker it will advance in popularity, and the more trust (credibility) you will have as a developer.
+1 to post of Sera.
Open source is another option.
But I do trust you so I'd like to try it. How?
Open source is another option.
But I do trust you so I'd like to try it. How?
Last edited on
You could use this: http://www.noswearing.com/index.php (NSFW warning).
Last edited on
closed account (3hM2Nwbp)
Like above, trust builds with reputation. Building from source would probably scare away a bunch of potential test subjects end users (in my case, learning how to work my compiler(s) was 10x harder than learning C++ was!) A website / blog would probably help as well.
You could include the source in the program, but put the precompiled binaries in the parent directory (or in a separate "bin" directory, though they might not know to look in there, whereas if the binaries are in the parent directory then it is much more obvious that those are the files to run).
@darkest: I'm totally cool with making my projects open source, most of them at least.. I'll consider that.
@Blackcoder && xander Thank you! I'll set up a blog tomorrow, and post all my projects there from now on. I'll drop a link in this thread.
@seraphimsan: I agree completely, I'm just having a somewhat difficult time building the initial reputation.
@chrisname: haha I emailed 'em yesterday!
@Luc: blog idea +1. I agree on building from source, I still have problems because of all of the different compilers and libraries.
On another note. My "blacklist" is completely done. I've come up with several PR ideas, and I'm really really excited!!! My server needs to be configured with my asynchronous partner server, and once that's done I can't think of anything that I need to add to the app!
@Blackcoder && xander Thank you! I'll set up a blog tomorrow, and post all my projects there from now on. I'll drop a link in this thread.
@seraphimsan: I agree completely, I'm just having a somewhat difficult time building the initial reputation.
@chrisname: haha I emailed 'em yesterday!
@Luc: blog idea +1. I agree on building from source, I still have problems because of all of the different compilers and libraries.
On another note. My "blacklist" is completely done. I've come up with several PR ideas, and I'm really really excited!!! My server needs to be configured with my asynchronous partner server, and once that's done I can't think of anything that I need to add to the app!
Have you made it possible to disable the blocklist? Obviously that's impractical if the blocking is done before the text reaches the receiving client (if its done by the sending client or the server) but otherwise, as a die-hard libertarian, I personally wouldn't use something that blocked words if I couldn't disable it.
The possibility exists. Users can add and remove any words they want. My general thought is that anyone who uses the application will want to be in a community of like minded individuals, with similar desires for speech cleanliness. The server filters nothing, it's almost pure port forwarding.
I am rating the application 17+ so I don't run into trouble with children trying to use it and the inevitability of people bypassing the filter. It's going to happen, and I'm making plans for it.
I am rating the application 17+ so I don't run into trouble with children trying to use it and the inevitability of people bypassing the filter. It's going to happen, and I'm making plans for it.
| I am rating the application 17+ so I don't run into trouble with children trying to use it and the inevitability of people bypassing the filter. It's going to happen, and I'm making plans for it. |
Hmm... I think 17+ is a bit extreme. I'm 17, but I've had to deal with excessive swearing at school since around about 14. I think a 17+ rating might also send an unwanted message.
Edit: 14 is just a guess, it could have been a little later, or a lot earlier.
Last edited on
Which client does the filtering? The sender or the receiver? If it's the sender then you won't be able to bypass the filter for incoming words (though you could use something like libpcap to capture all its incoming packets and then reverse the blocklist or something), only outgoing words, and vice versa.
I think the first time I swore in school was when I was 10, but that was a genuine slip-of-the-tongue.
I think the first time I swore in school was when I was 10, but that was a genuine slip-of-the-tongue.
The receiver does the filtering, it's a very simple method, and it won't find the words in the middle of letters, however anything else will work, now I'm working on wildcards (pretty simple, just need to implement it)
Well 17+ doesn't mean no one under 17 can buy it, it just means that I recommend that age group. I can guarantee that people will sit around attempting to send nasty stuff to people... Luckily I am stripping all calls to img html so no one can send pictures (unless users start complaining that they want it)
Well 17+ doesn't mean no one under 17 can buy it, it just means that I recommend that age group. I can guarantee that people will sit around attempting to send nasty stuff to people... Luckily I am stripping all calls to img html so no one can send pictures (unless users start complaining that they want it)
Working on it!! Sorrry! I've been nasty busy!! On that note, does anyone have a recommended hosting site? blogspot, wordpress?
Oh wordpress.com
It's a much more serious environment than blogspot (aka a day in the life of a mom).
It's a much more serious environment than blogspot (aka a day in the life of a mom).
Well serious environment, I don't really care. I'm wondering about features. Like max number of clients, bandwidth limits, etc. I'll more than likely just end up hosting it on my server.
Alright, got a blog! Posted my first post! Follow me =) Comment! Do stuff!
http://ultifinitus.blogspot.com/
http://ultifinitus.blogspot.com/
Pages: 12