Allow feed ids in first recps slot

index.js

@@ -256,9 +256,18 @@ function init (ssb, config) {
 
   return {
     publish (content, cb) {
-      if (!content.recps) return cb(Error('recps missing in content'))
+      if (!content.recps) {
+        return ssb.db.create({
+          content,
+        }, cb)
+      }
 
-      if (!isGroup(content.recps[0])) return cb(Error('first recp in recps needs to be a group id'))
+      if (!isGroup(content.recps[0])) {
+        return ssb.db.create({
+          content,
+          encryptionFormat: 'box2'
+        }, cb)
+      }
 
       ssb.box2.getGroupInfo(content.recps[0], (err, groupInfo) => {
         if (err) return cb(Error('error on getting group info in publish', { cause: err }))

test/publish.test.js

@@ -83,7 +83,7 @@ test('publish (group + feedId)', t => {
   })
 })
 
-test.skip('publish (DMs: myFeedId + feedId)', async t => {
+test('publish (DMs: myFeedId + feedId)', async t => {
   const alice = Server()
   const bob = Server()
   const name = (id) => {
@@ -94,7 +94,6 @@ test.skip('publish (DMs: myFeedId + feedId)', async t => {
   const content = {
     type: 'announce',
     text: 'summer has arrived in wellington!',
-    // TODO: failing here because the first recp isn't a groupId. the old code just published anyway. do we still want to do that? i think the spec might allow it but we disallow it in tribes2
     recps: [alice.id, bob.id]
   }