Services like Facebook, Instagram, Google Photos, iCloud Photo Sharing, Flickr, SmugMug, 500px, and more are available for hosting and sharing photos online. I'm curious what service, or set of services, you you use and how you decided. Do you cross post between them, and if so what strategy do you use?

I'm currently spread a bit and without much cross-posting between Facebook, Instagram, and Flickr. Not a strong conscious decision, though I've been wanting to do a bit more photography and would like to figure out a better strategy.

I think some key points to consider are cost (free vs pro, ease of upgrade/downgrade), storage space and restrictions (total space, max individual size, filetypes, enforced resizing/compression), ease and control of sharing publicly or privately, network audience and reach, and creative rights (who owns what rights on the content)

This Terms of Service; Didn't Read site can be helpful for at least determining what the general rights on these services are with some broad judgement.

Does anyone have a business subscriber Internet connection? Is it worth it?

I just spoke with my ISP, and for an extra $40/mo I can get a static IP address with 100mbps that I can host my own website on. I have a virtualization server, and I've been thinking about hosting my own hobby-scale website for a while. I haven't had any luck finding rack hosting space that I'd feel comfortable using so I'm thinking about just going rogue, and operating solo. If I had a static IP address with a pipe that would allow me to host then all I'd need to do is stand up a server, register a domain, and point it at my IP address.

Other than the typical security risks, what do I need to worry about? Would the experience be worth it?

I have been looking for some software where I can brain dump all the things I need to remember on a constant basis so I can easily find it again in the future. A personal wiki basically. I am wondering what any of you tilderians are using?

The things I am looking for:

Absolute requirements:

• Open Source: I want to be in control of the data myself, and I want to be able to hack on it myself as the need arises.
• Self Hostable: Goes hand-in-hand with with open sourceness, I want the data to live on the server in my apartment, under my own control.
• An API of some sort so I can programmatically add/read/modify data.

Nice to haves:

• Revision history of some sort.
• Common/simple data format for easy backup and longevity.
• Web interface, with mobile compatibility.
• Lightweight as possible, so I can run it on a low powered server.

Does anything know anything like that?

Options I have heard of:

• TiddlyWiki
• DokuWiki
• MediaWiki
• ZIM
• Emacs with Org Mode

Here is a previous discussion on the topic @ Lobste.rs

EDIT: signups are now closed.

relevant blog post

teknik.io is a website that provides services like email, [encrypted] file uploads, Git repos, blogs, URL shortening, and more. I've used them for a few years and they're wonderful. It's all open-source and privacy conscious, maybe some Tildes users would like it?

Registration is usually invite-only, but it's open for a few hours.

Thanks @duckoverflow for mentioning this.

Edit: also their privacy policy is short, simple, and easy-to-read if anyone is interested in that. I'd consider it a great example of what a privacy policy should be.

I have an idea, it's not particularly new. I think git code sharing could integrate very nicely with blockchains.

I think it could be done elegantly without modifying the git protocol at all, just as an optional superset (like Github) to provide forks, PR and discussion.

Something like:

• smart contract based system
• something like lightening network for off master chain pushes
• local node hosting all obtained versions of code, something like PNPM meets zeronet
• cloning/pushing over DHT with web torrent.
• client key pairs for collaboration and authentication

Do you guys think it could be done? Thoughts? Ideas? Criticisms?

Would anyone be interested in working on something like this? I'd like all the help I can get and any input people have.

Having just joined recently and made my way though the (technical goals documentation)[https://docs.tildes.net/technical-goals], I am interested in the lower-level stuff. How scaling is being considered, off-loading static content to CDNs, fault-tolerance etc... As well as code testing, deployments, etc...

I guess this will be a bit clearer when Tildes goes Open, but I think a discussion on it could also be helpful for roadmapping and growth if possible.