• chevron_right

      ProcessOne: ejabberd Docs now using MkDocs

      news.movim.eu / PlanetJabber · Yesterday - 17:02 · 1 minute

    The ejabberd Docs website did just get a major rework: new content management system, reorganized navigation, improved markdown, and several improvements!

    Brief documentation timeline

    ejabberd started in November 2002 (see a timeline in the ejabberd turns 20 blog post). And the first documentation was published in January 2003, using LaTeX, see Ejabberd Installation and Operation Guide . That was one single file, hosted in the ejabberd CVS source code repository, and was available as a single HTML file and a PDF.

    As the project grew and got more content, in 2015 the documentation was converted from LaTeX to Markdown , moved from ejabberd repository to a dedicated docs.ejabberd.im git repository, and published using a Go HTTP server in docs.ejabberd.im , see an archived ejabberd Docs site .

    New ejabberd Docs site

    Now the ejabberd documentation has moved to MkDocs+Material, and this brings several changes and improvements:

    Site and Web Server:

    • Replaced Go site with MkDocs
    • Material theme for great features and visual appeal, including light/dark color schemes
    • Still written in Markdown, but now using several MkDocs, Material and Python-Markdown extensions
    • The online site is built by GitHub Actions and hosted in Pages, with smaller
      automatic deployment time
    • Offline reading: the ejabberd Docs site can be downloaded as a PDF or zipped HTML, see the links in home page

    Navigation

    • Major navigation reorganization, keeping URLs intact so old links still work (only Install got some relevant URL changes)
    • Install section is split into several sections: Containers, Binaries, Compile, …
    • Reorganized the Archive section, and now it includes the corresponding Upgrade notes
    • Several markdown files from the ejabberd and docker-ejabberd repositories are now incorporated here

    Content

    • Many markdown visual improvements, specially in code snippets
    • Options and commands that were modified in the last release will show a mark, see for example API Reference
    • Version annotations are shown after the corresponding title, see for example sql_flags
    • Modules can have version annotations, see for example mod_matrix_gw
    • Links to modules, options and API now use the real name with _ character instead of - (compare old #auth-opts with #auth_opts ). The old links are still supported, no broken links.
    • Listen Modules section is now better organized
    • New experimental ejabberd Developer Livebook

    So, please check the revamped ejabberd Docs site, and head to docs.ejabberd.im git repository to report problems and propose improvements.

    The post ejabberd Docs now using MkDocs first appeared on ProcessOne .
    • wifi_tethering open_in_new

      This post is public

      www.process-one.net /blog/ejabberd-docs-now-using-mkdocs/

    • chevron_right

      Erlang Solutions: Blockchain Tech Deep Dive| Meaning of Ownership

      news.movim.eu / PlanetJabber · 7 days ago - 08:59 · 6 minutes

    Welcome to part three of our ‘Making Sense of Blockchain’ blog post series. Here we’ll explore how our attitudes to ownership are changing and how this relates to the value we attach to digital assets in the blockchain space. You can check out ‘Innovating with Erlang and Elixir’ here if you missed part two of the series.

    Digital Assets: Ownership in the era of Blockchain

    While physical goods contain an abstract element: the design, the capacity to model, package and make it appealing to the owners or consumers. Digital assets have a far stronger element of abstraction which defines their value. In contrast, their physical element is often negligible and replaceable (e.g. software can be stored on disk, transferred or printed). These types of assets typically stimulate our intellect and imagination.

    Digital goods have a unique quality in that they can be duplicated effortlessly and inexpensively. They can exist in multiple forms across various platforms, thanks to the simple way we store them using binary code. They can be recreated endlessly from identical copies. This is a feature that dramatically influences how we value digital assets.  Because replicas are so easy to make, their copies or representations don’t hold value, but the original digital creation itself. This principle is a cornerstone of blockchain technology, with its hash lock feature safeguarding the integrity of digital assets.

    If digital items are used correctly, the capacity to clone a digital item can increase confidence that it will exist indefinitely, which keeps its value steady. However, the immutable and perpetual existence of digital goods isn’t guaranteed forever.

    They are dependent on a physical medium (e.g. hard disk storage), that could be potentially altered, degraded or become obsolete over time.

    A blockchain, like the one used in the Bitcoin network, is a way to replicate and reinforce digital information via Distributed Ledger Technology (DLT).

    nE1KVPGM_tt0iUmfPcCrCuKSblhVNCfoQtoLAp_YsCOCi44CbZsZ6rujNiLzuID9w2mQKXvku1OYe-skE7QMpfbHvAEWfhyVTm-eu4LALguQgihuIa4cQ24NUOh7wxYfKskjVviKd9PWKoQix_K-mdg

    An example of the DLT network

    Distributed Ledger Technology lets users record, share, and synchronise data and transactions across a distributed network comprising of many participants.

    It includes mechanisms to repair issues, should data become corrupted due to hard disk failure or a malicious attack.

    However, as genetic evolution suggests, clones with the same characteristics can all die out by the introduction of an actor that makes the environment unfit for survival. So it might be sensible to introduce different types of ledgers to keep data safe on various physical platforms, increasing the likelihood of survival of information.

    The evolution of services and their automation

    Now let’s consider how we have started to attach value to services and how we are becoming increasingly demanding about their performance and quality.

    Services are a type of abstract value often traded on the market. They involve actions defined by contracts that lead to some kind of change. This change can apply to physical goods, digital assets, and other services themselves or people. What we trade is the potential to exercise a transformation, which in some instances might have been applied already. For example, a refined product like oil that has already been changed from its original raw state.

    As transformations become more automated and the human element decreases,  services are gradually taking the shape of automated algorithms, which are yet another form of digital assets. Take smart contracts, for example, a rapid-growth industry projected to grow from USD 1.9 Billion in 2023 to USD 9.2 Billion by 2032, according to Market Research Future .

    DbGr8SJzEtFtVmaUVlEeMufcT5aKjus0G9cFauvpw8X8FahZwMI2Zyd0RWn7VBn1ZiPTe-KzybiZjnD6_REyHypSp4hi21sQ5FQpA6bIwCmc1X_Ib0LMWA1fBTqpbiAX03ib0dft33QNG6vzss8nQOY

    Smart Contracts Market Projection Overview

    But it’s important to state that an algorithm alone isn’t enough to apply digital transformation, we also require an executor, like a physical or virtual machine.

    Sustainability and access to resources

    Stimulation of the intellect and/or imagination isn’t the only motivator that explains the increasing interest in digital goods and ultimately their rising market value. Physical goods are known to be quite expensive to handle. To create, trade, own and preserve them, there is a significant expenditure required for storage, transport, insurance, maintenance, extraction of raw materials etc.

    There’s a competitive and environmental cost involved, making obtaining physical resources inherently difficult to scale and sometimes costly- especially in densely populated urban areas. As a result, people are motivated to possess and exchange digital goods and services.

    The high power consumption required by the Bitcoin network’s method of consensus would potentially negate these environmental benefits. Although power consumption is a concern, it should be remembered that blockchain technology can act as a force for good, being used for environmentally beneficial projects.

    A great example is the work being done by dClimate , a decentralised climate information ecosystem making it easier for businesses to find and utilise essential environmental information that could impact their sector. These important decisions in turn provide information on:

    • Where businesses can build infrastructure
    • Where they can manage water resources
    • How businesses can protect vulnerable communities

    However, some of these activities (such as those requiring non-physical effort, like stock market trading, and legal or accounting services) are best suited for significant cost reduction through algorithmic automation  (assuming that the high carbon footprint required to drive the ‘Proof of Work’ consensus mechanism used in many DLT ecosystems can be avoided).

    Barriers to acceptance of digital assets

    While it is sensible to forecast a significant expansion of the digital assets market in the coming years, it is also true that, at present, there are still many psychological barriers to overcome to get broader traction in the market.

    The main challenge relates to trust. A buyer wants some assurance that traded assets are genuine and that the seller owns them or acts on behalf of the owner. DLT provides a solid way to work out the history of a registered item without, interrogating a centralised trusted entity. Provenance and ownership are inferable and verifiable from several replicated ledgers while block sequences can help ensure there is no double spending or double sale taking place within a certain time frame.

    Another challenge is linked to the meaning of ownership outside of the context of a specific market. Take the closure of Microsoft’s ebook store. Microsoft’s decision to pull out of the ebook market, presumably motivated by a lack of profit, could have an impact on all ebook purchases that were made on that platform. The perception of the customer was obviously that owning an ebook was the same as owning a physical book.

    What Microsoft might have contractually agreed through its End-User License Agreement (EULA), however, is that this is true only within the contextual existence of its platform.

    There is a push, in this sense, towards forms of ownership that can break out from the restrictions of a specific market and be maintained in a broader context. Blockchain’s DLT in conjunction with smart contracts, that exist potentially indefinitely, can be used to serve this purpose allowing people to effectively retain their digital items’ use across multiple applications.

    The transition to these new notions of ownership is particularly demanding when it comes to digital non-fungible assets. Meanwhile, embracing fungible assets, such as cryptocurrency, has been somewhat easier for customers who are already used to relating to financial instruments.

    This is probably because fungible assets serve the unique function of paying for something, while in the case of non-fungible assets, there is a range of functions that define their meaning in the digital or physical space.

    What this will mean for blockchain adopters

    In discussing the major emerging innovation that blockchain technology has influenced dramatically over the last few years, the ownership of digital assets, it is clear that what we are witnessing is a new era that is likely to revolutionise the perception of ownership and reliance on trusted and trustless forms of automation. This is driven by the need to increase interoperability, cost compression, sustainability, performance and customisation. For any business size in any industry, we’re ready to investigate, build and deploy your blockchain-based project on time and to budget. Let us know about your blockchain project here.

    The post Blockchain Tech Deep Dive| Meaning of Ownership appeared first on Erlang Solutions .

    • chevron_right

      Erlang Solutions: Blockchain Tech Deep Dive | Innovating with Erlang and Elixir

      news.movim.eu / PlanetJabber · Thursday, 11 April - 09:10 · 7 minutes

    We’re back with the latest in our Blockchain series, where we explore in-depth In our first post, we explored the Six Key Principles of Blockchain .

    In our latest post, we’re making the case for using Erlang,Elixir and the BEAMVM to power your blockchain project.

    Blockchain and business needs

    Building a robust and scalable blockchain presents many challenges that a research and development team typically needs to address. The often ambitious goals to drive decentralised consensus and governance require unconventional approaches to achieve extra performance and reliability.

    Improved Transactions per Second (TPS) is the most common challenge that blockchain-related use cases expose. TPS as the name suggests, is a metric that indicates how quickly a network can execute transactions per second. It is inherently difficult to produce a distributed peer-to-peer (P2P) network that can register transactions into a single data structure.

    Guaranteeing consensus while delivering high TPS throughput among a vast number of nodes active on the network is even more challenging. Also, the fact that most public blockchains need to operate in a non-trusted mode requires adequate mechanisms for validation, which implies that contextual data needs to be available on demand. A blockchain should also be able to respond to anomalies such as network connectivity loss, node failure and malicious actors.

    All of the above is further complicated by the continuous growth of the blockchain data structure itself, which becomes problematic in terms of storage.

    It is clear that, unless businesses are prepared to invest vast amounts of resources, they would benefit from a high-level language and technology that allows them to quickly prototype and amend their code.

    The ideal technology should also:

    • Offer a strong network and concurrent capabilities
    • Have technology built with distribution in mind
    • Offer a friendly paradigm for asynchronous computation
    • Not collapse under heavy load
    • Deliver when traffic exceeds capacity

    The Erlang Beam VM (available also in the Elixir syntax) undoubtedly scores high on the above list of desirable features.

    Erlang & Elixir’s strengths for blockchain

    Fast development

    The challenge: Blockchain technology is present in extremely competitive markets. According to Grandview Marketing Analysis report, The global blockchain technology market size was valued at USD 17.46 billion in 2023 and is expected to grow at a compound annual growth rate (CAGR) of 87.7% from 2023 to 2030.

    Grandview Marketing Analysis report

    It is critical for organisations operating in them to be able to release new features in time to attract new customers and retain existing ones.

    The answer: Both Erlang and Elixir are functional languages, operating at a very high level of abstraction which is ideal for fast prototyping and development of new ideas. By using these languages on top of the Beam VM, developers dramatically increase the speed to market when compared to other lower-level or object-oriented technologies.

    Solutions developed in Erlang or Elixir also lead to a significantly smaller code base, which is easier to test and adapt to changes of direction. This is helpful when you proceed to fast prototyping new solutions and when you discover that amendments and upgrades are necessary, which is very typical in blockchain R&D activity. Both languages offer support for unit testing in their standard library. This enables developers to adopt Test Driven approaches ensuring the quality is preserved when modules and libraries get refactored. The common test framework also provides support for distributed tests and can be integrated with Continuous Integration frameworks like Jenkins . Both Erlang and Elixir shells let the programmer flesh out ideas fast and access running nodes for inspection.

    Introspection

    The challenge: To keep a competitive advantage in a fast-changing market, it is critical for organisations to promptly identify issues and opportunities by extracting relevant information about their running systems so that actions can be taken to upgrade them where appropriate.

    The answer: Erlang and Elixir allow connection to an already running system and a status check. This is an extremely useful debugging tool, both in the development and production environment. Statuses of processes can be checked, and deadlocks in the live system can be analysed. Some various metrics and tools can show overload, bottlenecks and other key performance indicators. Enhanced introspection tools such as Erlang Solutions’ Wombat OAM are also helping with the identification of scalability issues when you run performance tests.

    _IAdP2lllWF8mFgcErYQW3Q5CkuvmSz6Elbe63LNYa7H5HXtdumpA0iUs55gYIgkiOyB6oe25pNHdQorAkFRQwCWlWXjiJH-CBbqwwHB6kodZJ0tq9IilKYG6okmCERPbCuf6O3QIBYShSJLafrKHUs

    Networking

    The challenge: Delivering a highly scalable and distributed P2P network is critical for blockchain enterprises. It is important to rely on stable battle-proven network libraries as reliable building blocks for exploiting use case-specific innovative approaches.

    The answer: Erlang and Elixir come with strong and easy-to-manage network capabilities. There is a proven record of successful enterprises that rely on the BEAM VM’s networking strengths; including Adroll, WhatsApp, Bleacher Report , Klarna, Bet365 and Ericsson. Most of their use cases have strong analogies with the P2P networking that is required to deliver a distributed blockchain.

    Combined with massive concurrency, the networking makes Erlang and Elixir ideal for server applications and means it can handle many clients. The binary and bitstring syntax makes parsing binary protocols particularly easy.

    Massively concurrent

    The challenge: There is a weakness afflicting Bitcoin and Ethereum where the computation of a block is competitive rather than collaborative. There is the opportunity to drive a collaborative concurrent approach: i.e. via sharding so that each actor can compute a portion of a block.

    The answer: The BEAM VM powering Erlang and Elixir provides lightweight processes for applications. These are lightweight so that hundreds of thousands of them can run simultaneously. These processes do not share memory, communication is done over asynchronous messages (unlike goroutines) so there’s no need to synchronise them. The BEAM VM implementation also makes use of all of the available CPUs and cores. This makes Erlang and Elixir ideal for workloads that involve a huge amount of concurrency and consist of mostly independent workflows. This feature is especially useful in addressing the coordinated distribution of portions of work to compute a Merkle Tree of transactions.

    High availability and resilience

    The challenge: These are the requirements for every type of application and even more so for competitive and highly distributed blockchain networks. The communication and preservation of a state need to be as available as possible to avoid inconsistent states, network forks and disruptions experienced by the users.

    The answer: The fault tolerance properties mentioned in the previous paragraph combined with built-in distribution leads to high availability even in cases of hardware malfunction. Erlang and Elixir have the built-in mnesia database system with the ability to replicate data over a cluster of nodes so if one node goes down, the state of the system is not lost.

    Erlang and Elixir provide the supervisor pattern to handle errors.

    An example of a Supervision Tree , used to build a hierarchical process structure

    Computing is done in multiple processes and if an error occurs and a process crashes, the supervisor is there to handle the situation, restart the computing or take some other measures. This pattern lets the actual code be cleaned as error handling can be implemented elsewhere. As processes are isolated, they do not share memory meaning errors are localised.

    Built-in distribution

    The challenge: This is highly relevant for trusted or hybrid networks where a central network takes authoritative decisions on top of a broader P2P network. Using the “out of the box” Erlang distribution and proven consistency approaches such as RAFT can be a quick win towards a fast prototype of a blockchain solution.

    The answer: Erlang and Elixir provide out-of-the-box tools to run a distributed system. The message-handling functionalities of the system are transparent, so sending a message to a remote process is just as simple as sending it to a local process. There’s no need for convoluted IDLs, naming services or brokers.

    Safety and Security

    The challenge: Among the security features that both trusted and untrusted blockchain solutions strongly require, is the critical protection of access to the state memory, therefore reducing the exposure to a range of vulnerabilities.

    The answer: Erlang and Elixir, just like many high-level languages, do not manipulate memory directly so applications written in Erlang and Elixir are effectively immune to many vulnerabilities like buffer overflows and return-oriented programming. Exploiting these vulnerabilities would require direct access to the memory, but the BEAM VM hides the memory from the application code.

    While many business leaders are still trying to figure out how to put the technology to work for maximum ROI, most agree on two things:

    1. Blockchain unlocks vast value potential from optimised business operations.
    2. It’s here to stay.

    Unlocking the potential of technology

    Talking about blockchain implementation is no longer merely food for thought. Organisations should keep an eye on developments in blockchain tech and start planning how to best use this transformative technology, to unleash trapped value in key operational processes.

    It’s clear – blockchain should be on every company’s agenda, regardless of industry.

    If you want to start a conversation about engaging us for your project. Just drop the team a line.

    The post Blockchain Tech Deep Dive | Innovating with Erlang and Elixir appeared first on Erlang Solutions .

    • wifi_tethering open_in_new

      This post is public

      www.erlang-solutions.com /blog/erlang-and-elixir-blockchain-tech-deep-dive/

    • chevron_right

      Ignite Realtime Blog: Smack 4.4.8 released

      news.movim.eu / PlanetJabber · Thursday, 4 April - 17:04

    We are happy to announce the release of Smack 4.4.8, our XMPP-client library for JVMs and Android. For a high-level overview of what’s changed in Smack 4.4.8, check out Smack’s changelog

    Smack 4.4.8 contains mostly small fixes. However, we fixed one nasty bug in Smack’s reactor causing an, potentially endless, busy loop. Smack’s new connection infrastrucutre makes heavy use of the reactor, that enables tausands of connections being served by only a handful of threads.

    As always, this Smack patchlevel release is API compatible within the same major-minor version series (4.4) and all Smack releases are available via Maven Central .

    We would like to use this occasion to point at that Smack now ships with a NOTICE file. Please note that this adds some requirements when using Smack as per the Apache License 2.0 . The content of Smack’s NOTICE file can conveniently be retrieved using Smack.getNoticeStream() .

    1 post - 1 participant

    Read full topic

    • chevron_right

      Erlang Solutions: A Guide to RabbitMQ

      news.movim.eu / PlanetJabber · Thursday, 4 April - 12:20 · 5 minutes

    Looking to learn more about the basics of RabbitMQ? This powerful message broker plays a key role in modern, distributed systems.

    This post will break down its fundamentals and highlight its importance in the world of modern, distributed systems.

    An introduction to RabbitMQ

    RabbitMQ emerged from the need to create a scalable, robust messaging system that was able to handle high volumes of communications between applications, all while maintaining both data and performance.

    It is now a popular open-source messaging broker, with queue software written in Erlang. One of its key strengths is its ability to support and adhere to Application Programming Interface (API) protocols, for example, AMQP, HTTP AND STOMP.

    What are APIs you ask?

    They define the rules and conventions that allow for the interaction and communication of different software. For developers, APIs are the go-between that allows them to access a software or services functionality, without the need for a full understanding of the ins and outs of that particular system.

    In turn, these protocols offer a standard method of transmitting commands and data. The result? Seamless integration and interoperability between different systems.

    Let’s circle back to one previously mentioned protocol, the Advanced Message Queuing Protocol or AMQP. This protocol was made to ensure that messages are reliably delivered between applications, no matter where the platform it is running on is located. AMQP has precise rules for the delivery, formatting and confirmation of messages. This ensures that every message sent through an AMQP-based system, like RabbitMQ, reaches its intended location.

    Here’s an illustration better explaining the AMQP system:

    WLNyVn79-YOLOKFPxdXPwWcUNMU1zDFfgD7XJC7wTvD5CP6wDwME9yhMQ4Ji0sIJzRnIQ6wVfvX1r_nLpkzu9KI1o4tqdlSgRZesJ97N5KDCudIx5O1lW_jmbc6Nw2CQt6cnVPY67JMw_5-DqWR3E00

    Source: The Heart of RabbitMQ

    What is RabbitMQ used for?

    Developers use RabbitMQ to efficiently process high-throughput and reliable background jobs and facilitate the integration and communication between applications. It is also great at managing complex routing to consumers by integrating various applications and services.

    RabbitMQ is also a great solution for web servers that require a rapid-request response. It also effectively distributes workloads between workers, handling over 20,000 messages per second. It can manage background jobs and longer-running tasks, for example, PDF conversion and file scanning.

    How does RabbitMQ work?

    Think of RabbitMQ as a middleman. It collects messages from a producer (publisher) and passes them on to receivers (consumers). Using a messaging queue, it then holds messages until the consumers can process them.

    Here’s a better overview of these core systems:

    Producer (publisher) It sends messages to a queue for processing by consumers.
    Queue Where messages are transferred and stored until they can be processed.
    Consumer (receiver) It receives messages from queues and uses them for other defined tasks.
    Exchange The entry point for the messaging broker. It uses routing rules to determine which queues should receive the message.
    Broker A messaging system that stores produced data. Another application can connect to it using specific details, like parameters or connection strings, to receive and use that data.
    Channel Channels offer a lightweight connection to a broker via a shared Transmission Control Protocol (TCP) connection.

    kp3v0PXLxkDsL_nKMPs8IR55TsPsb5fRgzFaIVNVFuzStdjWTEhGBTNOEs-4SXuFEKvhuV-BQGGuOE2E7Ndp-p9xqoe82naibtoT1TeXP8_y_-7dSVatVyQN_W6r30q36-mb7Lzh7jLJv6v_BdH2ve8

    Source: RabbitMQ tutorials

    Key features of RabbitMQ

    As one of the most powerful and flexible messaging systems, RabbitMQ offers several key features, including:

    Security: Various security features in RabbitMQ are designed to protect systems from unauthorised access and potential data breaches. With authentication and authorisation support, administrators can control which users or applications have access to certain queues or exchanges. It also supports SSL/TLS encryption , to ensure clear communication between brokers and clients.

    Reliability: Reliable message delivery by supporting features, such as message acknowledgement and persistent message storage.

    Scalable and fault-tolerant: RabbitMQ provides features for building scalable and fault-tolerant messaging systems. It also supports clustering, whereby adding more nodes to the cluster allows the system to handle higher message volumes. It’s then able to distribute the workload across multiple nodes, making for efficient utilisation of resources. In the case of a node failure, other nodes in the cluster can continue to handle messages without interruption.

    Extended features: RabbitMQ is not limited to the AMQP protocol, but is very versatile and can support a host of others, such as MQTT and STOMP.

    Enterprise and the Cloud : RabbitMQ is lightweight and easy to deploy on the public as well as private clouds using pluggable authentication authorisation.

    Tools and Plugins: RabbitMQ offers a host of tools and plugins , ideal for integration and wider support.

    Common use cases for RabbitMQ

    We’ve already highlighted the versatility of RabbitMQ in modern distributed systems. With its robust features and flexible architecture, here are some most common use cases:

    Legacy applications: RabbitMQ integrates with legacy systems by using available or custom plugins. You can connect consumer apps to legacy apps for example, connecting JMS apps using the Java Message Service (JMS) plug-in and JMS client library.

    Distributed systems: RabbitMQ serves as a messaging infrastructure in distributed systems. It fosters asynchronous communication between different components, facilitating the scalability and decoupling of the system.

    IoT applications: When used in Internet of Things (IoT) applications, RabbitMQ can handle the exchange of messages between devices and backend systems, allowing for reliable and efficient communication, control and real-time monitoring of IoT devices.

    Chat applications: For real-time communication in chat applications, RabbitMQ manages messaging exchanges between users, facilitating group chat and instant messaging functionalities.

    Task/job queues: RabbitMQ manages task queues and distributes work across multiple workers. This means that tasks are processed efficiently and at scale, reducing bottlenecks and utilising resources.

    Event-driven architectures: RabbitMQ is great for carrying out event-driven architectures.

    It allows various system components to respond to events and seamlessly interact with each other.
    Microservices communication: A common use of RabbitMQ is enabling asynchronous and reliable communication between microservices. Messages are delivered, even if some services are unavailable.

    To conclude

    As businesses seek to adopt distributed architectures and microservices-based applications, RabbitMQ remains a go-to choice for improved adaptability and seamless integration across systems. If you’d like to discuss how RabbitMQ can improve your applications, get in touch with the Erlang Solutions team.

    The post A Guide to RabbitMQ appeared first on Erlang Solutions .

    • chevron_right

      Isode: Harrier 4.0 – New Capabilities

      news.movim.eu / PlanetJabber · Thursday, 4 April - 11:33 · 1 minute

    Harrier is our Military Messaging client. It provides a modern, secure web UI that supports SMTP, STANAG 4406 and ACP 127. Harrier allows authorised users to access role-based mailboxes and respond as a role within an organisation rather than as an individual.

    You can find out more about Harrier here .

    Server Administration and Monitoring

    Harrier 4.0 adds a Web interface for server administrators to configure Harrier. Key points:

    • Secure bootstrap
    • Sensible defaulting of parameters to facilitate startup
    • Per domain and global configuration options
    • Security features, including TLS, HSM, S/MIME and Security Labels/Security Policy
    • Full configuration of all Harrier options and capabilities

    In addition to configuration, the Web user interface provides a monitoring capability to show server activity and key operational parameters.

    UI Enhancements

    A number of improvements made to the Harrier UI including:

    • Variable size compose windows, retaining user preferences and stacking multiple windows
    • HTML Message editing:
      • Font bold/italic/underline/colour
      • Lists and Bullets
      • Reply to HTML messages
    • Undo and redo in message editor
    • Organizations in from selection has configurable default and alphabetic sort.
    • Active role shown on browser tab. Facilitates working with multiple roles in different tabs.
    • Extended message search capabilities to include:
      • Filter by precedence
      • Free text search in choice of: body; subject; SIC; action; info; from

    Security Enhancements

    The following security enhancements added:

    • Per domain S/MIME signing policy (never/if possible/always). Model is administrator choice rather than user selection.
    • Policy control of using S/MIME header signing.
    • Policy choice to alert users to unsigned messages.
    • Policy choice to allow encryption.
    • Policy choice of encryption by enveloping or triple warp.
    • Message Decrypt on initial access. The primary goal of S/MIME encryption is end to end protection. Some clients leave messages encrypted, which can lead to problems over time if keys become unavailable or are changed. Decryption prevents these issues. Note that for triple wrap, the inner signature is retained.

    Other Enhancements

    • Server option to force user confirmation of message send (audit logged). Important in some scenarios to confirm message responsibility.
    • Option to configure multiple address books in different directories.
    • Revalidation of recipients before message release.
    • Timezone option to be Zulu or Local.
    • wifi_tethering open_in_new

      This post is public

      www.isode.com /company/wordpress/harrier-4-0-new-capabilities/

    • chevron_right

      XMPP Providers: redlibre.es

      news.movim.eu / PlanetJabber · Saturday, 30 March - 00:00

    Available since Jul 9, 2023 · Website: ES
    Service
    Cost: Free of charge
    Legal notice: ES
    Bus factor : 1 person
    Organization: Private person
    Server
    Server / Data location: 🇪🇸
    Professional hosting
    Green hosting
    Server software: ejabberd 24.2.0

    Account

    You can register on this provider directly via:
    An email address is not required for registration
    A CAPTCHA must be solved for registration
    You can reset your password: ES
    Messages are stored for 14 days

    File Sharing ( HTTP Upload )

    Allows to share files up to 104 MB
    Shared files are stored up to 500 MB
    Stores files for 30 days
    Compatibility / Security
    Compatibility 100
    Security ( C2S ) unknown
    Security ( S2S ) unknown
    Contact
    Email EN
    Chat EN
    Group chat EN

    Provider Category

    C

    Categories explained
    Why not category "A"
    • Provider is too young or not listed long enough
    redlibre.es badge
    Embed badge

    This provider offers a Provider File .

    Latest change: Mar 9, 2024 · Something changed?

    Providers are checked for updates on a daily basis.

    Badge copied!
    • wifi_tethering open_in_new

      This post is public

      providers.xmpp.net /provider/redlibre.es/

    • chevron_right

      XMPP Providers: suchat.org

      news.movim.eu / PlanetJabber · Saturday, 30 March - 00:00

    Available since Jun 11, 2012 · Website: ES
    Service
    Cost: Free of charge
    Legal notice: ES
    Bus factor : 1 person
    Organization: Private person
    Server
    Server / Data location: 🇪🇸
    Professional hosting
    Green hosting
    Server software: ejabberd 24.2.0

    Account

    You can register on this provider directly via: You can register on this provider via a web browser
    Register (EN)
    An email address is not required for registration
    A CAPTCHA must be solved for registration
    You can reset your password: ES
    Messages are stored for 14 days

    File Sharing ( HTTP Upload )

    Allows to share files up to 104 MB
    Shared files are stored up to 500 MB
    Stores files for 30 days
    Compatibility / Security
    Compatibility 100
    Security ( C2S ) unknown
    Security ( S2S ) unknown
    Contact
    Email EN
    Chat EN
    Group chat EN

    Provider Category

    A

    Categories explained
    suchat.org badge
    Embed badge

    This provider offers a Provider File .

    Latest change: Mar 9, 2024 · Something changed?

    Providers are checked for updates on a daily basis.

    Badge copied!
    • chevron_right

      XMPP Providers: macaw.me

      news.movim.eu / PlanetJabber · Saturday, 30 March - 00:00

    Available since Mar 14, 2019 · Website: EN
    Service
    Cost: Free of charge
    Legal notice: EN
    Bus factor : 1 person
    Organization: Private person
    Server
    Server / Data location: 🇺🇸
    Professional hosting
    Green hosting
    Server software: ejabberd 23.10

    Account

    You can register on this provider directly via:
    An email address is not required for registration
    A CAPTCHA must be solved for registration
    You can reset your password: EN
    Messages are stored for an unlimited time

    File Sharing ( HTTP Upload )

    Allows to share files up to 104 MB
    Shared files are stored up to an unlimited size
    Stores files for an unlimited time
    Compatibility / Security
    Compatibility 100
    Security ( C2S ) unknown
    Security ( S2S ) unknown
    Contact
    Email EN EN
    Chat EN EN
    Group chat EN

    Provider Category

    A

    Categories explained
    macaw.me badge
    Embed badge

    This provider offers a Provider File .

    Latest change: Feb 2, 2024 · Something changed?

    Providers are checked for updates on a daily basis.

    Badge copied!