Add more serious scrap

scraps/idea:persistent-chat-client

@@ -0,0 +1,21 @@
+id: 'idea:persistent-chat-client'
+content: |
+  One could (to easily work with existing chat services) write a
+  secondary, personal server. This would act as a meta-client,
+  actually being responsible for talking to other chat services,
+  keeping secondary logs of that content and maybe scraping it
+  for image links &c.
+
+  It would then open a (protected) connection to some other kind
+  of chat client, either over an existing chat protocol or using a
+  new secured protocol. If no connections are currently active, then
+  it would set the relevant presence to 'offline', whereas if one
+  or more clients are connected, it will transparently allow any
+  or all of them to communicate.
+
+  (This is in sharp contrast to typical Jabber implementations,
+  which always designate a particular connection as 'active'.)
+
+  It could also send the last dozen (or so) messages send and
+  received to the client, so that switching client in
+  mid-conversation will still keep the user in the loop.

scraps/test-scrap

@@ -1,9 +0,0 @@
-id: test-scrap
-content: |
-  what the **hey**, man,
-  is this
-related:
-  - name: test-scrap
-    why:  "it's THIS one"
-  - name: test-two
-    why:  "it's another scrap, is why"

scraps/test-three

@@ -1,2 +0,0 @@
-id: test-three
-content: WHOOO

scraps/test-two

@@ -1,5 +0,0 @@
-id: test-two
-content: |
-  This is another one with
-
-      def some_code(): pass