phone

    • chevron_right

      Profanity: Profanity and OpenPGP for XMPP (OX)

      Profanity • news.movim.eu / PlanetJabber • 24 March, 2022 • 2 minutes

    We have been to implement OX in profanity. OX is XEP-0374: OpenPGP for XMPP Instant Messaging whichmay replace XEP-0027: Current Jabber OpenPGP Usage .

    It is part of Profanity since version 0.10 but got some fixes since then.

    Feel free to try and test the implementation. Let us know, if you have someissues and support the development via testing and reporting bugs.

    How does it works? There are some parts which will be done directly withGnuPG. You will see those gpg commands which needs to be executed in theshell. The commands within profanity are the /ox commands.

    Generate OpenPGP key materials

    The first step is to create a OpenPGP key pair. The key pair generationwill be done with the gpg command of GnuPG.

    gpg --quick-generate-key xmpp:alice@domain.tld future-default default 3y

    This command will generated a OpenPGP key with a UID xmpp:alice@domain.tld . The option future-default has been used togenerate a ed25519/cv25519 key. The expiration date will be in threeyears. Replace the Jabber ID with your JID and do not forget the URI xmpp: prefix.

    pub   ed25519 2021-09-21 [SC] [verfällt: 2024-09-20]      583BAE703A801095B6B71A56BD801174B1A0B84Auid                      xmpp:alice@domain.tldsub   cv25519 2021-09-21 [E]

    Export your public key

    You need to export your public key to share this public key with yourbuddy. Use the command below to export public key:

    gpg --export \  --export-options export-minimal \  --export-filter 'keep-uid=uid =~ xmpp:alice@domain.tld' \  --export-filter 'drop-subkey=usage =~ a' \  583BAE703A801095B6B71A56BD801174B1A0B84A \  > /tmp/pep-key.gpg

    The key will be exported to /tmp/pep-key.gpg . You may check the key withthe command below:

    gpg --show-key --with-sig-list /tmp/pep-key.gpg

    Keep in mind: Public keys may have some information (signatures, name,e-mail address). Be careful which data will be exported. The export-options and export-filter option of GnuPG will help you tofilter the data.

    Publish your key

    You can use profanity to publish your exported key into your account (PEP).The /ox announce command will publish your key.

    /ox announce /tmp/pep-key.gpgAnnonuce OpenPGP Key for OX /tmp/pep-key.gpg ... 

    The command will create two PEP node records to store the key.

    Discover keys

    The /ox discover command will be used to discover keys.

    /ox discover buddy@domain.tldDiscovering Public Key for buddy@domain.tld 1234567890ABCDEF1234567890ABCDEF12345678

    To request and import a key, you can use the /ox request command.

    /ox request buddy@domain.tld 1234567890ABCDEF1234567890ABCDEF12345678Requesting Public Key 1234567890ABCDEF1234567890ABCDEF12345678 for buddy@domain.tldPublic Key imported 

    The key will be imported into your gnupg keyring.

    Sign the imported key

    The key can been shown via gpg gpg -k xmpp:buddy@domain.tld .Make sure the key is the key of your buddy and sign the key with your key.

    gpg --ask-cert-level --default-key 583BAE703A801095B6B71A56BD801174B1A0B84A --sign-key 1234567890ABCDEF1234567890ABCDEF12345678

    The command /ox contacts will show the keys with XMPP-UID.The command /ox keys will show all known OpenPGP keys.

    Use OX

    Within a chat window you can start OX via /ox start and stop it via /ox end .

    Messages will be send signed and encrypted.

    • chevron_right

      Ignite Realtime Blog: GoJara plugin for Openfire version 2.2.3 release

      guus • news.movim.eu / PlanetJabber • 24 March, 2022

    The Ignite Realtime community is happy to announce the immediate availability of a maintenance release of the GoJara plugin for Openfire. GoJara provides an implementation of XEP-0321 “Remote Roster Management” and helps out with monitoring Spectrum 2 .

    Your Openfire instance should automatically display the availability of the update. Alternatively, you can download the new release of the plugin at the GoJara plugin’s archive page . If you’ve got feedback or ideas about this plugin, come and join the conversation on Discourse !

    For other release announcements and news follow us on Twitter

    1 post - 1 participant

    Read full topic

    • chevron_right

      Gajim: Development News March 2022

      Gajim • news.movim.eu / PlanetJabber • 24 March, 2022 • 1 minute

    March brings a new issue reporting system and many performance improvements for both Gajim and python-nbxmpp. Gajim’s OMEMO plugin comes with some improvements as well. Last but not least, there has been a security issue in python-nbxmpp, which has been fixed in version 2.0.6.

    Changes in Gajim

    As some of you might know, Gajim is being developed using Python. Exceptions and tracebacks are Python’s way of communicating errors to developers. In the past, you would see an error window popping up, which presents some details. Clicking ‘Report Issue’ (step 1) would lead to our development platform , where you would have to login (step 2), and then post the issue including some of your feedback (step 3). This is not a simple process, and it certainly holds users back from reporting issues.

    In order to simplify reporting issues, we implemented error reporting via Sentry . Sentry is an optional library, which enables users to send error reports directly to our development platform, without requiring them to login (only a single step needed). Of course you still get to decide if you want to send a report or not. There is no automatic reporting. If the Sentry library is not installed on your system, Gajim’s error reporting will fall back to the previous behaviour. We hope this lowers the hurdle for users to report issues, leading to a better overview of what needs fixing the most.

    What else happened:

    • Search performance has been improved significantly
    • Menu handling has been refactored
    • Create Group Chat window has been simplified
    • Chat history export has been improved
    • Start Chat display performance has been improved
    • Privacy settings are now applied without requiring a restart
    • Text selection and copying has been improved
    • Fixed global proxy setting
    • Fixed status icon for some desktop environments
    • Improved resilience against cache database corruption

    Plugin updates

    Gajim’s OMEMO plugin received an update which raises the allowed amount of unacknowledged messages until a key becomes invalid. This should help with clients being left out of an encrypted chat after idling for some time.

    Changes in python-nbxmpp

    python-nbxmpp 2.0.5 and 2.0.6 have been released, fixing a security issue in resolving websocket URIs. Furthermore, there have been performance improvements for processing network data, which should make Gajim more responsible during heavy load.

    As always, feel free to join gajim@conference.gajim.org to discuss with us.

    Gajim

    • wifi_tethering open_in_new

      This post is public

      gajim.org /post/2022-03-24-development-news-march/

    • chevron_right

      Erlang Solutions: 5 Key Tech Priorities for Fintech Leaders in 2022

      Michael Jaiyeola • news.movim.eu / PlanetJabber • 22 March, 2022 • 4 minutes

    Issues caused by sub-optimal tech choices are commonplace in the industry, leading to companies failing under unexpected stress or being unable to adapt in time when their business requirements change.

    While no two projects are the same, we’ve observed some common themes for using scalable futureproof technologies to build diverse fintech systems. Taking advantage of these learnings sets financial service providers up to have reliable, secure, futureproof systems, providing a solid foundation for long term success.

    We explore this and more further in our new white paper ‘Fintech Trends for 2022’ that you can download here .

    1. Leaders need a greater overall understanding of emerging technology

    We don’t mean getting as granular as in knowing how to code, but you do need a sufficient amount of knowledge to engage with your tech colleagues productively. With the pace of change accelerating, more is being asked of tech teams beyond just keeping the lights on, and this demands investment from business leaders into learning where the opportunities for innovation exist.

    For those in doubt, being at the forefront of innovative technologies has shown to be incredibly important to the success of the tech giants disrupting financial services in the Chinese market. Machine learning (ML) and artificial intelligence (AI), for instance, can help firms to better mitigate risk, combat fraud, personalise customer experiences and, crucially, analyse massive blocks of data to make truly informed decisions.

    While other developments such as blockchain and digital currencies are still nascent, they do make up a large part of what some are calling web3 — or the next chapter in the internet economy — which is set to be far more decentralised in nature. We recently co-organised a panel debate as part of Fintech Week London on blockchain’s potential in financial services, which gave plenty of food for thought on where things are heading.

    2. Software engineering should be at the core of business strategy

    Business and IT borders are blurring — business is the technology, and technology is the business. Software engineering is key to creating value and the best performing traditional banks now focus more of their tech spend on growth and innovation rather than on maintenance.

    With a centuries-old monopoly over the financial industry now eroded for incumbents, similar to what happened in telecoms, significant disruption is being driven by technological advances. Although it is difficult to predict the future models of finance, they are sure to be created by the world’s brightest software engineers.

    3. Customer-centricity is the driving force of change in the industry

    The rapid digitisation of the last two years was ultimately in response to changes in customer behaviour during the pandemic. Customer-centricity has been a winning strategy for fintech

    firms for some time, and any traditional firms who were not yet on board have now joined the party, even if a little late.

    Bill Gates said in 1994, “banking is necessary, banks are not,” and the rise of embedded finance (such as buy-now-pay-later), which is all about providing a better customer experience, is evidence of this being true to at least some extent. Whether it is AI personalisation, blockchain powered digital onboarding or something else not yet imagined, at the end of the day, technology is a means to an end and being customer focused is the theme that underpins everything that has longevity. The goal is to deliver value to customers, and the tech used to do it is secondary.

    4. A clear strategy for modernisation of legacy infrastructure is essential

    Financial services incumbents have multiple core legacy systems written in different programming languages which are complex, fragmented and pre-date the digital era. Years of integrating new services, mergers and acquisitions have led to IT architecture that is expensive to run and maintain, but also tricky to change.

    The stress placed on systems caused by spikes in online commerce since the pandemic has shown that the short-term superficial additions and fixes made were in many cases not implemented with long-term resilience and scalability in mind. While banks experiencing IT system failure is a regular occurrence, the potential damage from a reputational and trust perspective is now more severe than ever.

    5. System security, fault tolerance and resilience are more important than ever

    Trust in financial services institutions are extremely important to society as a whole, especially in the wake of the 2008 financial crisis. When banking and fintech systems are suboptimal from a security and operational resilience perspective, the risks to customer trust are substantial and potentially fatal if things go wrong. Top of what keeps CIOs and CTOs awake at night is the threat of potential cyber attacks.

    In modern financial services, fast delivery of new digital products and services must be balanced against the security and reliability of the system. If you have designed your system with resiliency in mind, you can avoid any trade-off. Software with built-in resilience can give you the foundation to be agile and nimble while simultaneously maintaining system security.

    And don’t forget the human bit

    Fintech firms and incumbents use technologies like cloud, blockchain, AI and ML, but there is often a lack of skilled employees that truly understand how to leverage them effectively. According to the World Economic Forum, more than half (54%) of all employees will require significant reskilling in 2022. Cultivating a technology literate workforce with an engineering mindset has never been of such value in organisations as it is today, but the reality is finding and onboarding experienced fintech software developers can be extraordinarily difficult for CTOs. This is where partnering with an extended team to work on your architecture and backend services while your in-house team does the frontend and UI/UX can help you develop and launch products quicker than the competition.

    For a deeper dive into these fintech themes and how they should inform your tech strategy and decision making, download our free whitepaper “Fintech Trends for 2022” here.

    The post 5 Key Tech Priorities for Fintech Leaders in 2022 appeared first on Erlang Solutions .

    • wifi_tethering open_in_new

      This post is public

      www.erlang-solutions.com /blog/5-key-tech-priorities-for-fintech-leaders-in-2022/

    • chevron_right

      Maxime Buquet: Am I allowed to say no?

      pep. (blog@bouah.net) • news.movim.eu / PlanetJabber • 21 March, 2022 • 1 minute

    People often take photographs for granted. It does seem obvious in our societythat people like to appear with their friend on Facebook, TikTok, and what haveyou.

    Early on I started telling people I didn’t want to have my picture taken. Ithas never really been clear why, not even to myself to be honest. It might havebeen out of shyness – a trait that is still ever so present – or because Ididn’t like the way I look in them, or perhaps some other reason. But I kepttelling them.

    As I grew up I started fiercely advocating for privacy and so this obviouslymade it up the list of reasons. How would I know what people having access tothis picture would do with the information that I was at a specific place at aspecific moment, or what they would do with the image. And I kept tellingpeople not to take pictures of me.

    And despite saying all that, people kept teasing me about it, while some wouldplainly ignore my requests and take pictures anyway.

    When somebody insists or asks why – not that I mind having this discussionwhen they’re not pointing a camera at my face – all I hear is societyreminding me that not wanting to appear on pictures isn’t “normal”.

    I can try to explain and justify this all I want, but the real issue hereisn’t that I am saying no, it’s that nobody listens. What we really should beasking is why am I compelled to justify this behaviour to others in the firstplace, instead of them simply respecting me saying “no”.

    Consent , to name it, is to get a freely given “yes”.

    • wifi_tethering open_in_new

      This post is public

      bouah.net /2022/03/am-i-allowed-to-say-no/

    • chevron_right

      Sam Whited: Joanna

      Sam Whited • news.movim.eu / PlanetJabber • 16 March, 2022

    Sipping my tea, I think back and remember Joanna:Quietness isn't the same for me now.You came to America, wondering what you'd find:Atlanta in a forest of broken dreams,A people in turmoil, and no one seems to know why.Communities falter before they've begun.A lawnmower hums and I wake from my reverie.I'd forgotten, about your America.Driving to the North, far away from the city.You looked for meaning in every farm passing by.I bought you peanuts and gave you a tour of the mountains.We danced in Kirkwood, then took the train going nowhere;Out of the window the car lights flashed by.I said, ``Look at the city", forgetting you couldn't see:Our eyes met, and we knew eachothers minds.Concrete islands separate neighbor from neighbor,You took the bus and left Eastpoint behind.We can't be lovers, you've gone to discover,Your place in this new America.
    • chevron_right

      Erlang Solutions: FinTech Matters newsletter | March 2022

      Michael Jaiyeola • news.movim.eu / PlanetJabber • 14 March, 2022 • 4 minutes

    Subscribe to receive FinTech Matters and other great content, notifications of events and more to your inbox, we will only send you relevant, high-quality content and you can unsubscribe at any time.

    Read on to discover what really matters for tech in financial services right now.

    Despite more important things happening in the world right now, there has still been a lot of news in the financial services industry, we’ll take you through the important stories you may have missed.

    Michael Jaiyeola, Fintech Marketing Lead

    [Subscribe now]

    The Top Stories Right Now

    JPMorgan to spend $12 billion on tech

    This announcement from JPMC signals a significantly larger tech spend will be allocated to keeping pace with fintech challengers and Big Tech – which is quite a humble admission considering that the bank has over 60 million retail customers. [Read the press release]

    This will be an increase from $9.5 billion in 2020 for the leading US bank. As with all financial services incumbents, most of the tech costs will be gobbled up by managing legacy systems and keeping the lights on operationally.

    Beyond that, we do not have much light on where the additional budget will be focused beyond leveraging cloud computing, improving data strategy and investing in a product-led mindset.

    So what exciting innovation might this $12 billion investment in tech spawn? That is very much TBD because in an organisation as large as JPM, trying to mirror the nimbleness and agility of fintech startups is the biggest challenge of all.

    Read the full story

    UK regulators looking into operational resilience of cloud suppliers in banking

    According to an anonymous source speaking to the Financial Times, the Bank of England’s Prudential Regulation Authority is starting to consider cloud providers as “critical third parties that we need more oversight of.” Microsoft, Google and AWS are being looked into to understand the risk/benefit of cloud adoption in financial services and especially what disaster recovery is in place.

    The concerns about the consequences of a major cyberattack that would affect UK banks and an ever-growing number of British consumers whose banks are increasingly using cloud-based technologies.

    The PRA is set to publish a joint discussion paper with the Bank of England and the Financial Conduct Authority in 2022 to look into the issue.

    Read the full story

    Denmarks’ clearing house to adopt the P27 cross-border payments platform

    The platform developed by Danske Bank, Handelsbanken, Nordea, OP Financial Group, SEB and Swedbank will now also become the national clearing house for Denmark, replacing the current infrastructure. This is quite a big step forward and a great example of how cutting edge fintech can start to change underlying financial infrastructure

    Along with P27, Vocalink (part of Mastercard) has won several big contracts around the world, including with Singapore, Thailand and the US bank-backed ACH The Clearing House.

    The consortium of Nordic banks’ lofty ambition for P27 is to create one common state of the art payment platform in the Nordic countries. The platform includes Vocalink’s innovative Immediate Payment System (IPS) which uses Erlang based technologies to achieve massive scale at the centre of the global payments infrastructure.

    R ead the full story

    More content from us

    We’re looking forward to taking part in Fintech Week London again. Last year we were able to organise a star-studded in-person panel to discuss the non-crypto uses of blockchain in banking and financial services.

    With distributed ledger technology experiencing an uptick in attention of late, now might be a good time to review some of the expert thoughts and insights from our panel from last summer.

    Watch the video

    We have just published our “Fintech Trends for 2022” white paper.

    👉 Discover 5 key tech trends shaping modern financial services and learn how to bridge the gap between business and tech functions.

    It is produced in collaboration with our global fintech clients, internal engineering and project management team and some of the most influential subject matter experts in the industry.

    Download it no w

    “System disruption”, “significant technical issues” – another IT issue grounds British Airways flights

    With a cyberattack being ruled out as a cause the finger points again to ailing BA legacy tech. This is the latest in costly recurrences of tech mishaps for the once-great British travel institution. Since 2018 there have been major leaks of credit card data and system outages hitting the bottom line and BA’s reputation.

    Read the full story

    UK fintech – could do better?

    A year on from the Ron Kalifa report for the UK government to roadmap the future of British based fintech, Innovative Finance (the non-profit industry body) has written to outline areas of improvement with the signatures of leaders at 70 of the biggest fintech firms.

    Read the full story

    Erlang Solutions bitesize

    Code reviews and healthchecks – our team has a wealth of experience delivering secure, compliant solutions to heavily regulated industries such as healthtech and financial services. We are able to help you design your system for resilience and security and spot potential issues and vulnerabilities in existing architecture.

    We’ll provide you with a comprehensive analysis of your system, as well as an actionable set of steps to improve performance, reduce bottlenecks and, most importantly, reduce security vulnerabilities.

    Speak to our experts

    To make sure you don’t miss out on any of our leading FinTech content, events and news, do subscribe for regular updates. We will only send you relevant high-quality content and you can unsubscribe at any time.

    Connect with me on LinkedIn

    Email: michael.jaiyeola@erlang-solutions.com

    The post FinTech Matters newsletter | March 2022 appeared first on Erlang Solutions .

    • chevron_right

      Prosodical Thoughts: Prosody 0.12.0 released

      The Prosody Team • news.movim.eu / PlanetJabber • 14 March, 2022 • 12 minutes

    ÄNTLIGEN! It’s finally here! After 3 years of development and through some chaotic times, Prosody 0.12.0 is released!

    What’s the significance of this release? Like many software projects, Prosody follows a “branch” development/release model. We frequently make minor releases with bug fixes and improvements from our stable branch, while we implement more adventurous changes in our development branch, ready for the next major release.

    Well, this is one of those adventurous major releases! Specifically, the first release in the 0.12 series, which will now be our new stable branch.

    We can’t wait to share the many exciting features and changes with everyone. With over 2400 commits, this release couldn’t have been achieved without all the help from our many contributors, testers and other community members - you know who you are!


    Before continuing with the release announcement, we want to acknowledgethat some people are facing bigger problems right now. We deeply believe thatcommunication is a superior path to resolving disputes than armed conflict,we are saddened by recent developments in Europe and unreservedly condemn such violence.

    We hope that, by building decentralized open communication tools withoutbarriers, we can use our particular skills to contribute positive change in theworld in what way we best can. We encourage all our community, includingyou, to reflect on what you can do, or keep doing, to contribute positivechange - no matter how small it seems.


    XMPP Compliance

    It makes sense to start off by looking at how the new release progresses Prosody with regards to compliance and interoperability.

    Every year, the XMPP Standards Foundation publishes updated Compliance Suites , which provide the evolving guidance about what features and XEPs modern XMPP software should be implementing.

    We’re glad to report that Prosody 0.12 meets the criteria for “Advanced Server”, “Advanced IM”, “Advanced Web”, “Core Mobile” and”Advanced A/V” according to the latest (2022) XMPP Compliance Suites ( XEP-0459 ).

    What does this mean for you? It means that when you install Prosody, you can be sure of the latest XMPP features and great compatibility with the latest XMPP software.

    If you are upgrading from a previous release, do see the release notes which contain some advice about ensuring your server and configuration is up-to-date with all the new changes.

    Mobile and connectivity optimizations

    In 0.11 we introduced support for mobile connection optimizations that help preserve bandwidth and battery power of mobile devices, using the CSI protocol framework.

    In this new release, we are finally adding official support for another piece of this puzzle - fast reconnects using XEP-0198. This functionality has long been available in the community modules repository, in mod_smacks. Originally written by Matthew Wild, with substantial improvements in recent years from Kim Alvefur and, more recently, Thilo Molitor , the module has a long history.

    With the module finally transitioning into Prosody, we have streamlined the module’s code (as we no longer need compatibility with multiple Prosody versions) and improved efficiency - especially regarding memory usage.

    HTTP file sharing

    If you remember a time on XMPP before the HTTP upload file transfer method came along - you know what an improvement it has been. The first file transfer methods in XMPP (and indeed most other IM protocols at the time) would always attempt to stream the file directly from sender to their contact. As well as being extremely prone to failure due to NATs/firewalls and other network issues, it also made it impossible to send files to people who were offline, or to groups.

    A new mechanism was standardized in XEP-0363 that solves all these issues by building upon an existing standard protocol that is already great at transferring files - HTTP! With this new method, the sender uploads the file to a server, and simply sends the URL to their contact(s).

    To allow easy deployment, Prosody now includes mod_http_file_share . It allows authenticated users to upload files to the server, so they can share them with their contacts.

    This new module is quite comprehensive. Some features include:

    • Configurable file size limit
    • Optional per-user daily upload quota, to ensure fair use of resources
    • Global quota, to prevent excessive disk space consumption on the server by uploaded files.
    • Support for an external upload server
    • Configurable expiry to clean up old uploads
    • Monitoring of disk usage

    As well as the features listed above, mod_http_file_share also takes advantage of internal HTTP server improvements in Prosody 0.12 that allow it to efficiently handle large files. Say goodbye to that 10 MB limit!

    Upgrading from other HTTP upload modules

    Many Prosody deployments already support HTTP file transfer using community modules such as mod_http_upload and mod_http_upload_external . These will continue to work but, especially if you are using mod_http_upload, we encourage you to upgrade to enjoy the new improvements.

    To migrate existing files from an existing mod_http_upload setup, check out the handy mod_migrate_http_upload .

    Audio/video calling support

    Audio and video calls on XMPP have really taken off in the past few years! Although we’ve had support for calling in XMPP for a long time, modern clients are building atop the WebRTC stack for more efficient, reliable and secure encrypted calls (contrary to what you may think, WebRTC can be used outside browsers too). A few of the clients supporting these include Conversations , Dino , Movim , Beagle IM and Siskin IM .

    Prosody itself is not especially involved in the actual calls - it mainly relays the call negotiation between the clients, and assists in the discovery of STUN and TURN services that are used to improve call reliability through NATs and firewalls.

    To facilitate this last part, a server operator needs to do two things:

    1. Set up a STUN and TURN server (usually provided by the same software - eturnal and coturn are popular choices)
    2. Configure Prosody to advertise these services to your users’ clients.

    The second step has traditionally been achieved using a community module, mod_turncredentials . From Prosody 0.12 we now bundle a simpler (but just as effective) module, mod_turn_external .

    We have even implemented a simple STUN/TURN client into prosodyctl so it can verify that your setup is working correctly.

    To get started, see our full overview of setting up STUN/TURN with Prosody .

    Monitoring with OpenMetrics/Prometheus

    We’ve supported various options for monitoring Prosody for quite a while in various forms, including internal statistics gathering and output to statsd-compatible collectors and agents.

    Although statsd has served us well, and is still a good choice for certain environments, Prometheus has emerged as a very popular alternative. So much so, Prometheus’s protocol has been reworked as an open standard - OpenMetrics , with ongoing work to publish it as an IETF RFC.

    Starting from Prosody 0.12, anything using our internal metrics API can now be exposed in a Prometheus-compatible OpenMetrics HTTP endpoint.

    To see how, head over to the mod_http_openmetrics documentation .

    Many thanks to Jonas for leading and implementing this feature, and providing this screenshot of it in use at search.jabber.network .

    Grafana dashboard showing graphs of metrics obtained via Prometheus

    Invitations!

    It’s no secret that we’re big fans of invitation-based registration. As explained in our blog post, Great Invitations , we believe it is the safest and most user-friendly way to let people register on your XMPP server.

    This release brings core support for invitations into Prosody.

    Specifically, the following modules are now bundled with Prosody:

    • mod_invites provides core invitation handling, including the ability to create new invitations via prosodyctl
    • mod_invites_register allows people to register on your server by invitation, from XMPP clients that support XEP-0445 (which includes Conversations, yaxim, Siskin and Snikket).
    • mod_invites_adhoc allows admins (and optionally users) to generate invitations from within their XMPP client. With native support in Conversations, yaxim and Snikket, you can also manually use ad-hoc command support in supporting clients such as Gajim.

    For the full experience, consider also setting up the following community modules:

    The best place to get started with invitations is the mod_invites documentation .

    Direct TLS

    Direct TLS ( XEP-0368 ) is now officially supported, along with SNI to allow more than one certificate per port, as well as reloading those certificates without a restart. The legacy_ssl_ports configuration option has thus been renamed to c2s_direct_tls_ports . The prosodyctl check dns command can also help you make sure the corresponding SRV records are set up correctly .

    Server-to-server connections also support Direct TLS, enabled with s2s_direct_tls_ports and is automatically used with remote serversthat have published the corresponding DNS record.

    What are the benefits of direct TLS over the more traditional “STARTTLS” connections?

    • Faster connection time (fewer network round-trips)
    • Compatibility with TLS middleware such as load balancers and proxies
    • Simpler implementation for clients.
    • Improved traversal of restrictive firewalls, e.g. by running XMPP over port 443, the port usually used for HTTPS (typically not blocked).

    If you’re curious how to support XMPP connections over port 443 alongside a web server, check out the XEP-0368 tech page on the XMPP wiki.

    Other new modules

    A number of other new modules have been added in this release that are worth mentioning.

    mod_s2s_bidi

    Enables using a single connection instead of two between servers, reducing resource usage and latency.

    mod_auth_ldap

    Previously a community module, we have imported this into Prosody for out-of-the-box LDAP support. This replaces our Cyrus SASL support, which has been moved into the community modules repository.

    mod_cron

    More and more modules have periodic tasks, e.g. to expire old messages or files, this module aims to coordinate them.

    mod_mimicking

    This module prevents registration of addresses that look very similar to previously registered addresses, e.g. “zash” vs “zаsh” (that’s Cyrillic a, U+0430 ).

    This is useful for public servers, and helps protect against impersonation attempts that utilize Unicode homoglyphs .

    mod_tombstones

    Another recommending module for public servers, this one prevents re-registration of deleted accounts. It ensures that a deleted account cannot be re-registered by someone else in order to gain access to resources the account had access to - e.g. chat rooms where the account is still listed as a member.

    mod_bookmarks

    XMPP has evolved through a few ways to store “bookmarks” (essentially the list of group chats that a user is joined to).

    With clients supporting different mechanisms, and attempting to keep them in sync, this module supports the latest recommendations and provides compatibility layers between three different ways to store group chat bookmarks, ensuring open group chats are always synchronized between users’ devices, whatever client they are using.

    We encourage client developers to upgrade to XEP-0402: PEP Native Bookmarks for the best experience. Eventually the older mechanisms will be retired as they are no longer needed.

    Plugin Installer

    Our extensive range of community modules , ranging from the silly mod_swedishchef to the amazingly powerful mod_firewall , are almost a defining feature of Prosody.

    Thankfully it’s now easier than ever to install community modules thanks to the work of João Duarte, a student who participated in Google Summer of Code and implemented a plugin installer for Prosody. It uses LuaRocks, which needs to be installed on your system.

    For example, maybe you want to add a nice web client to your XMPP server? There’s a module for that. Simply install mod_conversejs by running prosodyctl install mod_conversejs and then enable it!

    More documentation about this new feature can be found in the plugin installer documentation .

    Built-in HTTP server improvements

    As we mentioned earlier, Prosody’s built-in HTTP server can now efficiently handle large uploads - writing files directly to disk instead of consuming more and more memory until completion.

    Other things have also been improved. You should never have to worry about CORS again! CORS is a security feature of the modern web. However, most HTTP services in Prosody already have some sort of authentication and generally don’t benefit from CORS, which mostly just causes problems for people setting up XMPP web clients. From 0.12 they will work by default (via BOSH and/or websockets).

    The built-in HTTP server also has better support for reverse proxies, and will understand it when HTTPS is handled by the proxy.

    Evolving the Prosody admin shell

    Prosody has had The Telnet Console for a long time. This is an incredibly powerful administrative interface. However, it is also far from perfect. One of the biggest issues is the lack of authentication. Although Prosody ensures it is only accessible to localhost by default, that does not make it safe on any system with untrusted users.

    To improve this, the console itself can now be accessed via a UNIX socket, which is secured using file system permissions. This admin socket functionality is internally quite powerful - it’s actually running a pseudo-XMPP stream, over which multiple kinds of data can flow. Expect to see some fun stuff building on top of this in the future!

    Get started with sudo prosodyctl shell !

    Tip: You can also now run simple commands directly from the command-line, useful for scripting. E.g. rather than connecting to run 'module:list() , you can now simply run: prosodyctl shell module list .

    Future support for 0.11

    If you are currently running 0.11.x and not in a hurry to upgrade, you may be wondering what to expect now that 0.12 is here.

    Our traditional policy is to support release branches that are included in Debian, for as long as that version of Debian is supported by Debian’s security team (note: this does not include the extended “Debian LTS” period, which is a sponsored effort by a separate team). We will continue with this policy for 0.12.

    The latest version of Debian, 11 (“bullseye”) , supplies Prosody 0.11. Although the pace of 0.11 releases will undoubtedly slow down now, you can expect us to continue with security and important bug fixes for a couple of years. That should give everyone plenty of time to evaluate 0.12 and plan their upgrade (right?!).

    Next steps

    Hopefully we’ve shown you enough of 0.12 to get you interested! Head to the Prosody downloads page to find out how to get the new release or upgrade an existing installation.

    If you are upgrading an existing installation, you’ll find relevant advice (along with a more complete list of changes in this release) in our release notes as usual.

    Happy chatting!

    • wifi_tethering open_in_new

      This post is public

      blog.prosody.im /prosody-0.12.0-released/

    • chevron_right

      The XMPP Standards Foundation: The XMPP Newsletter February 2022

      The XMPP Standards Foundation • news.movim.eu / PlanetJabber • 5 March, 2022 • 6 minutes

    Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of February 2022.

    Like this newsletter, many projects and their efforts in the XMPP community are a result of people’s voluntary work. If you are happy with the services and software you may be using, especially throughout the current situation, please consider saying thanks or help these projects! Interested in supporting the Newsletter team? Read more at the bottom.

    Newsletter translations

    This is a community effort, and we would like to thank translators for their contributions. Volunteers are welcome! Translations of the XMPP Newsletter will be released here (with some delay):

    XSF Announcements

    XSF and Google Summer of Code 2022

    XSF fiscal hosting projects

    The XSF offers fiscal hosting for XMPP projects. Please apply via Open Collective . For more information, see the announcement blog post . Current projects:

    Events

    Articles

    • JMP.chat describes in their blog why gateways, and especially bidirectional gateways, with XMPP and other protocols, are so useful. Their Newsletter also announces the launch of worldwide calling and completion of their rebrand.

    JMP.chat bidirectional gateways

    Software news

    Clients and applications

    Dino 0.3 has been released : Video calls and conferences - encrypted and peer-to-peer. Dino now supports calls between two or more people!

    Dino calls

    Gajim development news : February brought a unified group chat details window, which offers all the configuration knobs you need. Also this month: less memory leaks and improved OMEMO QR codes.

    Monal had a successful funding campaign for a build server, which will significantly reduce build time. Further insights into Monal development : Monal will drop support for iOS 12 and 13, and for macOS Catalina. Monal’s team is searching for a SwiftUI developer, and they need help with building a new and simplified website.

    Big news from Movim: Movim 0.20 “Skiff” has been released, which features OMEMO support, GUI improvements, and better group chat management.

    Movim GUI update

    Psi+ 1.5.1605 has been released with OMEMO fixes.

    Poezio 0.13.2 has been released , this version only fixes the compatibility with the newly released slixmpp 1.8.0 , but a much more interesting release is to come soon.

    Profanity developers wrote a blog post on how to run their client on Pinephones.

    Tigase released BeagleIM 5.1 and SiskinIM 7.1 featuring improved OMEMO support.

    Servers

    Jackal 0.57.0 , an XMPP server written in Go has been released.

    Openfire announces the release of Openfire 4.7.1 : Notable fixes include security updates to bundled database drivers, logging configuration fixes, and an important fix for users experiencing troubles with users getting booted from group chat rooms. Furthermore, Openfire Pàdé 1.6.1 has been released. REST API Openfire plugin 1.7.1 hase been released, too.

    Snikket published an important update for users of their server software on ARM devices, including Raspberry Pi boards .

    Tigase XMPP Server 8.2.0 has been released.

    Libraries

    Mellium Co-op has released v0.21.0 and v0.21.1 of the melium.im/xmpp library for Go! Highlights for this release include basic support forPubSub and PEP as well as In-Band Bytestreams. More information can be found in the release announcement . Version 0.21.1 fixes a security issue that was discovered in the websocket package and should be preferred when updating. For more information see CVE-2022-24968 .

    Slixmpp 1.8.0 has been released, which adds compatibility with python 3.10, as well as a lot of improvements related to typing and async under the hood.

    Tigase had several releases for their products: Halcyon 0.0.17 , JaXMPP 3.5.0 , Tigase Swift 3.1.0 , and Tigase Swift-OMEMO 2.1.0 .

    Extensions and specifications

    Developers and other standards experts from around the world collaborate on these extensions, developing new specifications for emerging practices, and refining existing ways of doing things. Proposed by anybody, the particularly successful ones end up as Final or Active - depending on their type - while others are carefully archived as Deferred. This life cycle is described in XEP-0001 , which contains the formal and canonical definitions for the types, states, and processes. Read more about the standards process . Communication around Standards and Extensions happens in the Standards Mailing List ( online archive ).

    Proposed

    The XEP development process starts by writing up an idea and submitting it to the XMPP Editor. Within two weeks, the Council decides whether to accept this proposal as an Experimental XEP.

    New

    • No new XEPs this month.

    Deferred

    If an experimental XEP is not updated for more than twelve months, it will be moved off Experimental to Deferred. If there is another update, it will put the XEP back onto Experimental.

    • No XEPs deferred this month.

    Updated

    • Version 2.13.0 of XEP-0004 (Data Forms)

      • Add incomplete submission form handling (melvo)
    • Version 1.24.1 of XEP-0060 (Publish-Subscribe)

      • Add hint for processing incomplete submission forms (melvo)
    • Version 1.24.0 of XEP-0060 (Publish-Subscribe)

      • Advertise support for publishing items
      • Replace ‘allow’ with ‘allows’ (melvo)
    • Version 1.23.0 of XEP-0060 (Publish-Subscribe)

      • Clarify (redefine) pubsub#type field. (edhelas, pep)

    Last Call

    Last calls are issued once everyone seems satisfied with the current XEP status. After the Council decides whether the XEP seems ready, the XMPP Editor issues a Last Call for comments. The feedback gathered during the Last Call help improving the XEP before returning it to the Council for advancement to Stable.

    • No Last Call this month.

    Stable (formerly known as Draft)

    Info: The XSF has decided to rename ‘Draft’ to ‘Stable’. Read more about it here.

    • No XEPs advanced to Stable this month.

    Deprecated

    • No XEP deprecated this month.

    Call for Experience

    A Call For Experience - like a Last Call, is an explicit call for comments, but in this case it’s mostly directed at people who’ve implemented, and ideally deployed, the specification. The Council then votes to move it to Final.

    • No Call for Experience this month.

    Spread the news!

    Please share the news on other networks:

    Subscribe to the XMPP newsletter

    Also check out our RSS Feed !

    Looking for job offers or want to hire a professional consultant for your XMPP project? Visit our XMPP job board .

    Help us to build the newsletter

    This XMPP Newsletter is produced collaboratively by the XMPP community. Therefore, we would like to thank Adrien Bourmault (neox), alkino, anubis, Anoxinon e.V., Benoît Sibaud, cpm, Damian Sartori, emus, Ludovic Bocquet, Licaon_Kter, mathieui, MattJ, nicfab, seveso, Sam Whited, singpolyma, TheCoffeMaker, wurstsalat,xdelatour, Ysabeau for their support and help in creation, review and translation. Many thanks to all contributors and their continuous support!

    Each months’s newsletter issue is drafted in this simple pad . At the end of each month, the pad’s content is merged into the XSF Github repository . We are always happy to welcome contributors. Do not hesitate to join the discussion in our Comm-Team group chat (MUC) and thereby help us sustain this as a community effort. You have a project and want to spread the news? Please consider sharing your news or events here, and promote it to a large audience.

    Tasks we do on a regular basis:

    • gathering news in the XMPP universe
    • short summaries of news and events
    • summary of the monthly communication on extensions (XEPs)
    • review of the newsletter draft
    • preparation of media images
    • translations

    License

    This newsletter is published under CC BY-SA license .

    • wifi_tethering open_in_new

      This post is public

      xmpp.org /2022/03/the-xmpp-newsletter-february-2022/