danger/u/
This thread is permanently archived
Image Hosting

| I like to take a shit ton of screenshots all day every single day and imgur is pretty shit and no way i'm making a account in that shit service. What image hosting service do you use g/u/rl? I'm considering joining a private/self-host a image hosting service


| My own VPS


| Why is imgur shit?


| What's wrong with imgur?


| >>413800
>>413825
Botnet


| Also, you have to enter the freaking site to visualize images, even if you click a "direct" link. I'd like some alternatives too.


| Yeah basically self host your shit, domain for like 10-15 a year, raspberry pi for 35, sd for 30-50 and run it at your house for pennies worth of electricity, or buy a vps if you're no fun


| >>413800
>>413825
Compresses your image like shit unless you register. mobile users are forced to deal with the website bullshit. they are literally trying to copy leddit and it's shit


| 0x0.st


| >>413859 this.

just set up a linux machine, either on a raspberry pi or a cheapass desktop from the pawn shop, rent a domain, do a little bit of pretty simple coding (codeacademy should teach you most of what you need to know to run an image server) and ask your isp to give you a static ip address.

Cost: $50-60 up front, then maybe 10 a year after that

programming skill: very, very little. I did all this in my junior year of high school during class because I was bored.


| >>414265
What if the server gets hacked because of the shit code tho


| >>414273 A good firewall goes a long way if you just scan the harddrive every day or so, and as for client side security, parsing and simple encryption is really easy if you set it up right. High school/hobby level code isnt too bad.

You probably wouldn't have to worry about hacking anyway since this type of setup isn't able to support a large number of users in the first place.

though ofc you don't want to keep sensitive info on a public image hosting site.


| >>414273 installing just Apache or nginx isn't going to give an easy way to get in, not impossible but you'd need a 0-day and those are expensive, you're more likely to get "hacked" by ssh than through a stock web server with no php or anything


| Basically all you need to do is run sudo apt-get update && sudo apt-get upgrade once a week and reboot if there is kernel changes


| The site doesn't even really need any coding, just need to edit a config file, and drop images in a folder, use something like samba for shared folders, and you should be good


| >>414482 it needs some sort of front end for the users.

and as for hacking, sql or php injections aren't easy if you parse stuff.


| >>414481
You don't really need to reboot for kernel upgrades since a few years ago afaik. The new kernel will replace the old one during the upgrade process and all programs started afterwards will use the new kernel while all currently running programs will still use the old one until you restart said programs.


| >>414848 I was unaware awesome

>>414690 really depends on how you set it up, don't need a front end for private use when it's on your same network and could just attach network storage then have your screenshot program save into it, just link the direct image


| Could use nextcloud if you wanted something though, simple no coding required


| >>414848
only if you use ksplice. I don't think that's turned on by default. You certantly can't load kernel modules for the new version without rebooting, that's for sure.

Total number of posts: 20, last modified on: Tue Jan 1 00:00:00 1538667388

This thread is permanently archived