Install rules IDK

I HATE GIT

XEPS-TBD.TXT

@@ -31,12 +31,6 @@ For future XEPs:
         A minor issue with that is pack management. XMPP requires a pack field 
         which is used along PEP, it seems, and meanwhile Matrix has ''support''
         for packs too, tracking them is between "annoyance" and "yeah, no.".
-    - https://xmpp.org/extensions/xep-0080.html
-        Doxxing people over two protocols is great! Sadly works over PEP it seems, 
-        so I can't think of a good analogy tbf, also I hate dealing with PEP tbf.
-    - https://xmpp.org/extensions/xep-0118.html
-        I feel like polluting Matrix status(which more clients should implement)
-        sounds like a bad idea. When are we getting _extensible statuses_?
 
 ON STANDBY BECAUSE THESE HAVE BEEN TERRIBLE TO DEAL WITH AND WHO KEEPS WRITING
 THESE I WANT TO SEND THEM A NICE, BRIGHT GIFT:
@@ -45,13 +39,16 @@ THESE I WANT TO SEND THEM A NICE, BRIGHT GIFT:
         Matrix and XMPP both have support for these.
         XEP-0084 is a pain in the ass to implement and seems generally just
         unreliable, however.
+    x https://xmpp.org/extensions/xep-0080.html
+        Can't think of a good analogy to these...
 
 
 Not XEPs, but ideas that _needs_ to be added:
-    ~ "also it [Bifrost] doesn't respect voice either" -> Send a form on moderated 
+    v "also it [Bifrost] doesn't respect voice either" -> Send a form on moderated 
       MUCs (which is standard, so its not too bad!). Currently WIP, and barely tested.
     ~ "GIVE THE PUPPETS APPROPRIATE PLS/ROLES" - Hydro/t4d
     - Standalone/Static Parsee, ideally as small as it can be(if not as APE).
+    - Kappa-like extension system(maybe bridging more than just Matrix-XMPP.)
     - https://www.youtube.com/watch?v=InL414iDZmY