Recent searches
Search options
#pidgin
I am using #xmpp since the time of windows xp and #pidgin. It is sad to see how the ecosystem moved. On Linux the only client available is gajim (there is no realistic way to install dino on Linux Mint). I appreciate the work people do to make those clients but.. it has so much problems. Now it constantly crashes so my xmpp communication is almost gone. Or lets say, my xmpp usage is tied to my smartphone with "conversations" as client.
Well we've gone and done it! Pidgin 3.0.0 Experimental 2 has been released!! You can find the full release announcement on our discourse!
https://discourse.imfreedom.org/t/pidgin-3-0-experimental-2-2-91-0-has-been-released/262
Greetings Programs!!! It is release night for @pidgin 3.0 Experimental 2!! And we're getting a bit of a late start at that... So I better get to it then! Come join us!
So we had some issues in that Ibis 0.13.0 release which we've fixed in the 0.13.1 release!
Full release announcement is here! https://discourse.imfreedom.org/t/ibis-0-13-1-has-been-released/
Hey everyone, we just released version 0.13.0 of Ibis our #IRCv3 library that we've built for the #IRC support in @pidgin 3!
The big feature in this release is that we're parsing formatting and making it available to users of the library so they can display formatted messages. See the screen shot for what that looks like in Pidgin 3 experimental 2!!
You can find the official release announcement here! https://discourse.imfreedom.org/t/ibis-0-13-0-has-been-released
So @pidgin 3.0 Experimental 2 is due out on Monday and we realized we could probably sneaking message formatting in for #IRCv3 in the last few days.
This still needs some work, but check out the Pidgin 2 vs 3 handling of message formatting...
I thought we fixed the italics stuff in Pidgin 2 awhile, but apparently not.
Anyways this is all spec complaint per https://modern.ircdocs.horse/formatting
If you have any questions, comments, etc feel free!
Greetings Programs!! We're 3 days away from @pidgin 3.0 Experimental 2 and it's crunch time! Come on by and get crunched!!
Greetings Programs!! We're about 4 days away from @pidgin 3.0 Experimental 2! And while it doesn't look like we're going to get everything in that I wanted, we still have work to do!! So com on by!
Greetings Programs! We are 7 days away from @pidgin 3.0 Experimental 2! Unfortunately we're just out of time for some stuff I was really hoping to get done, but lets see what we can do with the remaining time!! Come on by!!
Greetings Programs!! We're back at it trying to get this @pidgin 3.0 Experimental 2 release in shape!! Come on by!!
Greetings Programs!! We're 14 days away from @pidgin 3.0 Experimental 2 and wow do I wish I had more time...
Anyways come watch me panic as I try to get everything in this release that I want to!!
Greetings Programs!! A late start tonight, but we're continuing on our path towards @pidgin 3.0 Experimental 2!! Come on by!!
@pidgin Also if anyone wants to explore more themselves, meson makes this really easy.
From the top of our source tree you can run meson with the following command
meson build -Db_coverage=true -Dgplugin:vapi=false build-coverage
The vala bindings need to be disabled because the confuse gcovr.
Once configuration is done you can run the tests and generate the coverage report with the following
cd build-coverage
ninja turtles
ninja coverage-html
@pidgin Some more info. Keep in mind that the 130 suites include libraries we maintain as well, but the code coverage here does not include.
Also, the coverage includes, libpurple, pidgin, and the protocol plugins and that pidgin and the protocol plugins aren't exactly testable although we have some stuff we're working on for that.
Holy crap! I just noticed we're up to 130 unit test suites in @pidgin 3 now! Compare that to the 7 suites we have in Pidgin 2!
This is what we've been talking about when we've been saying that we're making the code easier to maintain. The code has been reworked so that we can actually unit test way more of it and we will continue to add more tests as we move forward!
Anyone else as excited as much as I am for new message notifications in @pidgin 3?
This implementation is super hacky and not done the right now, but it works and will be in Experimental 2!
We'll still be working on the right implementation for this, but this is a nice stop gap even if it is buggy and shows events too 
Do you also think that #MicrosoftTeams is bloated? There is a lightweight alternative: use @pidgin with this libpurple plugin: https://github.com/EionRobb/purple-teams