I wrote something similar in Java that basically adds a ttl to everything I post. My grand vision was to support all social media that just eats there breadcrumbs I leave behind.
I really wish self destructing messages were more common.
That's my favorite feature of keybase chat.
My week old conversation is irrelevant it has no reason to exist beyond that time frame.
Agree on wishing for more self-destructing messages. I was looking at the Facebook Graph API as well and (unsurprisingly) it didn't look like they grant you much control over deletion.
My idea was to just have a service that ties to a web page where you can choose the media and give a TTL based on content. Then just have the service run every N time or be reactive depending on how you architect it but the general idea is:
tweet: delete every 7 days
DMS: keep?
FB photo: no TTL, or maybe 1 year.
Of course you can do this on a per message as well when you send it, but the more social services you add and supported content type the more complex it gets. Though if anyone wrote something like this, I would love to use it.
I wrote something similar in Java that basically adds a ttl to everything I post. My grand vision was to support all social media that just eats there breadcrumbs I leave behind.
I really wish self destructing messages were more common.
That's my favorite feature of keybase chat.
My week old conversation is irrelevant it has no reason to exist beyond that time frame.
Ahhh ttl is a great idea!
Agree on wishing for more self-destructing messages. I was looking at the Facebook Graph API as well and (unsurprisingly) it didn't look like they grant you much control over deletion.
My idea was to just have a service that ties to a web page where you can choose the media and give a TTL based on content. Then just have the service run every N time or be reactive depending on how you architect it but the general idea is:
tweet: delete every 7 days
DMS: keep?
FB photo: no TTL, or maybe 1 year.
Of course you can do this on a per message as well when you send it, but the more social services you add and supported content type the more complex it gets. Though if anyone wrote something like this, I would love to use it.
This needs a lot of love, but if anyone finds value in it, there's the code: github.com/SocialOxpecker/SocialOx...