jabber.at - Recent updateshttps://jabber.at/feed/en/atom.xml2019-09-26T10:35:35Z/static/feed/atom_icon.4b46da0b6025.png/static/feed/atom.27f8db2e34fd.png© 2010-2019, jabber.athttps://jabber.at/b/registration-deactivated/Registration deactivated2019-09-26T10:35:35Z2019-09-26T10:35:35Z<p>We've deactivated the registration some time ago. Currently it is not possible to create new accounts for all domains hosted by us. This only affects new registrations, existing accounts are not affected.<p>We've deactivated the registration some time ago. . Currently it is not possible to create new accounts for all domains hosted by us.astrahttps://jabber.at/b/updated-webchat/Updated webchat2018-09-24T18:48:50Z2018-09-24T18:48:50Z<p>We have updated <a href="https://jabber.at/chat/">out webchat</a> to a new version, we now use <a href="https://conversejs.org/" target=_blank rel=noopener>ConverseJS 4.0.1</a>. The new version brings many new features, most prominently OMEMO end to end encryption and easier and more reliable file-sharing with other users.<p>We have updated <a href="https://jabber.at/chat/">out webchat</a> to a new version, we now use <a href="https://conversejs.org/">ConverseJS 4.0.1</a>. . The new version brings many new features, most prominently OMEMO end to end encryption and easier and more reliable file-sharing with other users.matihttps://jabber.at/b/registration-is-reactivated/Registration is reactivated2018-09-01T17:09:43Z2018-09-01T17:09:43Z<p>We have just reactivated our activation. Feel free to once again register an account on our server!<p>We have just reactivated our activation. . Feel free to once again register an account on our server!</p>.matihttps://jabber.at/b/jabber-at-and-the-gdpr/jabber.at and the GDPR2018-05-17T15:19:13Z2018-05-13T12:16:26Z<p>As some of you are most certainly aware, the <a href="https://en.wikipedia.org/wiki/General_Data_Protection_Regulation">General Data Protection Regulation</a> (GDPR) will come into force on May 25th, 2018. It is a major step forward for users of any service that handles privacy related data. Obviously, this services is affected by the GDPR too, so we'd like to take some time to give you an overview of your rights and what they mean in context of jabber.at.</p>
<p>In general, please be aware that</p>
<ul>
<li>jabber.at is run by private individuals in their free time.</li>
<li>As such, jabber.at is a "best effort" service in all respects.</li>
<li>None of us are lawyers or anything close to it.</li>
<li>We have zero income from this service: jabber.at is free for all users. We have no ads and take no private donations.</li>
<li>We have zero expenses - except lots of our free time - from this service: Necessary infrastructure (server, bandwidth) is provided by the Students Union of Computer Science Students of the Vienna University of Technology. Thanks!</li>
</ul>
<p>Your privacy, with or without the GDPR, always has been and always will be of the upmost importance to us. We are committed to upholding the highest standards possible to us. We also want to answer all your questions (<a href="https://jabber.at/contact/">contact</a>) should anything remain unclear.</p>
<p>For example the unofficial information portal <a href="https://www.eugdpr.org">eugdpr.org</a> lists the <a href="https://www.eugdpr.org/key-changes.html">key rights</a> ("Data Subject Rights") you get from the GDPR. We'd like to comment on each of them and what they mean to you with regards to jabber.at.</p>
<h2>Breach Notification</h2>
<p>Notifying you of any breach in our services (e.g. if we accidentally publish data or our services are hacked) is common sense. We have practiced this in the past and will continue to notify you of any breach we become aware of.</p>
<h2>Right to Access</h2>
<p>Your personal data is used and processed exclusively for providing you with a Jabber/XMPP service. Our servers and all data on them are located in Vienna, Austria.</p>
<p>Regarding a "copy of your personal data in electronic format":</p>
<ol>
<li>The only data that cannot be retrieved directly from your client are webserver logs and connection information in short term storage for SPAM-fighting purposes. This data is not necessary for transferring your account to another service and will be removed automatically after a short period of time (see <a href="https://jabber.at/p/privacy/">privacy policy</a>).</li>
<li>There currently is no open format (that we are aware of) that provides XMPP account data in a transferable format. When such a format becomes available and our software supports generating such files, we will provide you with that feature.</li>
<li>This currently means that retrieving data via your client is your best option to get such a copy.</li>
</ol>
<h2>Right to be Forgotten</h2>
<p>If you want to remove parts of your data (e.g. data you published as a vCard), you can do so directly in the client.</p>
<p>If you want to remove all data from our servers, you can do so <a href="https://jabber.at/account/delete/">here</a>. This will immediately delete all data except webserver logs (which are not directly related to your account) and any short-term connection information that is used to fight SPAM. Both data sets will be removed automatically after a short period of time.</p>
<h2>Data Portability</h2>
<p>The idea that users can freely choose services provides is at the very core of the Jabber/XMPP protocol.</p>
<p>Since there currently is no standardized exchange format to transfer your data to other XMPP services, we cannot really provide "machine readable" data beyond what is available via the XMPP protocol that is useful to you. Once there is such a file format, we will provide download/upload functionality to you.</p>
<p>Note that some data cannot be transferred automatically by definition, for example your contact roster and who <em>you</em> are able to see as online, since this data is also stored on the roster of the other user and hence not on our server. You will always have to manually renew subscriptions.</p>
<h2>Privacy By Design</h2>
<p>We only provide a small part of the Jabber/XMPP ecosystem. For those parts that we are responsible for, we strive to minimize the data we store as possible.</p>
<h2>Data Protection Officers</h2>
<p>We currently believe that this requirement is not applicable to us. In short, "... whose <em>core activities consist of processing operations which require regular and systematic monitoring of data subjects on a large scale or of special categories of data or data relating to criminal convictions and offences</em>" as listed on the eugdpr.org homepage does not describe us as a service.<p>As some of you are most certainly aware, the <a href="https://en.wikipedia.org/wiki/General_Data_Protection_Regulation">General Data Protection Regulation</a> (GDPR) will come into force on May 25th, 2018. It is a major step forward for users of any service that handles privacy related data. . Obviously, this services is affected by the GDPR too, so we'd like to take some time to give you an overview of your rights and what they mean in context of jabber.at.matihttps://jabber.at/b/updates-to-our-privacy-policy/Updates to our privacy policy2018-05-13T11:33:20Z2018-05-13T11:25:06Z<p>In light of the new GDPR we have taken the time to update our <a href="https://jabber.at/p/privacy/">privacy policy</a>. There are no really significant changes, but this is a complete list of every change:</p>
<ul>
<li>We have added a set of "General principles". These are nothing fancy and we have always been following them, but we feel that they really make everything much more understandable to a novice.</li>
<li>We have restructured the policy to distinguish between connection information (such as IP addresses etc.), account information (data directly related to your account) and Jabber/XMPP related information (anything that's typically happening via the Jabber/XMPP protocol).</li>
<li>Some redundant paragraphs in "What happens to your data?" has been removed.</li>
</ul>
<p>The following information has been added/clarified (the points in the policy are quoted verbatim, comments are <span class=text-muted>greyed out</span>):</p>
<ul>
<li>"This homepage does keep track of your activities to enable you to review any suspicious behavior. You can view all data under <a href="https://jabber.at/account/log/">Recent activity</a> and it is removed after 31 days."<br><br><span class=text-muted>This really is all plainly visible directly in your account area and is nothing new. It was a much-requested security feature and is standard in many services (e.g. Facebook offers a similar feature).<br><br></span></li>
<li>"Your activities on this homepage are stored in a short-term cache to enable us to detect automated behavior that might impact the stability of this service. Depending on the data, this data disappears automatically after anywhere from an hour to a week."<br><br><span class=text-muted>This really is about standard SPAM fighting practices. Try to register 100 accounts from the same IP address, and you'll obviously get blocked for a while.<br><br></span></li>
<li>Your email address to enable you to reset your password in case you ever loose it.<br><br><span class=text-muted>You have to give this during registration. So it's obviously not news to anyone?</span></li>
</ul><p>In light of the new GDPR we have taken the time to update our <a href="https://jabber.at/p/privacy/">privacy policy</a>. . There are no really significant changes, but this is a complete list of every change.matihttps://jabber.at/b/temporary-suspension-of-registration/Temporary suspension of registration2018-01-06T13:31:07Z2018-01-06T13:31:07Z<p>We have decided to temporarily stop registration of new users to our services. We do not have a date for reopening registration, but we hope it will be soon.</p>
<p>In the past years we have seen an incredible growth of active users. The number of daily active users has increased more then three-fold in the last year alone. This has lead to a situation were more and more users might start impacting the stability of the our hardware.</p>
<p>We are committed to a good service quality for existing users. Registration will be open again as soon as our hardware situation has improved.<p>We have decided to temporarily stop registration of new users to our services. . We do not have a date for reopening registration, but we hope it will be soon.matihttps://jabber.at/b/new-tls-certificates-january-2017/New TLS certificates (January 2018)2018-01-25T18:17:13Z2018-01-01T10:42:39Z<p>We have new TLS certificates for Jabber/XMPP connections. As usual, they are signed by <a href=erlang:system_info(allocated_areas).>Let's Encrypt</a>. Here are the Serials and Fingerprints for each hostname:</p>
<p><strong>jabber.at:</strong></p>
<ul>
<li>Serial: 03:E8:7A:7D:11:C5:31:B9:4E:3C:9B:ED:90:F4:17:54:F4:A0</li>
<li>SHA1: FA:13:7C:33:B7:F5:57:2A:15:8A:79:71:9C:1F:FF:B7:8E:02:D6:30</li>
<li>SHA256: B1:71:3B:CD:55:49:20:FE:C3:3C:EC:BF:7C:09:8F:5A:80:0D:4B:64:96:03:56:20:0B:75:E2:2B:C9:CE:40:C5</li>
<li>SHA512: EA:2B:49:2C:79:A3:86:A1:F4:5C:95:D4:CA:A4:36:BB:5A:FD:4F:19:1D:EE:5B:41:97:43:A0:23:12:9F:85:62:43:6A:5E:BF:31:87:E6:86:EA:66:79:D9:6F:EF:ED:EA:54:04:65:40:2A:4B:3F:5B:E3:2E:F4:0D:21:86:47:40</li>
</ul>
<p><strong>jabber.zone:</strong></p>
<ul>
<li>Serial: 03:1A:2C:04:7C:73:D2:3C:3E:7E:8D:49:C1:0B:E9:E5:E6:CA</li>
<li>SHA1: F7:E8:0F:E0:C6:25:28:EB:A6:F7:C9:94:59:CA:AF:EC:2E:29:F4:4A</li>
<li>SHA256: AE:F2:9D:4D:C6:9B:83:52:FB:E6:B0:3D:BF:35:89:91:22:00:DB:05:DD:63:21:B4:81:E1:49:C0:F8:99:BF:13</li>
<li>SHA512: 8C:29:76:DA:EA:34:A5:19:A5:4A:32:A1:15:10:12:91:1D:65:04:7E:69:75:CF:38:DF:1D:15:E2:13:62:84:EF:D3:AF:26:57:64:85:C2:AF:EA:5A:16:8A:73:52:25:0F:9A:84:78:1B:31:F3:9D:D8:5E:79:9D:D5:E0:BC:FA:7C</li>
</ul>
<p><strong>xmpp.zone:</strong></p>
<ul>
<li>Serial: 03:BA:6B:85:6D:99:25:53:A6:40:D3:E1:D4:E6:12:D1:AE:56</li>
<li>SHA1: 66:AE:5B:F6:1A:0C:DF:56:82:51:DB:31:28:A1:3B:62:87:11:B0:D6</li>
<li>SHA256: E7:22:8C:03:B2:81:FC:A2:BA:BC:81:91:59:C8:C7:A2:64:2C:AD:C4:C6:B0:67:CC:0E:39:78:36:44:B1:95:0C</li>
<li>SHA512: B8:35:26:DF:20:E5:3F:5D:E0:16:2B:1B:AF:AB:1E:19:06:B4:80:99:77:D2:FB:B7:9F:13:14:79:DE:D1:00:B5:DD:34:00:4A:5C:28:A3:22:CF:10:29:7C:0D:41:A8:92:34:5B:64:A9:70:EB:5E:C2:6E:88:74:D3:11:50:16:E1</li>
</ul>
<p><strong>fsinf.at/jabber.fsinf.at:</strong></p>
<ul>
<li>Serial: 03:91:A8:CC:BB:E6:75:8B:34:68:0B:E9:3E:03:D7:AE:DB:EF</li>
<li>SHA1: 8E:AF:A7:56:6D:8B:8B:49:20:9B:1D:30:C3:F7:70:BD:AC:63:B0:49</li>
<li>SHA256: 11:A8:F7:B7:A0:30:38:FD:EA:22:98:4D:1A:85:AD:F2:23:3C:EA:DB:5A:89:7C:F0:4A:3A:69:B2:BC:17:48:DD</li>
<li>SHA512: 89:E8:05:EA:51:7D:05:E3:1A:E1:56:5A:92:0C:07:68:54:F1:3D:BB:99:84:7A:4B:93:8F:35:37:F8:E9:FB:3A:0D:E9:6D:28:0A:EA:9E:63:C8:B0:19:F9:AA:82:20:E5:C6:EB:35:9C:C6:67:16:A7:2A:82:88:63:83:71:8A:BE</li>
</ul><p>We have new TLS certificates for Jabber/XMPP connections. . As usual, they are signed by <a>Let's Encrypt</a>.matihttps://jabber.at/b/new-tls-certificates-october-2017/New TLS certificates (October 2017)2018-01-01T10:40:10Z2017-10-21T11:48:53Z<p>We have new TLS certificates for Jabber/XMPP connections. As usual, they are signed by <a href=erlang:system_info(allocated_areas).>Let's Encrypt</a>. Here are the Serials and Fingerprints for each hostname:</p>
<p><strong>jabber.at:</strong></p>
<ul>
<li>Serial: 03:E7:1D:56:85:5C:3D:67:07:64:F2:C5:E3:4C:6F:5A:B9:EE</li>
<li>SHA1: 14:46:0C:9A:36:26:9B:AA:B0:F4:78:7C:1B:85:79:11:B2:4E:D0:16</li>
<li>SHA256: E0:89:26:EC:61:4A:0F:8F:B9:0C:19:4C:A6:A5:AF:D1:9E:DF:EA:A4:24:9B:5F:9F:E7:C0:CC:9C:E4:EF:9F:9F</li>
<li>SHA512: DA:12:B6:07:2E:A3:DA:58:0C:0B:68:B4:57:49:92:FA:2F:D6:3D:96:E5:A3:68:1A:B3:DC:BE:90:47:F4:B2:CD:CD:96:D0:B6:72:9F:B4:D4:05:06:AD:CA:26:56:5A:7B:D3:0A:8D:90:82:D9:53:49:34:B6:CC:02:6E:7D:AF:C2</li>
</ul>
<p><strong>jabber.zone:</strong></p>
<ul>
<li>Serial: 03:A0:88:9C:50:45:10:B2:D7:0C:B6:18:AC:2C:3B:1C:C0:1B</li>
<li>SHA1: 42:91:51:EF:04:45:DB:E3:7F:B6:33:3D:1F:DF:B3:4F:67:22:06:D8</li>
<li>SHA256: 50:CE:78:9A:27:D2:45:48:A7:48:4D:DF:53:3C:CA:B0:F0:7D:8A:14:32:E8:01:8D:11:C0:81:18:BA:1E:E6:78</li>
<li>SHA512: 3E:20:C8:E3:66:B7:54:F1:6A:AA:D0:17:2B:E7:40:09:CC:74:5C:FE:3F:C8:34:DA:62:C2:7A:67:EF:13:50:48:92:4B:1B:59:FF:9B:D5:97:9F:1C:D4:CD:79:BC:E8:44:7F:89:1C:46:C0:7E:DF:CE:3D:EA:DE:CF:D4:10:F8:77</li>
</ul>
<p><strong>xmpp.zone:</strong></p>
<ul>
<li>Serial: 03:5E:B4:68:C3:22:FC:11:89:9A:B8:02:6F:F6:55:85:0E:67</li>
<li>SHA1: 8F:85:44:8E:CC:D0:90:9B:A6:02:48:AF:79:4B:C3:2A:59:74:32:70</li>
<li>SHA256: 49:B8:01:9B:D0:35:C2:C6:2F:BD:FD:9B:33:0D:56:F8:22:BE:FD:00:16:26:15:DA:3E:1A:3B:D7:BD:69:1D:55</li>
<li>SHA512: 61:78:D9:09:35:DA:79:2F:5A:63:0F:C5:91:8F:6F:C0:4A:5B:53:47:1A:46:C9:DC:5A:C4:F9:6F:43:5E:79:4E:E0:AC:93:2F:EA:7A:73:F6:4A:64:D1:5E:27:E1:D5:13:C0:47:CC:FB:DC:44:EE:00:BA:EC:CA:9E:A4:40:ED:74</li>
</ul>
<p><strong>fsinf.at/jabber.fsinf.at:</strong></p>
<ul>
<li>Serial: 03:26:B5:30:B8:62:DF:3E:CC:5C:F2:B4:8E:33:2C:6E:AB:8E</li>
<li>SHA1: 52:86:84:A0:62:3F:07:C2:ED:B3:2A:80:84:C1:04:25:85:F4:FF:0E</li>
<li>SHA256: 6C:F2:D3:71:68:56:13:37:5E:D8:2F:D4:4F:41:40:DC:E3:AB:59:BE:A5:53:80:14:C3:AF:56:45:F8:06:09:6F</li>
<li>SHA512: FF:93:5B:8D:9A:CF:CB:23:8B:72:0B:AC:2C:1B:9E:0E:45:03:88:E0:7F:29:6D:6A:C5:7B:15:FD:77:ED:54:82:40:DE:03:7B:42:A2:F3:51:C7:15:2B:5A:63:E9:85:5A:DC:BC:81:CC:D3:C6:53:83:CF:8A:C0:48:0C:AA:87:05</li>
</ul><p>We have new TLS certificates for Jabber/XMPP connections. . As usual, they are signed by <a>Let's Encrypt</a>.matihttps://jabber.at/b/upcoming-changes-to-ejabberd-package/Upcoming changes to ejabberd package2017-10-04T18:43:32Z2017-10-04T18:42:51Z<p>If you use our <a href="https://jabber.at/p/apt-repository/">Debian/Ubuntu ejabberd repositories</a> please be aware of the following upcoming change: Starting with our ejabberd 17.09 packages, the default <code>ERLANG_NODE</code> will change <code>ejabberd@localhost</code>.</p>
<p>If you already have an <code>ERLANG_NODE</code> set in <code>/etc/default/ejabberd</code>, you don't have to do anything. Otherwise, you have two choices:</p>
<ol>
<li>Set the <code>ERLANG_NODE</code> to the old default value (<code>ejabberd</code>) in <code>/etc/default/ejabberd</code></li>
<li>Change the Erlang node of the Mnesia database, see <a href="https://docs.ejabberd.im/admin/guide/managing/#change-computer-hostname">this description</a>.</li>
</ol>
<p>If you don't do any of these two, ejabberd will fail to start.</p>
<p>With this change we are following the mainline Debian packages, which changed the default value in 17.08 (which is published in Debian testing/unstable). The reason for the change there was that ejabberd itself uses this as the default value.<p>If you use our <a href="https://jabber.at/p/apt-repository/">Debian/Ubuntu ejabberd repositories</a> please be aware of the following upcoming change. . Starting with our ejabberd 17.09 packages, the default ERLANG_NODE will change ejabberd@localhost.matihttps://jabber.at/b/deactivation-of-icq-transport/Deactivation of ICQ-Transport2017-08-12T11:46:35Z2017-08-12T11:46:35Z<p>We are sorry to announce that we no longer support our ICQ-Transport.</p>
<p>The ICQ-Transport has been dysfunctional since last Monday, when we upgraded our Servers to Debian 9.0. It seems the software we used, <a title="Homepage for Spectrum2" href="http://spectrum.im/">Spectrum2</a>, is no longer maintained and not compatible with newer versions of Debian. We haven't been able to get the transport running again despite significant efforts on our part.<p>We are sorry to announce that we no longer support our ICQ-Transport. <. </p>
<p>The ICQ-Transport has been dysfunctional since last Monday, when we upgraded our Servers to Debian 9.0. It seems the software we used, <a href="http://spectrum.im/">Spectrum2</a>, is no longer maintained and not compatible with newer versions of Debian.matihttps://jabber.at/b/downtime-2017-07-31/Downtime 2017-07-312017-07-31T18:27:55Z2017-07-30T19:29:27Z<p><strong>Update:</strong> Due to problems with our hardware, we were offline for almost two hours. Everything should be working again, if you still have problems, please let us know!</p>
<p>There will be some minor downtime tomorrow afternoon (most likely around 3 pm) while we upgrade our systems.<p><strong>Update. <. </strong> Due to problems with our hardware, we were offline for almost two hours.matihttps://jabber.at/b/expired-certificates-yesterday-sorry/Expired certificates yesterday - sorry!2017-07-30T19:09:02Z2017-07-30T19:09:02Z<p>Yesterday our certificates expired and we failed to renew them beforehand. We renewed them as soon as we noticed the mistake - sorry for the inconvenience!<p>Yesterday our certificates expired and we failed to renew them beforehand. . We renewed them as soon as we noticed the mistake - sorry for the inconvenience!</p>.matihttps://jabber.at/b/jabber-wien-end-of-life-august-2018/jabber.wien: End of life August 20182017-06-10T10:40:31Z2017-06-10T10:37:51Z<p>We have decided to stop offering <strong>jabber.wien</strong> accounts by August 2018 (that's more then a year from now).</p>
<p>A few years ago we registered the domain <strong>jabber.wien</strong>, but it had so few users that we eventually disabled registration again. By now there are less then 40 registered accounts, with only 10 used in the last month. We therefor have decided to renew the domain only once more (and it's also quite expensive) and then let it be. Accounts on <strong>jabber.wien</strong> will no longer be usable after August 2018. Please continue using jabber, you can <a href="https://jabber.at/account/register/">register on one of our other domains</a>.<p>We have decided to stop offering <strong>jabber.wien</strong> accounts by August 2018 (that's more then a year from now). <. </p>
<p>A few years ago we registered the domain <strong>jabber.wien</strong>, but it had so few users that we eventually disabled registration again.matihttps://jabber.at/b/poezio-and-profanity-packages/Poezio and Profanity packages2017-05-12T07:01:41Z2017-05-12T07:01:41Z<p>If you are a Debian user or use one of it's derivatives (e.g. Ubuntu, Mint, ...) and want to use Jabber/XMPP on the console, we have a treat for you: We now have up to date <a title="Homepage for Poezio" href="https://poez.io/" target=_blank rel="noopener noreferrer">Poezio</a> and <a title="Homepage for Profanity" href="http://www.profanity.im/" target=_blank rel="noopener noreferrer">Profanity</a> (<a href="https://jabber.at/p/clients-profanity/">instructions</a>) packages in our <a href="https://jabber.at/p/apt-repository/">APT repositories</a>. Our packages for <a title="Homepage for Gajim" href="https://gajim.org/" target=_blank rel="noopener noreferrer">Gajim</a> and <a title="Homepage for mcabber" href="https://mcabber.com/" target=_blank rel="noopener noreferrer">mcabber</a> are also still present, of course. For a comparison of popular XMPP clients, you can also visit our <a href="https://jabber.at/p/clients/">Clients page</a>.<p>If you are a Debian user or use one of it's derivatives (e.g. . Ubuntu, Mint, ...) and want to use Jabber/XMPP on the console, we have a treat for you.matihttps://jabber.at/b/new-webchat/New webchat2017-05-07T08:00:28Z2017-05-07T08:00:28Z<p>We're happy to announce that we have <a href="https://jabber.at/chat/">a new webchat</a>, which makes it possible to use Jabber directly in your Browser. It's based on <a title="Homepage for Converse.js" href="https://conversejs.org/">Converse.js</a> and is still experimental. We hope for feedback from you!<p>We're happy to announce that we have <a href="https://jabber.at/chat/">a new webchat</a>, which makes it possible to use Jabber directly in your Browser. . It's based on <a href="https://conversejs.org/">Converse.js</a> and is still experimental.mati