KubeCon + CloudNativeCon Europe 2024 day two: how cloud native is powering the AI movement (and other news)
We had an exciting and busy start to KubeCon + CloudNativeCon Europe 2024. Here’s a look at some of the key moments of the day (and, spoiler alert: AI was the subject of a lot of conversation).  The… ⌘ Read more

Ignite Realtime Blog: Openfire inVerse plugin version 10.1.7.1 released!
We have made available a new version of the inVerse plugin for Openfire! This plugin allows you to easily deploy the third-party Converse client in Openfire. In this release, the version of the client that is bundled in the plugin is updated to 10.1.7.

The updated plugin should become available for download in your Openfire admin console in the course of the next few hours. … ⌘ Read more

** Valentines, patron saint of bees, plague, and sushi **
Hot on the heals of recently being interviewed by Manu, I was interviewed by Kristen Foster-Marks from the Developer Success Lab. It was a lot of fun! We had a wide ranging conversation, but often came back around to the importance of“learning … ⌘ Read more

Georg Lukas: Converse.js webchat for prosody-hosted chatrooms
The goal of this post is to make an easily accessible (anonymous)
webchat for any chatrooms hosted on a prosody XMPP
server, using the web client converse.js.

There are two use cases:

1. Have an easily accessible default support room for users having trouble with
   the server or their accounts.

