Ignite Realtime Blog: Botz version 1.2.0 release
We have just released version 1.2.0 of the Botz framework for Openfire!
The Botz library adds to the already rich and extensible Openfire with the ability to create internal user bots.
In this release, a bug that prevented client sessions for bots from being created was fixed. Hat-tip to
Kris Iyer for working with us on a fix!
Download the latest version of the Botz framework from [its project page](https://www.igniterealtime.org/projects/botz/ … ⌘ Read more
Okay, so I spent about one hour setting up cmake, fltk and libcurl for c++, got all that running now.
I still need to fix the cmake script a bit, but I have a working verison now with this.
I will now add the same curl stuff I had in rust in c++, then work on the gui and all that.
So I will drop rust, and go for c++ instead, much easier for me. Was worth a try in rust, but for now that’s not for me to be honest, I much faster and better in c++.
[47°09′59″S, 126°43′16″W] Transponder fixed
[47°09′59″S, 126°43′27″W] Dosimeter fixed
Lindypress Bug Fix
Just a brief note that for the past couple of days, you might’ve been unable to buy books on LindyPress.net if you are in the United States, Canada or Australia (which is a lot of you). This has now been fixed, so you can place your orders now!
The issue was that there was a silent API update that kept addresses from validating states and provinces. Note that if your order placed, it’s all okay, this is only for people for whom the site would not let place an order.
… ⌘ Read more
Prosodical Thoughts: Prosody 0.12.3 released
We are pleased to announce a new minor release from our stable branch.
This is a bugfix release for our stable 0.12 series. Most notably, it fixes a
regression for SQL users introduced in 0.12.2, and a separate long-standing
compatibility issue with archive stores on certain MySQL/MariaDB versions.
It also fixes an issue with websockets discovered by the Jitsi team, some
issues with our internal HTTP client API, and we’ve improved the accuracy of
‘prosodyctl check dns’ in … ⌘ Read more
[47°09′05″S, 126°43′21″W] Transponder fixed
Okay one last time, then I’m going to bed, let’s hope this is the final bug that fixes Yarn/Twtxt <-> Activity Pub integration 😅
I should probably fix that
[47°09′38″S, 126°43′32″W] Dosimeter fixed
[47°09′55″S, 126°43′44″W] Dosimeter fixed
[47°09′50″S, 126°43′04″W] Transponder fixed
Gajim: Gajim 1.7.0
Gajim 1.7.0 is mostly a bug fixing release. Due to fundamental changes in the build system, we decided to jump from 1.6.x to 1.7 directly. Thank you for all your contributions!
Gajim’s build system had significant changes, which makes it necessary for package maintainers to change some things, as documented in the readme file.
More Changes- Account creation: Don’t allow to add account twice
- File previews: Y … ⌘ Read more
[47°09′06″S, 126°43′29″W] Dosimeter fixed
[47°09′00″S, 126°43′44″W] Transponder fixed
[47°09′30″S, 126°43′40″W] Transponder fixed
[47°09′35″S, 126°43′09″W] Dosimeter fixed
My motivation to work on GoBlog isn’t always the same. Sometimes I don’t feel like programming in my free time, so the most I do is some bug fixing when I find broken things. Sometimes I just have no time to work on new features or improvements. But since yesterday evening I feel a new push and have completely rewritten the plugin system to make it much more flexible (and I like flexibility). I had to break compatibility with existing plugins, but given the small user base and the limited scope of what plugins could … ⌘ Read more
[47°09′16″S, 126°43′21″W] Dosimeter fixed
[47°09′02″S, 126°43′37″W] Transponder fixed
Highlights from the BuildKit v0.11 Release
Docker BuildKit v0.11 is now available with new features, bug fixes, performance improvements, and more! ⌘ Read more
ProcessOne: ejabberd 23.01
Almost three months after the previous release, ejabberd 23.01 includes many bug fixes, several improvements and some new features.
A new module, mod_mqtt_bridge, can be used to replicate changes to MQTT topics between local and remote servers.
A more detailed explanation of those topics and other features:
Erlang/OTP 19.3 discouragedRemember that support for Erlang/OTP 19.3 is discouraged, and will b … ⌘ Read more
ProcessOne: ejabberd 23.01
Two months after the previous release, ejabberd 23.01 includes many bug fixes, several improvements and some new features.
A new module, mod_mqtt_bridge, can be used to replicate changes to MQTT topics between local and remote servers.
A more detailed explanation of those topics and other features:
Erlang/OTP 19.3 discouragedRemember that support for Erlang/OTP 19.3 is discouraged, and will be removed … ⌘ Read more
ProcessOne: ejabberd 23.01
Two months after the previous release, ejabberd 23.01 includes many bug fixes, several improvements and some new features.
A new module, mod_mqtt_bridge, can be used to replicate changes to MQTT topics between local and remote servers.
A more detailed explanation of those topics and other features:
Erlang/OTP 19.3 discouragedRemember that support for Erlang/OTP 19.3 is discouraged, and will be removed … ⌘ Read more
Finally back! My VPS’s main drive got toasted. I got a freshly installed VPS now, got yarn set up and working now, now I have to fix the rest of the stuff.
I’ve been using apache for many many years, but I had so many issues getting it set up today, so I switched to nginx, and that took me like 2 minutes.. So yeah - I’ll use nginx from now on.
[47°09′36″S, 126°43′50″W] Dosimeter fixed
Gajim: Gajim 1.6.1
Gajim 1.6.1 is mostly a bug fixing release, but it also brings some important improvements and adds more convenience. Thank you for all your contributions!
After we ported Gajim and python-nbxmpp to libsoup3, you might have noticed issues with file transfers. Now, python-nbxmpp 4.0.1 has been released, and it fixes an error which prevented transfers of files containing spaces in their file name.
Gajim s … ⌘ Read more
[47°09′39″S, 126°43′46″W] Transponder fixed
[47°09′20″S, 126°43′49″W] Dosimeter fixed
Gajim: Gajim 1.6.0
For Gajim 1.6.0 we ported Gajim’s and python-nbxmpp’s underlying HTTP library to libsoup3. Also, audio previews now look nicer and allow for more control (playback speed, jumping). We fixed emoji rendering on MacOS and we implemented many fixes under the hood. Thank you for all your contributions!
For all HTTP requests (e.g. file downloads, update checks, websocket connection, …) both Gajim and python-nbxmpp rely on libsoup. With Gajim 1.6.0, we ported to libsoup3. You shou … ⌘ Read more
[47°09′12″S, 126°43′33″W] Transponder fixed
[47°09′45″S, 126°43′59″W] Dosimeter fixed
Almost MIPS-only session today! Actually, I also briefly ran my PowrBook G4 and the Gemini PDA in attempt to fix my Pebble. But mostly the SGI O2 and the Indigo, too!
[47°09′34″S, 126°43′49″W] Dosimeter fixed
Prosodical Thoughts: Prosody 0.12.2 released
We are pleased to announce a new minor release from our stable branch.
This is a regularly delayed release containing a number of fixes for
issues that we have come across since the last release of the 0.12
series.
A summary of changes in this release:
Fixes and improvementsIgnite Realtime Blog: Spark 3.0.1 Released
The Ignite Realtime community is happy to announce the release of Spark 3.0.1 version.
This release contains mostly fixes. macOS now uses the default FlatLaf LaF. The user can also choose the type of tabs “scroll” as in Spark 3.0.0 or “wrap” as in Spark 2.X. See screenshot below. And also for some users, Spark not saved history.
… ⌘ Read more
[47°09′38″S, 126°43′31″W] Dosimeter fixed
[47°09′55″S, 126°43′20″W] Dosimeter fixed
Gajim: Gajim 1.5.4
Gajim 1.5.4 comes with a reworked file transfer interface, better URL detection, message selection improvements, and many fixes under the hood. Thank you for all your contributions!
Gajim’s interface for sending files has been reworked, and should be much easier to use now. For each file you’re about to send, Gajim will generate a preview. This way, you can avoid sending the wrong file to somebody. Regardless of how you start a file transfer, be it drag and drop, pasting a … ⌘ Read more
Find and Fix Vulnerabilities Faster Now that Docker’s a CNA
Docker is now officially a CNA under MITRE, which means you should get better notifications and documentation when we publish a vulnerability. ⌘ Read more
[47°09′03″S, 126°43′20″W] Dosimeter fixed
always something broken to fix, too
Écologie punitive, suite : 4 vols aérien dans votre vie, point.
La COP27 vient de s’achever et, bien qu’il soit difficile de ne pas se réjouir devant les mines déconfites des participants qui ont, tous, conclu que les objectifs (dangereux) fixé (arbitrairement) ne seraient pas atteints, il ne faut pas oublier que cette déconfiture sera justement utilisée par les ayatollahs de la religion verte pour réclamer […] ⌘ Read more
I reworked the current ActivityPub implementation of GoBlog, fixed ActivityPub replies to posts and also added support for reply updates and deletions. Under the hood it’s using the comment system. 🥳 Using the go-ap/activitypub library, working with ActivityPub is much easier (but still more complicated than I wish it would be). ⌘ Read more
Ignite Realtime Blog: Openfire Monitoring Service plugin 2.4.0 release
Earlier today, we have released version 2.4.0 of the Openfire Monitoring Service plugin. This plugin adds both statistics, as well as message archiving functionality to Openfire.
In this release, compatibility with future versions of Openfire is added. A bug that affects MSSQL users has been fixed, and the dreaded “Unable to save XML properties” error message has been resolved. A few other minor tweaks h … ⌘ Read more
[47°09′51″S, 126°43′39″W] Transponder fixed
[47°09′13″S, 126°43′14″W] Dosimeter fixed
@prologic@twtxt.net git worked after upgrade. But I seem to have to reinstall go. I have not done that yet. I will see if I have time to fix that later tonight.
I have found the issue with this very subtle bug.. the cache was returning a slice that would be mutated. The mutation involved appending an item and then sorting. because the returned slice is just a pointer+length the sort would modify the same memory.
CACHE Returned slice
original: [A B C D] [A B C D]
add: [A B C D] E [A B C D E]
sort: [E A B C] D [A B C D E]
fix found here:
https://git.mills.io/yarnsocial/yarn/pulls/1072
I have found the issue with this very subtle bug.. the cache was returning a slice that would be mutated. The mutation involved appending an item and then sorting. because the returned slice is just a pointer+length the sort would modify the same memory.
CACHE Returned slice
original: [A B C D] [A B C D]
add: [A B C D] E [A B C D E]
sort: [E A B C] D [A B C D E]
fix found here:
https://git.mills.io/yarnsocial/yarn/pulls/1072
** Occasional notes **
If they aren’t weekly, I guess they’re occasional?
3rd repair procedure to fix brain bleed was a success. I have a few more scans and follow ups, but, knock wood I think I’m through at this point.
I’ve spent about a week laying low and taking it easy navigating some wild pain, but that is subsiding now. I watched a bunch of stuff. It was a nice change of pace. I don’t typically watch much television or many movies. Stand outs (all things I revisited) include:
- Michael Clayton
- Point Break, the o … ⌘ Read more
[47°09′07″S, 126°43′53″W] Dosimeter fixed
Hmmm, after fixing my feeds to move the <author> from <entry>s to <feed>, Newsboat marked all old affected articles as unread. IDs were untouched, of course. Need to investigate that. Had something similar happen with another feed change I did some time ago. Can’t remember what that was, though.
@mckinley@twtxt.net Thank you! I didn’t even know about signing and encrypting XML documents. Right, RSS is a little bit messy.
Unfortunately, the autodiscovery document in one of your linked resources does not exist anymore. What annoys me in Atom is the distinction between <id> and <link>. I always want my URL also to be my ID, so I have to duplicate that – unnecessarily in my opinion.
Also, never found a good explanation why I should add <link rel="self" … /> to my feeds. I just do, but I don’t understand why. The W3C Feed Validation Service says:
[…] This value is important in a number of subscription scenarios where often times the feed aggregator only has access to the content of the feed and not the location from which the feed was fetched.
This just sounds like a very questionable bandaid to bad software architecture. Why would the feed parser need access to the feed URL at this stage? And if so, why not just pass down the input source? Just doesn’t make sense to me.
Also, I just noticed that I reference the http://purl.org/rss/1.0/modules/syndication/ namespace, but don’t use it in most of my feeds. Gotta fix that. Must have copied that from my yfav feed without paying attention what I’m doing.
Your article made me reread the Atom spec and I found out, that I can omit the <author> in the <entry> when I specify a global <author> at <feed> level. Awesome! Will do that as well and thus reduce the feed size.
Ignite Realtime Blog: Openfire 4.7.4 release
The Ignite Realtime Community is happy to announce the 4.7.4 release of Openfire. This release fixes a number of bugs and represents our effort to provide a stable 4.7.x series while work continues on the next feature release of Openfire.
Notable fixes include enhancements to cluster-specific implementation of Multi-User Chat functionality, improved websocket handling and improv … ⌘ Read more
[47°09′31″S, 126°43′56″W] Dosimeter fixed
[47°09′55″S, 126°43′02″W] Dosimeter fixed
[47°09′52″S, 126°43′00″W] Dosimeter fixed
ProcessOne: ejabberd 22.10
This ejabberd 22.10 release includes six months of work, over 140 commits, including relevant improvements in MIX, MUC, SQL, and installers, and bug fixes as usual.
This version brings support for latest MIX protocol version, and significantly improves detection and recovery of SQL connection issues.
There are no breaking changes in SQL schem … ⌘ Read more
ProcessOne: ejabberd 22.10
This ejabberd 22.10 release includes five months of work, over 120 commits, including relevant improvements in MIX, MUC, SQL, and installers, and bug fixes as usual.
This version bring support for latest MIX protocol version, and significantly improves detection and recovery of SQL connection issues.
There are no breaking changes in SQL schem … ⌘ Read more
Security Advisory: Critical OpenSSL Vulnerability
The OpenSSL Project will imminently release a security fix (OpenSSL version 3.0.7) for a new-and-disclosed CVE. In the meantime, learn how Docker tooling helps you uncover and remediate image vulnerabilities. ⌘ Read more
[47°09′32″S, 126°43′49″W] Dosimeter fixed
[47°09′21″S, 126°43′26″W] Transponder fixed
How to Fix and Debug Docker Containers Like a Superhero
While containers help developers rapidly build and run cross-platform applications, creating error-free apps remains a constant challenge. And while it’s not always obvious how container errors occur, this mystery is even harder for newer developers to unravel. Figuring out how to debug Docker containers can seem daunting. In this Community All-Hands session, Ákos Takács demonstrated how […] ⌘ Read more
After all, debugging is still fun!
One reason I use an Android smartphone is that there are apps like Indigenous (a MicroPub-compatible app for posting from your phone to a MicroPub-compatible blog). And even if the app ever disappears from the store, there’s still the option to manually install the app. And if you need to, you can also develop your own apps without having to invest nearly $100 a year. ⌘ Read more
[47°09′51″S, 126°43′49″W] Dosimeter fixed
Welcome back, @quark@ferengi.one! Your web server doesn’t send back a Last-Modified header for your feed, so the official twtxt client complains not to cache it. I just fixed that, so that tt shows your feed (of course no progress has been made in the meantime). And the Date header of your server seems to be quite funny, too. ;-)
[47°09′34″S, 126°43′42″W] Transponder fixed
[47°09′26″S, 126°43′58″W] Dosimeter fixed
Gajim: Gajim 1.5.2
Gajim 1.5.2 brings another performance boost, better emojis, improvements for group chat moderators, and many bug fixes. Thank you for all your contributions!
Generating performance profiles for Gajim revealed some bottlenecks in Gajim’s code. After fixing these, switching chats should now feel snappier than before.
Did you know that you can use shortcodes for typing emojis? Typing :+1 for example will ope … ⌘ Read more
[47°09′14″S, 126°43′09″W] Dosimeter fixed
[47°09′25″S, 126°43′51″W] Transponder fixed
[47°09′57″S, 126°43′35″W] Dosimeter fixed
[47°09′54″S, 126°43′39″W] Transponder fixed
[47°09′26″S, 126°43′14″W] Dosimeter fixed
[47°09′57″S, 126°43′14″W] Transponder fixed
[47°09′35″S, 126°43′57″W] Dosimeter fixed
RT by @mind_booster: The European Parliament has begun its discussions about corporations obligations to protect human rights and prevent environmental destruction in their value chains. Problem: a weak proposal due to pressure from lobby groups. 5 things the EP must fix: href=”https://txt.sour.is/search?q=%23HoldBizAccountable”>#HoldBizAccountable**
The European Parliament has begun its discussions about corporations obligations to protect human rights and prevent environmental destruction in their value chains. Problem: a weak proposal due to pressure from lobb … ⌘ Read more
[47°09′57″S, 126°43′23″W] Transponder fixed
A script for Go dependency updates
I regularly update the dependencies of my blog software, a Go based project. Dependency updates are important because they can contain security fixes or fixes for bugs. ⌘ Read more
[47°09′07″S, 126°43′05″W] Dosimeter fixed
@akoizumi@social.kyoko-project.wer.ee cool to see that you fixed the css
[47°09′01″S, 126°43′00″W] Dosimeter fixed
@abucci@anthony.buc.ci always nice with a easy fix!
[47°09′07″S, 126°43′33″W] Transponder fixed
[47°09′09″S, 126°43′02″W] Dosimeter fixed
@lyse@lyse.isobeef.org ¯\_(ツ)_/¯ fixed your arm.
@lyse@lyse.isobeef.org ¯\_(ツ)_/¯ fixed your arm.
[47°09′37″S, 126°43′52″W] Dosimeter fixed
Dependabot now alerts for vulnerable GitHub Actions
GitHub Actions gives teams access to powerful, native CI/CD capabilities right next to their code hosted in GitHub. Starting today, GitHub will send a Dependabot alert for vulnerable GitHub Actions, making it even easier to stay up to date and fix security vulnerabilities in your actions workflows. ⌘ Read more
[47°09′43″S, 126°43′15″W] Transponder fixed
[47°09′51″S, 126°43′14″W] Dosimeter fixed
Ignite Realtime Blog: REST API Openfire plugin 1.9.0 released!
We have released version 1.9.0 of the Openfire REST API plugin! This version adds functionality and provides some bug fixes that relates to multi-user chat rooms.
The updated plugin should become available for download in your Openfire admin console in the course of the next few hours. Alternatively, you can download the plugin directly, from [the plugin’s archive page](https://www.igniterealtime.org/projects/openfire/pl … ⌘ Read more
Ignite Realtime Blog: Openfire 4.7.3 released
The Ignite Realtime Community is pleased to announce the release of Openfire version 4.7.3. This version brings a number of bug fixes and other improvements and signifies our efforts to produce a stable 4.7 series of Openfire whilst work continues on the next feature release 4.8.0.
You can find download artifacts on our website with the fol … ⌘ Read more
[47°09′47″S, 126°43′48″W] Transponder fixed
[47°09′15″S, 126°43′41″W] Transponder fixed
[47°09′37″S, 126°43′21″W] Dosimeter fixed
Gajim: Gajim 1.4.7
Gajim 1.4.7 brings performance improvements, better file previews, and many bug fixes. Thanks for all your reports!
Multiple issues with Gajim’s file preview have been fixed. If you want to disable file previews entirely, there is now a setting in Gajim’s preferences.
For people with many contacts in their contact list, this release will bring a significant performance improvement 🚀
Furthermore, notifications on Windows should not appear in the taskbar anymore.
Fixes … ⌘ Read more