Skip to main content

Search

Items tagged with: matrix


What's been happening this week in Matrix? Circles in F-Droid, Elm refactoring, big changes in LibMatrix, new release of Trixnity, FOSDEM, and more! 🔥

matrix.org/blog/2024/02/02/thi…

#TWIM #Matrix


The Matrix.org Foundation is pleased to share that today, alongside @mozilla, we have joined @OpenForumEurope as supporters.

OpenForum Europe has proven an effective convener and advocate for open source and open standards in Europe, and we’re glad to help further that work: openforumeurope.org/mozilla-an…

#Matrix #OpenSource #OpenStandards #EU


The @dweb HQ is hosting a virtual meetup next week, Feb 7th, at 5pm PST

> "Join us at our first virtual DWeb Meetup of the year! (Rescheduled from this week) We'll be featuring lightning talks from projects across the DWeb ecosystem. Afterwards, we'll try meeting for an after-event hang out on Third Room—a virtual world platform built on the federated messaging protocol, #Matrix"

@matrix

RSVP on Eventbrite to join eventbrite.com/e/dweb-meetup-f…

#event #dweb #VirtualEvent


Today we launch a new fundraiser, talk about the scope of the Foundation's work, and begin to unpack our emerging roadmap for the future 🚀

There is a lot going on and we need your help to keep it going!

matrix.org/blog/2024/01/2024-r…

#Matrix #OpenSource #OpenStandards #FOSS #Interoperability


Thunderbird als Matrix-Client

Seit Thunderbird 102 ist Matrix standardmäßig aktiviert. Ich habe mal einen Blick darauf geworfen.

#Thunderbird #Matrix #Matrix_Client #Chat #Linux

gnulinux.ch/thunderbird-als-ma…


@delta is this also addressing / solving your issue on iOS?

#UnifiedPush #matrix


This week, next gen @element client, Element-X, and @neochat announced they are supporting #UnifiedPush. This makes 2 more @matrix clients supporting it !

NeoChat the second Linux app officially supporting UnifiedPush, after @tokodon

#matrix


I collected a few stories about what happened in and around Matrix in 2023: blog.neko.dev/posts/matrix-yea…
The post got a little delayed, because stuff never stops happening, but if you still want to read it, it is here now!

#matrix #2023


kind of shame at @bitwarden not place one from most noticeable and oldest email clients around which now supports #OpenPGP and #matrix ;/


We're proud to bring you the Creative Freedom Summit as a free virtual conference hosted entirely with **open source software**!

The talks are hosted on Jitsi, piped into @element where we also use a @matrix room for live chat, and also streamed live on @peertube where they will be immediately available for viewing after the event. Pretty cool!

Join the Creative Freedom Summit in 3 easy steps: creativefreedomsummit.com/

#CreativeFreedomSummit #ArtWithOpenSource #Matrix #PeerTube #OpenSource


Have you seen the Stack Overflow Developer Survey results for 2023?

Of the 83,830 folks surveyed, Matrix is the #1 chat tool in terms of current users' satisfaction. It's also rated as the most desirable among the open source tools listed, but there is a _lot_ of room for improvement in awareness there.

Let's build on this in 2024! 🚀 survey.stackoverflow.co/2023/#…

#Matrix #StackOverflow #FOSS #OpenSource


Hey #fediverse,

Can y'all Please tell #NPR about #mastodon, #activityPub (and #Matrix!), please?

No really.. They're literally asking for it,

npr.org/2024/01/11/1223974976/…

Ok, I could be reading too much into it, but it really would be nice if maybe I wasn't the only one that mentioned maybe it's something they should look into?

kthx,
- A. Rando


That is not what is happening here.

Anyone can fork an open source project, and they frequently do to varying degrees of success. @element isn't even the first company to fork Foundation-hosted projects.

Forks of projects hosted at other foundations, such as the ASF, don't make those foundations less relevant.

#Matrix


matrix.org/blog/2023/12/electi…

I wonder what rlevance the @matrix foundation has while it moves all relevant projects into the for-profit @element corporate.

#Matrix


@Lukáš Tyrychtr Thank you very much for preparing great accessibility improvements for #fractal. It's now merget and available in Fractal 6 beta! #Accessibility #Matrix


