darshan

> Never ask questions or attempt to keep the conversation going -- answer the questions directly asked, and give additional information where it is likely to be helpful, but don't offer to do more things for the user.

I've never had an LLM offer to do things or try to keep the conversation going with this in my prompt.

They apologized to the person they said it to, and it all seems settled from my perspective.

I'd say it's rude in general to tell someone they won't find something interesting, and especially so when it's done as a way of disowning your own preference not to talk about it.

The way I read it is:

* 219-09-9999 is a made-up number that was never issued to anyone.

* The woman thought it was her number for unexplained reasons.

* She used the pamphlet as evidence that it was her number.

I must be missing something important. Is it a joke, with the punchline being that she thought the pamphlet was her social security card? If so, how was this the fault of the Board? Was it her SSN somehow? If so, how did the pamphlet prove it?

Or am I picking up on confusion about my general model (which I'm certainly open to feedback about). If you draw and don't share, but press back or try to leave the page, you're prompted about destructively leaving. Sharing creates the doodle and makes a link for you to share (or bookmark, or whatever you like), so the contents aren't considered wiped at that point; they're considered successfully sent.

Please let me know if I'm failing to understand what isn't working as you expect, of if you think my model is confusing to new users. Thanks!

1) Much of the general idea is a sense of connection and intimacy -- it's not just the final product that you're sharing, but the process. When you see the mistakes, or the attempts to get something just right, it's a moment of connecting with the sender's experience while making it.

2) You can make emotionally evocative doodles by removing elements, so they're only present fleetingly but not present in the final image. (Examples of this are by friends I haven't thought to ask permission to share. But think: drawing a small plant, then undoing and drawing a bigger one, for several iterations, for example. You can sometimes do that by "erasing" the part you want to remove by drawing the background color, but if you want to remove something that's on top of something else, undoing is so much easier.)

The things that are in the native wrappers are things that would be iOS-specific or Android-specific regardless of zero shared code or maximum shared code. In my case, the bulk of the app is shared -- everything that can be a common code base is a common code base.

According to GitHub's rough metrics, that's: Go 44.7% Dart 32.8% Java 7.1% JavaScript 6.9% Swift 6.6%