Topic: bittit - Sell your pictures for Bitcoins - page 3. (Read 14621 times)

Yeah blockexplorer. My own client would definitely be more efficient but my VPS can't handle it... :-/ I have about 175MB left to spare and that isn't enough for bitcoin unfortunately... Deslok had a nice idea that could bring the time down to 3 minutes +1 block time if it works. I could check every 3 minutes the block count and only scan for new payments when it changes. But AFAIK the block count updates faster than the addressreceived API stuff. So checking the addresses right after tha block count changed could yeild no results in some cases. Another idea is to examine every single block and add up the received bitcoins to known addresses. That would scale perfectly even if the site get's really big, its completelly non-abusive for blockexplorer but needs a good coding to make sure I don't miss any payments... In fact the handling for blockchain merges could be a bit tricky... Quite tricky actually... We'll see. First thing will be to let the uploader choose how many blocks he wants to wait for.

No need to read this if you are not interested in our quarrel:
I don't get offended but I found your comments ignorant and accusing. You said that I sale pictures on behalf of others while I don't. You suggested I should make the ToS less protective for me and at the same time open holes for doublespending. That would make me open to getting sued in case someone doublespends, is that your opinion? Your first message ("BTW you can test your setup. How about that? Stitch your own big picture and set your limits accordingly instead of letting people find out their picture ends up public domain without getting any BTC.") sounded pretty sarcastic to me, like I was your employee and I had to test everything so that you are happy with it. You can suggest whatever you want, but don't be sarcastic to me if you expect me to stay calm. And I am not a pro. I made a site that I liked and I really don't care if I don't make money from it although I think it's worth it.

As for the spam problem. I scan pictures with tineye and google. That helps me to rule out lots of pictures. If you manage to find unindexed pictures that don't have a website logo and upload them then the DMCA will protect me AFAIK. I host pictures that users upload so if one infringes their copyrights they can report it using the procedure described by DMCA laws and not sue me. And specifically for the nsfw section most pictures would require validation before getting approved (as described in the help section). If I have problems with Tor, I will block it.

I don't like when people react offended when they asked for opinion and there is the slightest chance the "offence" might not have been meant to be one. Actually a pro would not even react offended when he actually was. But to be honest, your service made me think a lot and I don't mind sharing my thoughts no matter what you think of it:
I guess you would need to require the poster of content to register as there is so much content you can find for resale that you will have a hard time blocking all this with tools like tineye. How would you prevent me from paying 9$ membership at some random porn site and upload all the HD content to your site for 10cBTC each? I can automate it and upload through tor. You get top content and people would visit your page but you will never get away once the random porn site sues you over sharing hundreds of their pictures.
Same with the non-porn section. You can find thousands of pictures in members only sections that can be uploaded automatically and you don't care about the source? Courageous I would say.

no need to shout at me
bitcoinexplorer? Do you mean blockexplorer? Normally it should be way more efficient to use a bitcoin client directly for that.

I DO NOT receive payments on behalf of anyone. The payments go directly to the seller. I just monitor the bitcoin network to see when the payment happens. And the delays are mostly because of the bitcoin network and I can do nothing to make it faster so get over it and read the help and ToS or don't use it. And no, I won't accept by default transactions before they are included in a valid block because no matter what my ToS says I don't want someone to loose let's say 20BTC in a double spend attack. The ToS is there to protect my ass and not to allow me to mess up with my users. I might make it a parameter though for the seller to choose the protection level he wants but still there will be a 0-10 minutes delay before I check the address on bitcoinexplorer.

I will add "and wait 30 minutes" to the instructions on the front page.

