xmpp.dk
/
website
1
0
Fork 0
Code Issues Releases Activity

Fix blog post newlines so they work with excerpts 

Jekyll's default excerpt_separator is `\n\n`.
This commit is contained in:
Jesper Hess 2017-01-08 12:20:04 +01:00
parent 7ac88bdcab
commit 89fe1c63fd
Signed by: graffen
GPG Key ID: 351A89E40D763F0F
6 changed files with 17 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_posts/2016-04-06-xmppdk-launched.markdown
View File

@ -2,11 +2,11 @@
title: xmpp.dk launched!
layout: post
---
For a long time I've been wanting to set up a proper, public and free Jabber server. I've been looking around for a cool and relatively generic domain name for the server and last night I stumbled across the fact that xmpp.dk had been abandoned.
For a long time I've been wanting to set up a proper, public and free Jabber server. I've been looking around for a cool and relatively generic domain name for the server and last night I stumbled across the fact that xmpp.dk had been abandoned.
So I jumped at the chance, and what you're looking at is the result of this. I'll use this blog to post news when stuff happens and to keep you users up-to-date on the state of things. Hopefully I won't be posting a lot though :).
For now, feel free to create an account, add me (details under [Contact][contact]) or any of your friends and start chatting away.
For now, feel free to create an account, add me (details under [Contact][contact]) or any of your friends and start chatting away.
If you have any wishes or requests, just drop me a line.

2
_posts/2016-04-25-otr-required.markdown
View File

@ -3,7 +3,7 @@ title: OTR is now required on xmpp.dk
layout: post
---
OTR is now required to communicate through xmpp.dk. If someone attempts to initiate a chat to you without first enabling OTR,
they will be greeted with the following message:
they will be greeted with the following message:
```For security reasons, OTR encryption is required for conversations on this server```

2
_posts/2016-09-27-minor-site-update.markdown
View File

@ -2,6 +2,6 @@
title: Minor site update
layout: post
---
I added a page with information about the current set of OTR and TLS fingerprints in case you wish to verify the authenticicy of the web site and your XMPP connection.
I added a page with information about the current set of OTR and TLS fingerprints in case you wish to verify the authenticicy of the web site and your XMPP connection.
I will make sure to update the fingerprints and post on the blog every time the certificates get updated. Since I use LetsEncrypt, the certificates expire every 90 days.

2
_posts/2016-10-14-ipv6-support.markdown
View File

@ -2,7 +2,7 @@
title: IPv6 now supported
layout: post
---
When I initially set up this server, I was quite surprised that my provider had stopped supplying IPv6 addresses to new hosts.
When I initially set up this server, I was quite surprised that my provider had stopped supplying IPv6 addresses to new hosts.
But now IPv6 support is back, and I have got an address assigned to this server. Therefore, xmpp.dk and all services on it, are now accessible via IPv6.

20
_posts/2016-12-30-tls-s2s-now-required.md
View File

@ -5,22 +5,22 @@ layout: post
Coming to the end of 2016 I've been really happy with how much traffic this service is receiving. As I don't log anything, I haven't really
got a way to see exactly how much you guys have been chatting through xmpp.dk. But I can see from the traffic stats that the server is at least
generating a fair amount of traffic so that's awesome!
generating a fair amount of traffic so that's awesome!
Since we are at the end of 2016 and there is an ever-growing push for more and more privcay, I have decided that now is the time to take the next step.
Up until now, the server has been configured to _prefer_ but not _require_ TLS when connecting to other XMPP servers. That means that even though OTR is
required and your messages aren't being transmitted in cleartext, the XMPP messages themselves might have been.
But from today, the server's configuration has been changed so that TLS is now a _full requirement_ when another XMPP server wants to connect to us.
But from today, the server's configuration has been changed so that TLS is now a _full requirement_ when another XMPP server wants to connect to us.
This decision does come with some problems, however. There are _lots_ of XMPP servers out there that do not support TLS. Unfortunately, this means that you
as a user will no longer be able to talk to people who use these servers.
as a user will no longer be able to talk to people who use these servers.
If you're having trouble reaching some of your contacts now, you should either get your friends to persuade their providers to start using TLS for everyone's
increased privacy, or talk your friends into switching to a provider that already does. There are lots of free Jabber servers out there that do support
encrypted communications, so take a look at [xmpp.net][xmppnet] and look for servers that have at least an "A" grade in both C2S (client-to-server) and S2S (server-to-server).
Happy new year everyone!
encrypted communications, so take a look at [xmpp.net][xmppnet] and look for servers that have at least an "A" grade in both C2S (client-to-server) and S2S (server-to-server).
Happy new year everyone!
/Graffen

5
_posts/2017-01-02-twitter-account.md
View File

@ -4,9 +4,8 @@ layout: post
---
{% icon fa-twitter fa-5x %}
I've been posting updates about this service on my own personal Twitter for a while but I've decided I need a separate place where
I can report on things like certificate updates, maintenance schedules and the like.
I can report on things like certificate updates, maintenance schedules and the like.
So if you want to stay up-to-date and informed, go <a href="https://twitter.com/{{site.twitter_username }}">follow us on Twitter!</a>
[xmppnet]: https://xmpp.net/directory.php