* Ported to GTK3 / Python3Congratulations!
* Flatpak support
* Lots of refactoring
* New Emoji support
* New Chat Window design
* New StartChat Window (Ctrl+N)
* New ServerInfo Window
* AccountWindow Redesign
* Moved some encryption code out into Plugins (see PGP Plugin, Esessions Plugin)
* OTR Plugin was not ported, use OMEMO
* Added mam:1 and mam:2 support (mam:0 was removed)
* Added MAM for MUCs support
* Added support for showing XEP-0084 Avatars
* Added xmpp URI handling directly in Gajim
* Removed Gajim-Remote
* Removed XEP-0012 (Last Activity)
* Removed XEP-0136 (Message Archiving)
* Added XEP-0156 (Discovering Alternative XMPP Connection Methods)
* Added XEP-0319 (Last User Interaction in Presence)
* Added XEP-0380 (Explicit Message Encryption)
* Added Jingle FT:5 support
Q: What motivated you to develop Conversations?#conversations #freesoftware #xmpp #android #interview #pgp #otr #omemo #forwardsecrecy #xda
A: I am using Jabber/XMPP for many many years. Even back in 2009 I was able to use Jabber on my Nokia e71. Sometime around the year 2012 I switched to an Android phone, so I suddenly was unable to use Jabber. [...]
Q: Can you give three reasons why Conversations protects your privacy better than Whatsapp or Threema?
A: I don’t have to give my private phone number to strangers if I want to chat with them. I could have a private and a business account. I can disable the business account after my shift, to prevent my boss from annoying me during my free time. WhatsApp allows everybody to analyze my app usage patterns any time. (My boss could stalk me to investigate if I am using WhatsApp during my working hours or if I am using WhatsApp at night instead of sleeping and coming well rested to the office.) This is different with Conversations; Conversations also doesn’t upload my entire address book to Facebook.
Q: Is it allowed to compile Conversations on your own from your Github and use it for private use?
A: Of course. Not only private, also for business and everything else you want. It is also allowed to modify the code to meet individual requirements.
Movim is a distributed social networking platform founded in 2010. It can be accessed using existing XMPP clients and Jabber accounts, and is a free and open source software licensed under the AGPL.#movim #ejabberd #socialnetwork #federation #xmpp #agpl #prosody #debian #freesoftware
With version 0.12 released in October, Movim migrated its official server to ejabberd. Before, they were using Metronome, a Prosody fork. Today, we are chatting with Timothée Jaussoin, the founder of Movim, about this very complex migration.
We now have a proper packaging for our Linux distribution – Debian, which certainly makes it easier to maintain. There’s also an improved scalability and more stable CPU and memory consumption, which helps to predict hardware requirements.
Even if I see ejabberd more as a tool that needs integration and tuning to create a proper platform, ejabberd seems to be the more serious solution to build proper messaging systems using the XMPP protocol.
Dear developers,#debian #freesoftware #sourcecode #search #development #debsources #python #agpl3
We're happy to announce that Debsources, the Web application that
allows to browse and search the entire source code of all Debian
releases, is now hosted on the official Debian infrastructure and
available at https://sources.debian.org.
You may already know this service as previously hosted at
sources.debian.net . We took the move to Debian hardware as the
opportunity to officially announce it here.
Debsources is a web service that exposes the content of Debian source
packages on the Web, both via an HTML user interface and a JSON API
. To that end, an updater runs regularly (currently 4 times a day)
to unpack and index new packages from all the available Debian
suites. It also runs various plugins, for example to count lines of
code and measure the size of packages; this information is exposed in
Since all extracted information is stored in a PostgreSQL database,
various data warehouse features are available, such as the list of
file duplicates for every file, or package name search.
More than source code
Worth noting are two "sub-apps" that run on the same infrastructure:
* patches : for packages using 3.0 (quilt) package format, the list
of patches is extracted and exposed, along with some metadata.
* copyright : the copyright files of packages are exposed through
this interface, and displayed in a convenient way if they are
Debsources has been described extensively and used to conduct various
studies on the Debian source code. To learn more check out the paper:
Matthieu Caneill, Daniel M. Germán, Stefano Zacchiroli. The Debsources
Dataset: Two Decades of Free and Open Source Software. In Empirical
Software Engineering, Volume 22, pp. 1405-1437, June, 2017
An open access preprint of the paper and additional information about
Debsources are available on the Debsources documentation page .
Many credits go to everyone who submitted patches and feedback over
the years, thank you! In particular, Stefano Zacchiroli started the
project and wrote the updater infrastructure, and Orestis Ioannou
developed the patches/ and copyright/ apps.
This new instance of the service is hosted by DSA - without whom
sources.debian.org would not exist. Many thanks to the whole team for
their guidance in the d.n -> d.o migration, and in particular to
Julien Cristau and Peter Palfrader.
The previous instance of Debsources had been hosted by IRILL for
more than 4 years, who has also spearheaded the initial development of
the service - thanks for the non-interrupted service!
As always, we're more than happy to hear your feedback; you can
contact us at firstname.lastname@example.org . (See the footer
of the Debsources web page for bug report and contribution
For the Debsources team,
There is also a short demo video. Nice!
- it's decentralized and federated, no need to have X accounts to use X tickets handlers. You can also import tickets from third party projects (e.g. plugins for your project) into your website.
- it's standard: we can handle or fetch tickets in third party servers easily, without proprietary API.
- it's very flexible: any field can be used, and the mechanism can be used for any list (bug tracker, TODO list, shopping list, etc.)
- being based on SàT, it's usable on any platform
- it can be used with gateways, allowing to use transparently tickets from other services (think about Gitlab or Github for instance)
Each time I see the FSFE picture, just like on Daniel’s last post to planet.d.o, where it says:#cloud #freesoftware #openstack #fsfe #debian #privacy
“There is NO CLOUD, just other people’s computers”
it makes me so frustrated. There’s such a thing as private cloud, setup on your own set of servers. I’ve been working on delivering OpenStack to Debian for the last 6 years and a half, motivated exactly to fix this issue: I refuse that the only cloud people could use would be a closed source solution like GCE, AWS or Azure. The FSFE (and the FSF) completely dismissing this work is more than annoying: it is counter productive. Not only the FSFE shouldn’t pull anyone away from the cloud, but it should push for the public to choose cloud providers using free software like OpenStack.
The openstack.org market place lists 23 public cloud providers using OpenStack, so there is now no excuse to use any other type of cloud: for sure, there’s one where you need it. If you use a free software solution like OpenStack, then the question if you’re running on your own hardware, on some rented hardware (on which you deployed OpenStack yourself), or on someone else’s OpenStack deployment is just a practical one, on which you can always back-up quickly. That’s one of the very reason why one should deploy on the cloud: so that it’s possible to redeploy quickly on another cloud provider, or even on your own private cloud. This gives you more freedom than you ever had, because it makes you not dependent anymore on the hosting company you’ve selected: switching provider is just the mater of launching a script. The reality is that neither the FSFE or RMS understand all of this. Please don’t dive into the FSFE very wrong message.
Btw., the server searx.me seems to get slower and slower, because too many people use it. Please consider to use other entities of searx and - if you care for your privacy - use different servers alternating. There is a simple hack to automatically change the searx entity to use with every search, see here, here, and here.
- New theme: simple
- New engines
- Google videos (video)
- Bing videos (video)
- Arxiv (science)
- OpenAIRE (science)
- Pubmed (science)
- Genius (music/lyrics)
- Display engine errors
- Faster startup
- Lots of engine fixes (google images, dictzone, duckduckgo, duckduckgo images, torrentz, faroo, digg, tokyotoshokan, nyaa.si, google news, gitlab, gigablast, geektimes.ru, habrahabr.ru, voat.co, base, json engine, currency convert, google)
- Shorter saved preferences URL
- Fix engine duplications in results
- Py3 compatibility fixes
- Translation updates
A little more than a month ago I wrote how to observe the SIM card ID (aka IMSI number) of mobile phones talking to nearby mobile phone base stations using Debian GNU/Linux and a cheap USB software defined radio, and thus being able to pinpoint the location of people and equipment (like cars and trains) with an accuracy of a few kilometer. Since then we have worked to make the procedure even simpler, and it is now possible to do this without any manual frequency tuning and without building your own packages....
The gr-gsm package is now included in Debian testing and unstable, and the IMSI-catcher code no longer require root access to fetch and decode the GSM data collected using gr-gsm.
Here is an updated recipe, using packages built by Debian and a git clone of two python scripts: