photo brainstorming is a page where indieweb users who are working out how to publish photos on their own site can document design challenges, issues, brainstorm ideas and show examples of photography on the web that inspires them.
People Area Tagging
Why POSSE rather than TwitterCard
(Not sure if this belongs here or on Twitter page, but capturing as part of this for now.) Advantages to POSSEing actual photos to Twitter, rather than just a link to a photo post on your site with Twitter Cards metacrap markup:
- Further distribute the use of Twitter kind of like a CDN for your photos
- People see a larger version of the photo via a phototweet than a Twittercard
- Usual avoid metacrap (silo-specific meta tags) advantage
- Photo tweets appear inline in tweet list views (e.g. Twitter timeline / homepage) whereas twitter cards won't appear inline automatically (require twiddling open).
- Photo tweets work immediately, whereas photo cards require that Twitter whitelist your domain for cards in general (and maybe in particular for photo cards?)
- Using the TwitterAPI hides the proprietariness, whereas using twittercards means your own website has proprietary metacrap on it
- Twittercards set a worse example (proprietary metacrap) for others that may view source
It may make sense to cluster sequential photo posts when displaying them in a stream, especially in a composite stream (e.g. on a homepage).
- Tantek Çelik use-case is I want sometimes I want to post a bunch (a ton?) of photos and not worry that it would be "filling up" my homepage or stream etc. related: publics - concerns about overposting.
- Aaron Parecki Ah yeah the "dump lots of photos" problem i can relate to
- Aaron Parecki: "I often have unrelated photos in a sequence on my home page and I don't want them to cluster in a way that implies they are related"
- If the photos share a hashtag which is used in <10% of photo posts, then cluster them.
- that way if they really were "unrelated" photos, they wouldn't get clustered
- Aaron Parecki "if I wanted photos to be clustered I would make an album post instead"
Hosting my own photos has been something I've been wanting to do for a while. This is partly because I'm unhappy with most of the silos I've used:
- Instagram — fine for the odd snap, but I use it in private mode because there's no easy way of having privacy controls.
- Facebook — fine for putting up photos of friends, but... it's Facebook and they creep me out.
- Flickr — one word: Yahoo! It's been redesigned a couple of times now, not necessarily for the better.
- Wikimedia Commons — I'm reasonably confident Commons will stick around, but am unhappy with some of the administrative politics (and deeply distrust some of the administrators), and it has a limited scope—hosting only "freely-licensed educational media content". Commons is a great place to host some but not all content I wish to post. Commons is also very rigid about copyright: it attempts to adhere to copyright in both the United States and in the country where the photograph was taken. Some photos taken in France, Belgium, Italy and (with obscure exceptions) the Netherlands which do not have freedom of panorama cannot be hosted on Commons even though the images are legal in my country of citizenship, the United Kingdom.
Ideally, I want to host my own photos and have some of them stored elsewhere. The ones I don't want to be public are probably best stored on Facebook.
Photography on the web I find inspiring
- Paul Stamatiou's Photos — good photography, enticing layout.
- Urban75 — Urban75 is an old-school staple of British independent web publishing. The layout is very 90s but the photography is pretty good, and the information architecture makes me want to explore it more.
How to take photos
Some tips here for how as an indie photographer you can instruct your subjects:
- 2018-05-30 NYT: How to Pose for a Photograph