Maybe combined with ChatGPT we could even make those automatic getting-back-in-touch messages indistinguishable from the manual ones.
I’ve never heard that idea before and I love it.
So half a bit would be like hearing "Umm..." in response to that same question?
"Is this tree deciduous?" "Yes" - one bit
"Is this tree evergreen?" "Probably" - one bit (they don't know), another bit (their guess)
But I'm way off any formal understanding of this, and it can be rigorously defined.
Meta comment: "half a bit" was clearly a joke, and so was my response; now I'm taking your reply at face value and debating it seriously, while admitting that I haven't got anything close to firm enough ground under me to actually debate it :)
"Umm..." definitely carries some kind of information, but it doesn't actually help answer the question.
Based on the information theoretic definition of entropy we'd need to go from 50:50 to 89% certainty to get half a bit of information, and I'd probably qualify 89% certainty as "probably"
To try to be a little constructive, is a relationship really worth anything if a half-bit is all one can spare for it?
I'm more unsettled by the automation part. At least the half-bit received came from someone who consciously thought about you enough to send it. Once you emulate that part, all you have is a MITM initiating conversations between strangers.
extending this bit further - we might as well reply with chatGPT. then it's chatGPT all the way down, who needs human interaction when we tick the boxes of "I called them" and "I replied"?.. :)
"AI" for the following cases would be beneficial:
Social -> Antisocial
Social <- Antisocial
"AI" for the following cases would be net neutral:
Antisocial -> Antisocial
Antisocial <- Antisocial
And finally "AI" would be inapplicable (since neither party would use it) in the following cases:
Social -> Social
Social <- Social
In this drastically simplified model, there aren't any cases where the existence of a sufficiently competent AI would be detrimental to any party involved, while still providing value for those who choose to use it.
To be pedantic, this is not a single bit of data. This is zero bits attached to an event. The event is not discrete however, so I'm not sure what form of information theory would be appropriate to describe it.
Like if you'd walk on a noisy street, see someone you know, and greet them half-heartedly and wouldn't really mind if they didn't hear you.
Oh man, the thrill of not knowing if this message will actually be sent when I hit the "reply" button!
- MonicaHQ (open-source)
- Dex (free version seems good enough for most people, i'm trying this one out rn) getdex.com/
- Custom system in Airtable - https://news.ycombinator.com/item?id=30329475
- Infrequent app - blog post talks more about it, linked in comments - https://news.ycombinator.com/item?id=33308084
Personally, I would just like to see a contacts app that doesn't suck, and actually supports having both "companies" AND "people" as contact without treating them exactly the same. If I want to call some hotel or something, why does it have to be "First name: Holiday Inn" in order to even show up correctly...
It is, in other words, the exact opposite of 'spaced repetition', where you want to review right before forgetting to strengthen the memory the most; in this use-case, 'anti-spaced repetition', you want to review only after you've forgotten it. (https://www.gwern.net/Statistical-notes#program-for-non-spac...)
Also, want it to be 100% local and privacy first.
But I also want an AI personal assistant to know what to write to everyone, what we last did, what would they be interested in, and so on.
There’s also the problem of entering unflattering details, and subsequently leaking them out.
The search continues.
Great, easy to integrate one service with the APIs of a bunch of others!
> Also, want it to be 100% local and privacy first.
...but in combination? Never going to happen.
Ask yourself: who's signing up for the API keys to enable the client-side service to talk to all these services? Is it the end-user, or is it this software's developer?
If it's the software's developer, then they're effectively leaking all these API keys by embedding them into the software itself — where not just the end users, but anyone else could come along and reuse these keys for anything they like. The service providers will find this out, and block these keys. (No, you can't avoid this by proxying requests to some gateway, operated by the service-provider, that holds the API keys. Then you lose the "local/private" aspect.)
If it's each end-user, then the aggregate traffic from all the instances of this app running at once, will look exactly like a bot that's trying to evade API rate-limits using a "residential proxy cluster" like https://www.zyte.com/smart-proxy-manager/... and so the services will block these keys.
---
Mind you, in theory, you could do this on the OS level, using OS accessibility APIs to effectively "read" the messages off the screen. But 1. is there any third-party ISV — who isn't a certified accessibility-software provider — who you'd trust enough to allow their software the ability to constantly "read" everything on your screen? That includes your passwords, you know! And also, 2., the messages need to be on the screen for accessibility software to read them. An accessibility-API-driven CRM can't load your chat history unless you also grant it the ability to literally take your mouse and scroll through it for you.
Or, alternately, coming at this from the perspective of the Operating System vendor themselves, you could do this "in" the OS, by forcing emails/text/chat message handling to go through system APIs that can see these as special document types, and so do things with them. IIRC there was at least one pre-iPhone mobile OS that did this (BlackBerry OS, maybe?), enabling all of these types of messaging-app traffic to be muxed together into a single first-party app that did indeed manage all conversations with your contacts in a multi-channel way.
Look into it, you might be surprised.
You were very active with this friend for n years and it dropped off. Drop them a line.
Also, that presumes you're on desktop. On mobile, you just can't poke into another app's sandbox/container that way (unless the target app hasn't explicitly granted made some part of its container-filesystem externally accessible; and there's no reason these apps would.) And many people only have a mobile device.
If you're okay with a partial solution, a far easier one would be scraping the data out of the few clients that have web-app versions through browser extensions that read the state out of the page they're running in.
Problem is there’s a lot of input and upkeep which limits appeal, the most important social data sources (text & phone) are not accessible via api, its a personal tool that you don’t necessarily want to tell others you use which limits distribution & scale, and even after all that in general it’s hard to scale personal authenticity.
I think the problem needs to be approached from a different angle along the lines of a personal assistant rather that an explicit data management tool. And it likely has to come from those with access to privileged social data sources like Apple or Google or Facebook.
We would have continued a while longer but the 08 recession really burnt us. We were raising $$ in the weeks where banks were literally failing. RIP Good Times era. Our iPhone app was just about ready to ship and we were going to start building integrations like email next, but no runway. We had an angel lined up who’d have gotten us about 4-6mo of runway but I didn’t want to burn that relationship in such an uncertain environment, we were all pretty down about prospects then.
Fun fact tho: the app continued to work for years after. FB took a long time to deprecate API and our code was pretty solid.
The goal is to avoid just a dumb timer saying 'its been 4 weeks, why don't you chat with X'. That's how Socialfly worked, and it was pretty high friction in practical use.
For a while, I was going to a weekly event where I'd meet people, but I'd never remember their name next time because I'm terrible with names.
So I started jotting down notes after it was over. Like, today I met person X who is really into this one hobby and just moved here from such and such city. And person Y who is looking for a new apartment. And Z who came with Y.
Then before going next time, I'd review the list, and if I saw X, I knew their name and could ask how they're adjusting after their move. Or I could ask Y how the apartment search is going.
At first I thought if people saw this list they might think it was a little weird. And maybe, but I'm OK with it since it's a way of making an effort. As long as it's genuine and your motivations are good, people like that you remembered stuff about them. (I'm not doing it to impress people, etc.)
Anyway, I didn't have a good way to organize it. I stuck it all in a document, which didn't work great.
Integrate a scraping and keyword search for public facing social media postings to alert to people in distress, perhaps. Or just a general "you should check on X" feature. Not with automated messaging, that's too much.
Well, if you are worried about it being cringy, you probably shouldn't watch the 2022 Salesforce Dreamforce (their annual convention). It's cultish and shows the unbelievably arrogant confidence they have in their own importance - along with the most inexplicably childish moments for a professional conference I've ever seen. (Let's put foam rabbit ears on our "co-CEOs" to entertain the "trailblazers" as we gather around a fake wooden stage imitating the outdoors with faux trees, won't that be funny?)
This is what social media and messaging apps should innovate on.
But, without VC money, without ads, without feeds drive by algorithms that optimize for engagement. Without dark patterns and antifeatures that make our lives worse. Just a non-profit that churns out open source code and is supported by monthly recurring donations from a % of the userbase.
* https://keepmyfriends.com/ * https://getdex.com/
I haven't used any personally!