Image Distribution
i have reached the limits of gmail forwarding. before there was no need to verify forwarding addresses. it's a problem for me now because the addresses i want to forward to are not natural inboxes but automated systems with no way to track the verification email contents.
current channel for photos:
mobile -> gmail -> facebook-email
-> flickr-email-0
i want to extend this to:
mobile -> gmail -> facebook-email
-> flickr-email-1 -> twitter(text+link) #prereq: flickr services: twitter; http://www.flickr.com/services/twitter/
-> tumblr-email
-> posterous-email
how do i do this without gmail filters?
i think i would want to use fetchmail to watch my inbox and then autoforward to the above addresses. is fetchmail the best solution to this issue? any other MRA's? ref:
http://en.wikipedia.org/wiki/Mail_retrieval_agent
i'd like to do some more complicated things with the emails in an automated fashion too, how would i go about monitoring the inbox, doing some actions to the email before forwarding, and forward everywhere?
prerequisites:
a server:
fetchmail daemon to poll the account
local mailbox
script to clean & forward appropriately
backup email account (gmail)
is there an easier way to do this? any help would be greatly appreciated. i'm trying to automate my social content distribution.
(this question is mirrored on
SuperUser)
Here are a few other image channels:
laptop:
D80 -> flickr -> twitter #prereq: flickr services: twitter; http://www.flickr.com/services/twitter/
-> facebook
-> tumblr
-> local backup -> mirror
screenshots -> flickr -> twitter #prereq: flickr services: twitter; http://www.flickr.com/services/twitter/
-> tumblr
-> webhosting
-> local backup -> mirror
images -> tumblr
-> webhosting
-> local backup -> mirror
Small Format Text Distribution
i think this one is all figured out except backing everything up well.
mobile -> twitter -> facebook #prereq: facebook's twitter app
-> tumblr
-> posterous
laptop:
twitter -> facebook #prereq: facebook's twitter app
facebook
facebookquestions
quora -> twitter #prereq: quora's twitter auth
vark -> twitter #prereq: vark's twitter auth
superuser
buzz
i wonder if there's a great way to aggregate and backup all small format texts? ideas?
some possibilities:
scraping the endpoints
collecting during posttime
putting an intermediary backup point in each path
Large Format Text Distribution
laptop:
Documents:
pdf/word -> google docs -> twitter -> facebook
-> forums
-> docshare
-> local backup -> mirror
raw text -> forums -> twitter -> facebook
-> personal website -> twitter -> facebook
-> tumblr
-> facebook note
-> local backup -> mirror
looking for better ways to have a central repository and backup for all this as well.
Sharable Music Distribution
laptop:
youtube -> facebook
-> twitter
lastfm -> twitter -> facebook
soundcloud -> twitter -> facebook
Generic Web Content Distribution
laptop:
google reader -> rss_feed -> rss graffiti -> facebook
-> tumblr
-> buzz
-> bookmarks -> local backup -> mirror
stumbleupon -> twitter -> facebook
-> bookmarks -> local backup -> mirror
forums -> twitter -> facebook
-> bookmarks -> local backup -> mirror
delicious -> twitter -> facebook
-> local backup -> mirror
reddit -> bookmarks -> local backup -> mirror
i look forward to reading (and replying to) this when i have more time.
asemisldkfj
the law is no protection
once you figure out how to back all of these things up, let's create some web-based software that lets you search it and view it all pretty. something good for data-obsessed people. I don't know how many of those there are though.
imagine someone seeing a neat word cloud of their twitter updates generated from their backups and then wanting to share it on twitter.
asemisldkfj
the law is no protection
you could have something that pulls most of this content from its destination (e.g., facebook), rather than try to insert some intermediary backup point into each process. I don't know how easy various sites make this though. facebook has that download option but I don't know if you can automate it in any way.
this thread makes me want a speakeasy connection again.
For the photo channel, the message is also important for filtering, and replication purposes.
A sample message would be:
Subject: @projectdp photo distrib. test
http://flic.kr/p/9eTHqv
Attachment: 1600x1200 image from a 3 megapixel camera
(this example is 55/140 characters)
i use the "@projectdp" syntax for filtering purposes in one specific scenario, but it serves a dual purpose. mainly it's so that when i post to both flickr and facebook, the image reference isn't duplicated on facebook a second time with a text link. because i have facebook's twitter app monitoring my twitter feed for updates, it will pull anything that's not a reply or direct message. so i have to use a reply, and i might as well use a reply to myself so people see my username more often.
...gmail -> facebook-email -> facebook
-> flickr-email-1 -> flickr -> twitter(text+link) -> facebook
it'd be nice to have rule based outbound tweet signaling. this is where a python twitter bot might be helpful, but i can't really get over facebook's-twitter app limitations unless i want to work on an app for facebook.
---
asemi:
yeah i'm interested in that. i was thinking of a similar thing with images. consider this:
a full page of images appears, however many that fit.
when you click the image, it removes it, marking it as archive, a new image appears in its place. you remove all unwanted images from the view, then hit a save button. loop.
then you have a speedily sorted collection of all your images.
there would be another view of images, a horizontal ribbon
this one allows you to view your saved collection, you can sort however you like, but the idea is loosely: you can move the order of the images easily, when you click the image this time it allows you to schedule the sharing of these items. you can select the overall default post time interval in settings. you can select the services you want images sent to in settings (in my case: twitter, tumblr, facebook).
i think the cool part about this would be: it's an rss feed and it has timed updates of things you definitely want to share, and have digested already in the past.
when i say an intermediary backup point in each process it would be fairly transparent, and hopefully automated, kind of like the gmail setup with photos.
i can build (or help build) this solution for you to your specifications
let me know if you're interested
> fetchmail daemon to poll the account
this is less than ideal. it would be much more cool if you had an mta running with a hook that ran a script on every incoming email exactly when it is received.
i'm looking into mtas with the proper hooks for you. i can host this for you
i'm running postfix presently.
Postfix's approach allows for great flexibility. It is highly tunable through several configuration options, and besides supporting email standards, it provides well-documented interfaces for working with other programs. Postfix provides hooks to plug in all kinds of content filters and policy servers.
(http://www.seaglass.com/postfix/narrative-chapter.html)
this looks easy enough:
pipe
thanks for the help. pipe looks good!