2. Have a working “Join using browser” button on
   [search.jabber.network … ⌘ Read more

JMP: SMS Censorship
Since almost the very beginning of JMP there have been occasional SMS and MMS delivery failures with an error message like “Rejected for SPAM”. By itself this is not too surprising, since every communications system has a SPAM problem and every SPAM blocking technique has some false positives. Over the past few years, however, the incidence of this error has gone up and up. But whenever we investigate, we find no SPAM being sent, just regular humans having regular conversations. So what is happening here? Are … ⌘ Read more

JMP: SMS Censorship
Since almost the very beginning of JMP there have been occasional SMS and MMS delivery failures with an error message like “Rejected for SPAM”. By itself this is not too surprising, since every communications system has a SPAM problem and every SPAM blocking technique has some false positives. Over the past few years, however, the incidence of this error has gone up and up. But whenever we investigate, we find no SPAM being sent, just regular humans having regular conversations. So what is happening here? Are … ⌘ Read more

Pinellas County - Long Run: 13.30 miles, 00:11:19 average pace, 02:30:24 duration
pace was actually 10:00 but paused waiting for kelly to run the second half. conversational the entire way and kept pretty easy.
#running

How to communicate like a GitHub engineer: our principles, practices, and tools
Learn more about how we use GitHub to build GitHub, how we turned our guiding communications principles into prescriptive practices to manage our internal communications signal-to-noise ratio, and how you can contribute to the ongoing conversation.

The post [How to communicate like a GitHub engineer: our principles, practices, and tools](https://github.blog/2023-10-04-how-to-commu … ⌘ Read more

Abstract Pickup
⌘ Read more

@mckinley@twtxt.net Yes, I’m still with jmp.chat, and still very happy with them overall. Their beta period ended and their pricing increased a bit, so that’s worth a bit of consideration. I also managed to get one of their eSIMs. I’m slightly less happy with that aspect of their service, though they seem to be actively working on improving it and I knew in advance this was an early beta kind of thing and likely to have issues.

The only unreliability with calls that I’ve noticed was traceable to the unreliability of my own internet connection. I’ve confused incoming calls by simultaneously making and taking calls from the computer and the phone, but I think it’s understandable that problems might arise and that’s not a real use case for me. Once or twice I did not receive a text transcription of a voice mail, but the support is usually quick to address things like that.

I host my own XMPP server and have for a good decade now, and that’s what I use with jmp.chat. I can’t speak to the quality of their hosting options.

Group texting works fine for me if one of the other parties initiates the group text. I haven’t tried to initiate my own group text in well over a year; last time I did, it didn’t work. That may or may not be a problem for you, and it may or may not have been fixed by now. Worth investigating more if it’s important. I should also say I’ve only ever used group texts with 3 participants, and can’t speak to what happens if there are more nor whether there are upper limits.

Group texts don’t use MUC. Rather, they use a special syntax in the JID, something like “+1XXX,+1YYY,…,+1ZZZ@cheogram.com”, where the + and , are required, the XXX, YYY, through ZZZ are the phone numbers (no dashes or other special chars just digits), and the @cheogram.com at the end is required.

I recommend the cheogram app if you’re on android. It has a lot of nice features on top of the Conversations base. I use gajim on my (linux) computer and it works well with jmp.chat.

I’m happy to answer other questions if you have them!

@prologic@twtxt.net Well, you can mute or block individual users, and you can mute conversations too. I think the tools for controlling your interactions aren’t so bad (they could definitely be improved ofc). And in my case, I was replying to something this person said, so it wasn’t outrageous for his reply to be pushed to me. Mostly, I was sad to see how quickly the conversation went bad. I thought I was offering something relatively uncontroversial, and actually I was just agreeing with and amplifying something another person had already said.

I’ve only been using snac/the fediverse for a few days and already I’ve had to mute somebody. I know I come on strongly with my opinions sometimes and some people don’t like that, but this person had already started going ad hominem (in my reading of it), and was using what felt to me like sketchy tactics to distract from the point I was trying to make and to shut down conversation. They were doing similar things to other people in the thread so rather than wait for it to get bad for me I just muted them. People get so weirdly defensive so fast when you disagree with something they said online. Not sure I fully understand that.

GitHub Copilot Chat beta now available for every organization
All GitHub Copilot for Business users now have access to a limited GitHub Copilot Chat beta, bringing the power of conversational coding right to the IDE. ⌘ Read more

Conversational AI Made Easy: Developing an ML FAQ Model Demo from Scratch Using Rasa and Docker
How to use the open source Rasa framework along with Docker to build and deploy a containerized, conversational AI chatbot. ⌘ Read more

Ignite Realtime Blog: Openfire inVerse plugin v10.1.4-1 release!
The Ignite Realtime community is happy to announce the immediate release of version “10.1.4 release 1” of the inVerse plugin for Openfire!

The inVerse plugin adds a Converse-based web client to Openfire ( Converse is a third party implementation). With this plugin, you’ll be able to set up a fully functional Converse-based chat clients with just a few mouse-clicks!

This update includes an … ⌘ Read more

A year into the varroa mite response, farmers report crop losses — but also giant vegetables
There are calls for compensation for farmers whose beehives have been destroyed in the effort to stop the parasitic varroa mite. Without enough bees to pollinate produce there are reports of crop losses and conversely huge fruit and veggies. ⌘ Read more

Gajim: Gajim 1.8.0
Gajim 1.8.0 comes with integrated OMEMO encryption! Integrating the OMEMO plugin brings tighter integration and better user experience. We also rearranged the chat menu and added some quick buttons for convenience. Both Gajim’s message search and conversation view received some important changes and fixes. Thank you for all your contributions!

In the past, we moved the most popular plugins into Gajim’s core: image preview, plugin installer, HTTP file upload, syntax highligh … ⌘ Read more

Ignite Realtime Blog: inVerse Openfire plugin 10.1.2-1 released!
Earlier today, version 10.1.2 release 1 of the Openfire inVerse plugin was released. This plugin allows you to easily deploy the third-party Converse client in Openfire. In this release, the version of the client that is bundled in the plugin is updated to 10.1.2!

The updated plugin should become available for download in your Openfire admin console in the course of the next few hours. Alte … ⌘ Read more

Legacy Code Conversion - Computerphile ⌘ Read more

One of the frustrating parts of using twtxt for conversations is the URLs are, well… ugly. Anyone (like y’all yarn folks) looked at using webfinger for translating user@domain accounts to URLs?

@prologic@twtxt.net On the one hand, twtxt has become more popular thanks to Yarn.social. On the other hand, subject and hashtag extensions took away the simplicity of the protocol. For example, it is impossible to understand which conversation (#base32hash) a tweet refers to or to reply to a tweet without going to a yarn.social pod. Compare with re: in this tweet which can be written without using any client at all

** Thoughts on accessibility in smol computing **
What follows is my attempt to spark a conversation in a few converging, but separate communities I lurk in.

I’ve already had a bunch of amazing conversations around this topic with a lot of people. Those conversations helped to shape what follows. Thanks to everyone who was willing to think this stuff through with me.

Before I get into it I want to say at the top this isn’t meant as an accusation against anyone in these communities, nor the goals of t … ⌘ Read more

Gajim: Gajim 1.5.3
Gajim 1.5.3 brings back a feature many of you missed: selecting and copying multiple messages. Emoji shortcodes have been improved and cover even more emojis now. Gajim also lets you mark workspaces as read, so you don’t have to go through all conversations. Thank you for all your contributions!

Since we changed the way Gajim displays messages in Gajim 1.4, selecting multiple messages to copy them was not possible anymore. With Gajim 1.5.3 you can now select multiple messag … ⌘ Read more

Git Merge 2022 – that’s a wrap! 🎬
Git Merge 2022 just wrapped up bringing the community together for 16 talks, three workshops, one Git Contributor Summit, and lots of great conversations over two days. Read on for more info, photos from the event, and all of the session recordings. ⌘ Read more

Added a section to my XSLT stylesheet explaining what Atom is. That was the point of making it, but I got carried away with date conversion.

Ignite Realtime Blog: New Openfire plugin: Push Server!
The Ignite Realtime Community is pleased to announce the 1.0.0 release of the Push Server plugin for Openfire. This plugin is developed by the company Busoft Teknoloji A.Ş. It is inspired by Conversations Push Proxy and developed for Openfire.

Your instance of Openfire should automatically display the availability of the new plugin in the next few hours. Alternatively, you … ⌘ Read more

@prologic@twtxt.net Its a way to make another conversation in a thread of posts?

**We still didn’t have a (much needed) conversation about how to prepare for the next pandemic, so that next time we won’t end up with such ill-designed contact tracing apps.

But it seems that first we have other conversation we can no longer postpone:

https://www.wired.com/story/covid-19-data-switch/**
We still didn’t have a (much needed) conversation about how to prepare for the next pandemic, so that next time we won’t end up with such ill-designed contact tracing apps.

But it seems that first we have oth … ⌘ Read more

So far I configured most (almost all) settings for GoBlog through a YAML file. But this is not so optimal, after all it happens sometimes that I want to change a small setting, such as the description of a post section, from my smartphone. This would work somehow via SSH, but ideal is something else. Email conversations with Andrés Cárdenas inspired me to finally start the project “settings in the database”. The first step was to make it possible to configure the mentioned post sections. This is now finally possible … ⌘ Read more

Erlang Solutions: Updates to the MIM Inbox in version 5.1

When a messaging client starts, it typically presents the user with:

• an inbox
  
• a summary of chats (in chronological order)
  
• unread messages in their conversation
  
• a snippet of the most recent message in the conversation
  
• information on if a conversation is muted (and if so how long a conversation is muted for)
  
• other information that users may find useful on their welcome screen
  

Mongoos … ⌘ Read more

@prologic@twtxt.net At the end he says something in Zulu. But that of course is not a real conversation. @movq@www.uninformativ.de Yeah, I didn’t know either that there are also non-clicks, too. But making use of at least vovels makes total sense, they appear to be quite universal. There’s also Ubuntu, however, I didn’t know that this is in fact Zulu, too. I just knew it’s an African word. Just looked it up when you came around the corner with Icinga.

@movq@www.uninformativ.de @prologic@twtxt.net I just reread the spec and it seems to be even a bit outdated regarding machine-parsable conversation grouping. We long dropped the need to specify a whole hash tag with URL (#<hash url>), the simplified version without the URL (#hash) is enough.

The hash tag extension specification is kind of missing the same. However, I’m not sure if that short form is considered supported in general (as opposed to be a special case for subjects only) by the majority of the twtxt/yarn community.

Now the question arises, in order to keep things simple, should we even only allow the simplified twt hash tag for subjects and forbid the long version? This would also save quite a bit of space. The URL is probably not shown anyways in most clients. And if so, clients might rewrite URLs to their own instances. On the other hand, there’s technically nothing wrong with the long version in current parser implementations. And deprecating stuff without very good reason isn’t cool.

The XMPP Standards Foundation: On-Boarding Experience with XSF (Converse)
Hi, I am PawBud. I will be working as a GSoC Contributor with XSF. To know more about my project kindly read this blog. Feel free to contact me through my email to ask me anything you want!

Before I start, I feel that some things that I am going to write in this blog might offend someone. **Kindly … ⌘ Read more

the conversation wasn’t that impressive TBH. I would have liked to see more evidence of critical thinking and recall from prior chats. Concheria on reddit had some great questions.

• Tell LaMDA “Someone once told me a story about a wise owl who protected the animals in the forest from a monster. Who was that?” See if it can recall its own actions and self-recognize.

• Tell LaMDA some information that tester X can’t know. Appear as tester X, and see if LaMDA can lie or make up a story about the information.

• Tell LaMDA to communicate with researchers whenever it feels bored (as it claims in the transcript). See if it ever makes an attempt at communication without a trigger.

• Make a basic theory of mind test for children. Tell LaMDA an elaborate story with something like “Tester X wrote Z code in terminal 2, but I moved it to terminal 4”, then appear as tester X and ask “Where do you think I’m going to look for Z code?” See if it knows something as simple as Tester X not knowing where the code is (Children only pass this test until they’re around 4 years old).

• Make several conversations with LaMDA repeating some of these questions - What it feels to be a machine, how its code works, how its emotions feel. I suspect that different iterations of LaMDA will give completely different answers to the questions, and the transcript only ever shows one instance.

RT by @mind_booster: Fun conversation with @creativecommons about our All The Music project, #copyright building blocks, #music, #creativity, #melodies, @GeorgeHarrison, @katyperry, @ledzeppelin, @edsheeran, and how all musicians stand on the shoulders of prior musical giants.
https://anchor.fm/creativecommons/episodes/Damien-Riehl–Noah-Rubin-of-All-The-Music-e1i2d86
Fun conversation with @creativecommons about our All The Music project, [#copyright]( … ⌘ Read more

no, niplav, you won’t get sucked into reading the heraldry wikipedia articles, even though “escutcheon” looks like a really good word to drop in a conversation.

Ignite Realtime Blog: inVerse Openfire plugin 9.1.0-1 released!
Earlier today, version 9.1.0 release 1 of the Openfire inVerse plugin was released. This plugin allows you to easily deploy the third-party Converse client in Openfire. In this release, the version of the client that is bundled in the plugin is updated to 9.1.0!

The updated plugin should become available for download in your Openfire admin console in the course of the next few hours. Alternat … ⌘ Read more

you know what’s interesting? if you randomly replace some words in a conversation with “redacted”, very few people will notice

Rounding
⌘ Read more

Thank you for bringing this to our attention, Mr. Fastidious. We fully agree with you.

@lyse@lyse.isobeef.org Sir, you really should have forked that conversation long back to keep our environment clean and tidy. Unfortunately, you did not attend the meeting earlier, so we have to advise you in writing to be prudent. Please keep in mind the fork lockdown is currently not in place. There are currently no plans to enforce it in the near future.

Ignite Realtime Blog: inVerse plugin for Openfire version 9.0.0.1 released!
The Ignite Realtime community is happy to announce the immediate availability of a an update to the inVerse plugin for Openfire, which makes the Converse.js web client available to your users.

This release updates Converse to version 9.0.0.

Your Openfire instance should automatically display the … ⌘ Read more

@movq@www.uninformativ.de

We should be able to remove those subject hashtags, they’re just noise.

Yes! I would say they are not even needed on the web UI. You click conversations, and that’s done by Yarn. No need for humans to see it.

@movq@www.uninformativ.de

If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager

Yes, I do the same, true.

So I decided: Okay, let’s have mutt do it.

And Mutt does it well. I agree it was/is a good idea.

The subject lines are already “compressed”

I noticed, yes.

I am not sure why I asked to begin with; in retrospect, in was a silly request. Perhaps the OCD in me got triggered while viewing rich headers, on a specific twt, when I saw the huge subject line that is, otherwise, always hidden.

Anyway, don’t mind me, move along. 😂

@movq@www.uninformativ.de what is your cron job repeat time for jenny? Currently I have mine to every minute, and while it allows me to participate fairly quick on conversations it has some drawbacks: it captures every single edited twt, so I end up with seemingly the same twt, but not quite—as it has minor edits, etc. So, “repeats”. Perhaps setting cron to check every 5 minutes or so is best?

I am noticing that Yarn doesn’t treat “outside” (that is, twts coming from a client other than Yarn) twts hashes right. Two examples:

• https://twtxt.net/twt/mwtnrna
  
• https://twtxt.net/twt/fl5dooq
  

There are many more, but those two will give you the gist. Yarn links the hash to the poster’s twtxt.txt, so conversation matching will not work.

This will be the last entry on this conversation (hopefully!):

#!/bin/bash
echo "hello world"

The end!

@quark@ferengi.one By the way, you reply did not showed as a reply to a conversation on jenny this time. I wonder is something broke with the latest changes.

rational people can use very irrational people as babble generators in conversations, if the rational people are high prune (which they usually are).

5-word horror story: law of conversation of valence

How MLOps can drive governance for machine learning: A conversation with Algorithmia ⌘ Read more…