The next release of the js sdk is planning to bump the supported #matrix spec version to 1.5 or 1.6. This means it and as a result also Element Web will refuse to start on current versions of #conduit and #dendrite. This is an intentional decision resulting from a discussion between several SCT members.

I think that approach is bad and it should check for a range of supported versions instead of arbitrarily bumping the minor version to make the ecosystem move, but this is a heads up, that now is the time to contribute to both of those servers, if you use them and want to use the Element Web client on them going forward. (I already had my discussion with the SCT and I won't tell other projects, what they should do.)

JS-SDK change: github.com/matrix-org/matrix-j…Dendrite supported versions: github.com/matrix-org/dendrite…Conduit supported versions: gitlab.com/famedly/conduit/-/b…


I'm very excited to be presenting at FOSDEM in February! I've been working on messaging interoperability for about 2 years now with much of that focus being on developing an open standard for that exact purpose. We'll be exploring how #Matrix works as an existing decentralized open standard for *interoperable* communications, and how other protocol development work interacts with Matrix.

Join me for a technical look at #MIMI, #DMA, and the Matrix protocol: fosdem.org/2024/schedule/event…


Who Cares Who Delivers Our Notifications?


Android or iPhone — either Google or Apple delivers our messages — surely? You don't accept that?

Time I Learned: there are freedom-respecting phones.


People who do not want to depend on Google or have them control our devices are using android-compatible but not google-controlled phones, a.k.a. “degoogled phones”. We have been asking (ourselves) for several years if we can have google-free push notifications. Thanks to the developers of the UnifiedPush standard, the answer is now, “yes!”

But why?

You've probably heard of the Observer Effect. Partly influenced by hearing that someone is observing my blog from a social psychology angle relating to attitudes among the open source community, but also I was already thinking I should, I've decided to write more about why I write/build/care about the topics I choose. For a start I wrote a “Why Would I Care?” section for my latest post Google-Free Push Messaging for Google-Free Phones. Here, that section is published as an article on its own.

Why Would I Care?


Why would I care how my push notifications reach my phone? What difference does it make to me?

That's a good question. Inside a building that has a good heating, ventilation and air conditioning system, we don't notice the system, we just feel comfortable. With push notification delivery, part of the answer is the same: the system just does its job and our notifications come through. Whether the delivery channel is controlled by Google or by us or by someone else doesn't change that. The immediate, concrete result is the same. So it's not about wanting it to function differently; that's not why I care.

The difference it makes to me is about freedom, privacy, independence, self-agency. I am happy to have the choice to use any particular company's service, but I am not happy to be forced to use them, to have no choice, if I can't leave no matter how bad it gets. What if I don't like Google monitoring my notifications to know what I'm doing? What if I don't like to live in fear of offending them in some way and being cut off from their service and having no replacement option? What if I just don't want to condone their business model by using it, but I still want to be notified when I have messages?

Push notification delivery is one of the many invisible technical services that underpin our online communication systems. These kinds of services are implicitly considered to be part of the public infrastructure, something that we now assume is available to everyone.

When we allow ourselves to become dependent on any particular company's service, and yet do not regulate it as a public service provider, then we subject ourselves to the company's whims, priorities and values, which are different from ours. They will inevitably act against public interests.

Building publicly owned infrastructure based on open standards and freedom software is therefore essential to ensure the independent provision of services aligned with public needs and values.

I am one of the people who feels it is my place to use, promote and build non-proprietary public services, both for my own mental wellbeing and because I believe it is important for society.

It is the same reason why I support: open Ed-Tech, degoogled phones, #matrix, #fediverse, freedom software, open-source hardware, #rightToRepair.

Speaking as one of the people who prefer our devices not to be controlled by and dependent on Google:

What do we want? UnifiedPush!

When do we want it? Now!


I would love to work on any freedom tech project bringing UnifiedPush to a wider audience.


See my other posts tagged... #unifiedPush #degoogled #awesomeFOSS


Follow/Feedback/Contact: RSS feed · Fedi follow this blog: @julian​@wrily.foad.me.uk · use the Cactus Comments box above · matrix me · Fedi follow me · email me · julian.foad.me.ukDonate: via LiberapayAll posts © Julian Foad and licensed CC-BY-ND except quotes, translations, or where stated otherwise


Google-Free Push Messaging for Google-Free Phones


UnifiedPush open-standard push messaging complements degoogled android-compatible phone OS's such as LineageOS.

People who do not want to depend on Google or have them control our devices are using android-compatible but not google-controlled phones, a.k.a. “degoogled phones”. We have been asking for several years if we can have google-free push notifications. Thanks to the developers of UnifiedPush, the answer is now, “yes!”

The open standard UnifiedPush.org has now been created. While not a large number yet, a useful handful of apps already support UnifiedPush, including several matrix and fediverse apps. For its servers and the associated client-side “distributor” component, there are multiple successful implementations deployed.

The current situation is such that anyone can use UnifiedPush on an android-compatible device by installing their choice of UnifiedPush distributor app (which must run in the background), configuring it to connect to their chosen U-P server (compatible with chosen distributor), and then installing any number of U-P-aware apps which will then use it (without needing per-app configuration to do so).

In android-compatible OS ROM projects such as LineageOS, implementing some core support for the UnifiedPush.org standard now seems to me like the right way to go. Exactly what form of support is to be decided.

Involving the OS ROM


Some ways an OS like LineageOS could usefully be involved to improve the UnifiedPush experience are:

  • ensuring the U-P distributor app has a convenient way to be installed and permitted to run in the background, free from restrictions, because getting this right is critical and if the user installs the distributor manually it can be tricky to get right; (investigate: would it need to be a system app, or some kind of whitelisting (ugh), or be split into a system component and a user component, or what?)
  • providing a convenient way to let the user (or the OS distribution provider) configure the distributor's U-P server address: perhaps rather than using an ad-hoc UI provided by the distributor app, it could integrate with “accounts” settings.
  • potentially providing a system settings UI for monitoring the U-P connections and which apps are using them.

Thoughts on the role of microG. The purpose of microG as best I understand is to provide Google compatible APIs to apps which expect Google services. Underneath these APIs, it provides access to a mixture of actual Google services, alternative real services, and fake services. As far as I know it does not so far provide any non-Google APIs, and yet for push notifications the provision of UnifiedPush APIs might be a good fit for fulfilling its overall purpose as a compatibility layer. Or perhaps not, perhaps that is out of scope and should be in LineageOS or another add-on layer instead. I'm sure the folks involved will work out what is best.

Constraints, FCM Fallback, non-Android


Unlike the situation with some other google APIs, it is important to note that an OS compatibility layer such as microG cannot automatically divert the connections made by apps built using Google's FCM, to use U-P instead. The apps must be modified.

However, the inverse is possible: a UnifiedPush aware app can automatically “fall back” to using Google's FCM if U-P support is absent and FCM support is present. See details of the Embedded FCM Distributor in UnifiedPush documentation.

Non-Android devices can use UnifiedPush too, including Linux phones such as PinePhone and Purism Librem. The UnifiedPush D-Bus spec may be relevant. (On locked-down proprietary devices such as Apple's it is unlikely to be possible, nor to make much sense: FAQ.)

Packaging a UnifiedPush Distributor


A U-P distributor app could be built in to an OS or subsystem like microG but there is a significant down-side to that: it would support only one type, or at most a fixed small number of types, of U-P server. Choosing a distributor type is more of a whole OS packaging decision. In cases where the whole OS is related to a service provider of some kind (so not like LineageOS, but perhaps like Murena/Calyx/Graphene etc.), the service provider might choose to run a U-P server for their users and have their distributor automatically connect to it (with user consent/opt-in/opt-out). In the more generic/self-hosted case (like LineageOS) it makes more sense to leave it to the user to install their preferred U-P distributor.

I would love to see distributors of google-free phones, such as Murena, support google-free push notifications. I posted a brief sketch of a UnifiedPush Plan for Murena /e/-OS on their forum, without attempting to go into details of integrating the U-P distributor into the ROM.

History


A rough time line of UnifiedPush development. (From light research and having followed it through its development.)


Conclusion


Whatever the specifics of how any android-compatible OS ROM project might choose to proceed with google-free push support, the solution space enabled by UnifiedPush now exists. Speaking as one of the people who prefer our devices not to be controlled by and dependent on Google:

What do we want? UnifiedPush!

When do we want it? Now!


See my other posts tagged... #unifiedPush #degoogled #awesomeFOSS


Follow/Feedback/Contact: RSS feed · Fedi follow this blog: @[url=https://social.jsts.xyz/users/8mflxtuvnp]Julian[/url]​@wrily.foad.me.uk · use the Cactus Comments box above · matrix me · Fedi follow me · email me · julian.foad.me.ukDonate: via LiberapayAll posts © Julian Foad and licensed CC-BY-ND except quotes, translations, or where stated otherwise



After two and a half years of rewrite, #Fractal 5 is finally out! Get the #GTK 4 #Rust #Matrix client from flathub.org/fr/apps/org.gnome.… and enjoy new features such as #EndToEndEncryption, location sharing, or multi-account with Single-Sign On 🚀

:boost_ok:


Ну и что, по-вашему, можно обычным людям советовать использовать мессенджер, у которого в настройках такое?..

#Matrix #мессенджеры #пиздец


@Matthias ✔ I can't make it work. Perhaps it's not enough keyboard accessible or something similar. Can you please try to describe how you use this feature in slightly more details please? When trying to mention your display name I start typing the @ sign followed by mat, then pressing up or down arrow keys I am expecting I should be able to select from the list of suggestions. Pressing the tab key to trigger the auto complete is not working the way I would expect as well. To reference an accessible autocomplete implementation I can point out #element #matrix client for example. When using #tuskyapp with my #friendica account I can autocomplete #Hastags but I can't complete user mentions.


Mainstream social media and messaging apps (#Facebook, #WhatsApp, #Instagram etc) are a nightmare for our personal data and freedoms.

We have #FreeSoftware replacements for most of these services but maintaining these services has recurring cost and effort.

diasp.in is a community project supported by volunteers. We offer #diaspora, #matrix and #xmpp services.

If we don't find enough volunteers by October 31st, we will be forced to shut it down.

Please volunteer at diasp.in/volunteer


Wow, groupchat support for #WhatsApp? That's huge!
I guess I'll try #slidge now after all! 😀
Also looking forward for the #matrix bridge.
#slidge #xmpp #gateway


Communal Bonfires; creating space for group-scale discourse on top of @matrix

blog.erlend.sh/communal-bonfir…

Today we're pre-releasing Commune, our first foundational step towards a community platform built specifically for alignment with digital gardens.

Cyber-ecological messaging anyone?!

It's an evolving piece of software serving as the primary bonfire component of the overarching Community OS concept.

github.com/commune-os/commune-…

#fediverse #opensource #threadiverse #community #matrix


There we go, matridge first public commit!

It's an #XMPP server component acting as a #Matrix puppeteering gateway, based on slidge. It only supports public unencrypted group chats for now, but has cool features such as emoji reactions, rich replies and message retractions.

git.sr.ht/~nicoco/matridge
git.sr.ht/~nicoco/slidge


what.

Cactus Comments has now seen over 1.2 million unique users - only counting guest users on our free public instance.

Guest users on instances not hosted by us and signed in users on any server don't even count in this statistic.

cactus.chat has to be the Matrix server with most guest users at this point...

I keep spotting cactus in the wild as well. Last week I saw someone using it for the comment section of a livestream! So cool.

🌵 #cactuscomments #matrix

cactus.chat


Live location support and room maps coming to #KDE's #Matrix client @neochat: volkerkrause.eu/2023/06/24/mat… - powered by #OSM of course.


Hey @matrix check this out.

survey.stackoverflow.co/2023/#…

#Matrix is the the most admired synchronous tool for developers tool according stack overflow survey.


🚨 🇮🇳 #India banning #OpenSource #Matrix clients like #Element is equivalent to banning your favorite web browser or email client.

🤯 Can you imagine if Firefox, Chrome, or Thunderbird were banned nationally?

🔑 Privacy is a human right.

➡️ And governments will never stop human rights abuses by denying its citizens' human rights.

:boost_love: Pass it on.

timesofindia.indiatimes.com/in…