fixed markup in observations.md
This commit is contained in:
parent
894ffc6488
commit
b32552f7d9
|
@ -8,7 +8,7 @@ which make the life on mobile devices a lot easier but states that they are
|
||||||
currently very few implementations of those XEPs. So I went ahead and
|
currently very few implementations of those XEPs. So I went ahead and
|
||||||
implemented all of them in my Android XMPP client.
|
implemented all of them in my Android XMPP client.
|
||||||
|
|
||||||
###General observations
|
### General observations
|
||||||
The first thing I noticed is that XMPP is actually okish designed. If you were
|
The first thing I noticed is that XMPP is actually okish designed. If you were
|
||||||
to design a new chat protocol today you probably wouldn’t choose XML again
|
to design a new chat protocol today you probably wouldn’t choose XML again
|
||||||
however the protocol basically consists of only three different packages which
|
however the protocol basically consists of only three different packages which
|
||||||
|
@ -16,7 +16,7 @@ are quickly hidden under some sort of abstraction layer within your library.
|
||||||
Getting from zero to sending messages to other users actually was very simple
|
Getting from zero to sending messages to other users actually was very simple
|
||||||
and straight forward. But then came the XEPs.
|
and straight forward. But then came the XEPs.
|
||||||
|
|
||||||
###Multi-User Chat
|
### Multi-User Chat
|
||||||
The first one was XEP-0045 Multi-User Chat. This is the one XEP of the XEPs I’m
|
The first one was XEP-0045 Multi-User Chat. This is the one XEP of the XEPs I’m
|
||||||
going to mention in my article which is actually wildly adopted. Most clients
|
going to mention in my article which is actually wildly adopted. Most clients
|
||||||
and servers I know of support MUC. However the level of completeness varies.
|
and servers I know of support MUC. However the level of completeness varies.
|
||||||
|
@ -34,7 +34,7 @@ desktop for example) one wouldn’t have to name oneself `userDesktop` and
|
||||||
strange side effects. Prosody for example doesn’t allow a user to change its
|
strange side effects. Prosody for example doesn’t allow a user to change its
|
||||||
name once two clients are “merged” by having the same nick.
|
name once two clients are “merged” by having the same nick.
|
||||||
|
|
||||||
###Carbons and Stream Management
|
### Carbons and Stream Management
|
||||||
Two of the other XEPs Lukas mentions — Carbons (XEP-0280) and Stream Management
|
Two of the other XEPs Lukas mentions — Carbons (XEP-0280) and Stream Management
|
||||||
(XEP-0198) — were actually fairly easy to implement. The only challenges were to
|
(XEP-0198) — were actually fairly easy to implement. The only challenges were to
|
||||||
find a server to support them (I ended up running my own Prosody server) and a
|
find a server to support them (I ended up running my own Prosody server) and a
|
||||||
|
@ -44,7 +44,7 @@ mobile device. I had sessions running for up to 24 hours with a walking outside,
|
||||||
loosing mobile coverage for a few minutes and so on. The only limitation was
|
loosing mobile coverage for a few minutes and so on. The only limitation was
|
||||||
that I had to keep on developing and reinstalling my app.
|
that I had to keep on developing and reinstalling my app.
|
||||||
|
|
||||||
###Off the record
|
### Off the record
|
||||||
And then came OTR... This is were I spend the most time debugging stuff and
|
And then came OTR... This is were I spend the most time debugging stuff and
|
||||||
trying to get things right and compatible with other clients. This is the part
|
trying to get things right and compatible with other clients. This is the part
|
||||||
were I want to help other developers not to make the same mistakes and maybe
|
were I want to help other developers not to make the same mistakes and maybe
|
||||||
|
@ -73,7 +73,7 @@ honor the private tag on outgoing messages. While this is easily fixed I presume
|
||||||
that having both the private and the no-copy tag will make it more compatible
|
that having both the private and the no-copy tag will make it more compatible
|
||||||
with servers or clients I don’t know about yet.
|
with servers or clients I don’t know about yet.
|
||||||
|
|
||||||
####Rules to follow when implementing OTR
|
#### Rules to follow when implementing OTR
|
||||||
To summarize my observations on implementing OTR in XMPP let me make the
|
To summarize my observations on implementing OTR in XMPP let me make the
|
||||||
following three statements.
|
following three statements.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue