Earlier quoted context omitted.
This is how I feel too, it was surprising (and educational) to see some commenters having trouble accepting that someone might have just made a thing for fun. I think it's the fact that you can buy it that trips them up. I imagine Cards Against Humanity got a lot of the same comments.
A Man that steps aside from the World, and hath leisure to observe it without Interest or Design, thinks all Mankind as mad as they think him. – Halifax (1633-95)
IMGZ – Paid image sharing
351–360 of 409 posts
Re: IMGZ – Paid image sharing
#352Earlier quoted context omitted.
Is it free? Free image hosting always eventually shuts down or monetizes with redirects to an html page with your image and bunch of ads. Bandwidth isn't cheap enough for free image hosting to survive.
It is free. It has ads and accept donations. No compression. Online since 2006.
https://twitter.com/CubeUpload/status/1169580329683828736
Re: IMGZ – Paid image sharing
#353Re: IMGZ – Paid image sharing
#354Earlier quoted context omitted.
Out of curiosity, what do you use for email? I'm currently on Office365 but it's way overkill...
Tutanota. They’re a cooler company than Proton but due to the lack of a bright I can’t unconditionally recommend the service - you’re confined to the (web) app.
Re: IMGZ – Paid image sharing
#355I thought the comments to this were well above average on the entertaining scale. Pretty embarrassing, though, that probably the majority of comments seemed to take it seriously, even reprimanding the creator for not being serious enough, not taking his Business seriously enough. It seems to create dissonance among many that such a thing even exists. People seem deeply confused it's not full speed ahead, like every o…
This is how I feel too, it was surprising (and educational) to see some commenters having trouble accepting that someone might have just made a thing for fun. I think it's the fact that you can buy it that trips them up. I imagine Cards Against Humanity got a lot of the same comments.
Re: IMGZ – Paid image sharing
#356Earlier quoted context omitted.
This is how I feel too, it was surprising (and educational) to see some commenters having trouble accepting that someone might have just made a thing for fun. I think it's the fact that you can buy it that trips them up. I imagine Cards Against Humanity got a lot of the same comments.
The world needs more people like you.
Re: IMGZ – Paid image sharing
#357Earlier quoted context omitted.
Well that's extremely odd, I will look into that right now. EDIT: This is very odd, I'm not really doing any processing on the uploaded files, so it should definitely return the originals. I will have this fixed soon though. EDIT2: Unfortunately, the saved image in the DB itself is corrupt, so you will need to reupload after I solve this. EDIT3: Alright this should be fixed! Now I can start submitting animated GIFs t…
You said, no support. Why do you even care? F*k this guy. Delete his account. /s
Re: IMGZ – Paid image sharing
#358Earlier quoted context omitted.
I understand that postgres is pretty decent at storing large binary data though? I've been meaning to investigate trying storing images in postgres on a hobby web project where it could be convenient; I'd still want to make sure I was streaming bytes from postgres to the client, not loading the whole image into memory and only once fully loaded sending it to the client. Looking at the pg API's for my language/platfor…
> I understand that postgres is pretty decent at storing large binary data though? Storing large files in PostgreSQL is possible, but I would advise against it. PostgreSQL uses a technique called TOAST to store large objects. If you store something in a bytea column, it'll first be compressed (either deflate or a new algorithm that I forgot the name). Then it will be split into 8KB chunks (page size) and stored toget…
Size/speed of backups is a good point to consider.
Re: IMGZ – Paid image sharing
#359Earlier quoted context omitted.
I understand that postgres is pretty decent at storing large binary data though? I've been meaning to investigate trying storing images in postgres on a hobby web project where it could be convenient; I'd still want to make sure I was streaming bytes from postgres to the client, not loading the whole image into memory and only once fully loaded sending it to the client. Looking at the pg API's for my language/platfor…
Postgres is indeed good at that. I know from experience. If you want to commit ten things every second all week, don't transfer so much data in a single transaction that you hold any important locks for half a minute. And if you use replication, test while replicating. If the blobs you store are small enough to not disturb your commit rate, then pg's drawbacks are IMO smaller than those of the alternatives, particula…
So you've stored images in the db in production and had it work out fine?
I don't want to commit ten things a second. It would be a pretty read-heavy write-light load. Sounds like that would avoid one path of riskiness at least.