Stating that something is unacceptable is not necessarily aggressive. I evaluated your service and told you my result. I assume it will not be within the users expectations no matter what you write in any corner of your page. The main thing I see when I get to http://bittit.info/ is "To increase the resolution of this image send any amount of Bitcoins to its address."
Now you are selling content on behalf of (anonymous) users. These users will be after the money when they see the content got displayed in full resolution on your page. Some might even consider suing you over the missing payment in case they did not receive the money by the time the picture reached 100% but ToS5 even covers this. But change your perspective to the customer's side. These guys know bitcoin. When they pay a beer with bitcoin and their counterpart sees the transaction, they consider it done. They will not accept to wait for confirmations for a payment of 1BTC. You should definitely take this non-existant risk and show the content as soon as the transaction is visible on the network. At least for payments <10$. Anything beyond one confirmation is total overkill for payments <1000$. Especially when it is about buying things into the public domain, you will not deal with people running a big scale double spend attack, don't you think so? Where would they get their benefit out of that?

If it didn't work it wouldn't show a picture at all. But even if it just couldn't resize it and instead displayed it at full size, I would notice that during the approval phase... I will do some testing when I can though. I've got lots of things to test and add to it and no time to do them. Plus the other guy that wrote some of the code has got even less free time (it's the exam period).


It says in the help that it will take up to 30 minutes. If it took longer than that then there is probably a bug.
If it took less than 30 minutes then how do you define "acceptable"? I could wait for 6 blocks (since that is what is generally considered safe) which is more than an hour, and you think 30 min are unacceptable for you to wait to get a picture?

The cron job that checks bitcoinexplorer runs every ten minutes. Anything faster than that sounds a little abusing to me and I don't have the option to run my own bitcoin explorer.

Also why are you aggressive? It's a free to use service if you haven't noticed so if it makes you that angry just don't use it or politely ask me to fix it and be patient.

[EDIT] It can handle pictures up to 5000 x 5000. (at least)

Tried out your service and the delay is unacceptable. Not only do I not get full resolution pictures instantly after paying, I don't even get it after the transaction shows up in blockexplorer.

BTW you can test your setup. How about that? Stitch your own big picture and set your limits accordingly instead of letting people find out their picture ends up public domain without getting any BTC.

I was thinking about high quality scans of paintings. Maybe they could get decent prices.

Wow that is HUGE! I will increase the max upload size. Try again in 30 minutes form now. BTW the castle photo is amazing...

[EDIT] I changed my php.ini. I hope I changed the correct one cause I had like 4 of them... one for cgi one for cli etc... If it still errors drop me a pm or an email (email is on the site). BTW I don't know if the resizer can handle that big pictures. We'll see...

http://images.icanhascheezburger.com/completestore/2009/3/31/128829619717840668.jpg

I just uploaded a pretty awesome panoramic photo of the Neuschwanstein Castle that I took in Germany.  I also have an amazingly high quality panoramic photo of South Lake Tahoe taken from the Heavenly Lookout, but it is 30MB and it keeps erroring out in the upload.  Any suggestions?

Well you ain't reading it the first time so you are taken back to the SFW section. I think it will be obvious that you don't see the NSFW because of the choices you made in the last 3 seconds so you'll get it right the second time when you will have to read what the dialog says.

I might put a whole page asking the user for confirmation but I ain't doing that now. :-) (also the confirmation box is much faster)

Yes, that is exactly what I am talking about. The only time I ever see them is some popup after I try to x out of it, so I wont click it. I'm not sure whats to understand. Maybe my aversion to websites generating dialogue boxes doesn't make technical sense?

New stuff:
1. Configurable initial resolution
2. Made a logo, sort of.
3. "Premium" codes for automatic approval are available.

I don't understand. What dialog box? I thought you meant the javascript confirmation box for the NSFW section.

The only time you really see them used are click-jacking attempts.

And here is a subreddit for bug reports, suggestions etc... bittit.reddit.com

Why would someone email her to tell her she isn't their type?  I just close it and move on if I don't like it.  Not like telling her that will do any good either. 

Just added direct links to photos, hotlinks, link to uploader pages.

To create an uploader page just use the same uploader ID (which should not be forgotten or shared with other people) during the upload process. This will put a link under each of you photos that will take visitors to see all your photos (all photos that use the same uploader ID that is...). You can use this to create albums or whatever.

Why not?