Recent searches

No recent searches

Search options

Only available when logged in.
wetdry.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
We are a community focused on gaming, tech, entertainment, and more.

Administered by:

Server stats:

724
active users

wetdry.world: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.5.0-alpha.2+chuckya

#prosody

2 posts2 participants0 posts today

Перевёл Prosody с sqlite на postgres.

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

Всё со всем заняло больше 3 часов. При этом импорт в Postgres занял от силы несколько минут.

Процедуру бекапа тоже переделал. Теперь перед архивацией дампа базы и данных происходит деактивация хоста через "prosodyctl shell", а потом активация назад.
Теперь как минимум могу нормально базу смотреть через pgAdmin. :)

#prosody#postgres#soft
From the looks of it I might be better off just writing something to migrate from #Prosody #SQLite to #Ejabberd #PostgreSQL directly without relying on the provided migrator, given Prosody's migrator chokes on my >10k archives.

(I'd otherwise need to write something to extract from Prosody SQLite to Prosody files first.)

Has anyone done this before?

TIL about slidge.im/, which is a set of bridges for #XMPP to other services (Whatsapp, Slack, Messenger, Discord, ...)

Took me ~2h to figure out how to make Whatsapp work with #Prosody. It consumes ~150MB RAM so I can still fit it on my RPi5.

Maybe I'll ditch #Matrix ? It's the fashionable thing to do these days...

slidge.imslidge.im — Gateways from XMPP to Other NetworksSlidge is a chat gateway library for XMPP built in Python, and a set of gateways for other networks.

I set up a #prosody #xmpp server, and I liked it. I tested both Linux and Android clients. I hit a wall getting people self-registered via #iOS. Self-reg works on #monal, but confuses the users with the default server so they always screw that part up. Even once logged in, I can't really recommend it. #snikket would have been perfect, but it obscures the usernames in group chats so as to be functionally useless. #siskin fails on self-registration, but everything else about it is good.

For those that run an #XMPP server, does it seem safe enough to enable XEP-0357 if one is concerned about third party data leaks to push notification services? Is #OMEMO enough to nullify concerns? I'm using #Monocles and #Prosody and I'm trying to optimize battery usage on #Android / #LineageOS

Edit: Daniel Gultsch of Conversations.im answered my questions [gultsch.social] Thanks!

MastodonDaniel Gultsch (@daniel@gultsch.social)@empathicqubit@mastodon.de using 357 is unlikely to have a positive impact on battery life. (due to the way #Conversations_im and forks work). If anything it can - in some circumstances - increase reliability. That aside the privacy impacts are probably fine. The worst that can happen is linking your Jabber ID to your Google account.
*

@nina_kali_nina I've been using #XMPP for the last year or so, wondering if the halcyon ICQ days of yore are still to be had.

After testing it with several friends connecting to my own self-hosted #Prosody server, here's what I found:

- Yes it all works, on all XMPP clients. But MacOS/iPadOS/iOS clients are not all that mature at this time. The #Linux (#Gajim, despite no video or audio calls) and #Android (#Conversations) XMPP clients are the best, IMHO. Always favor those, I say, and they are confidently installable and reliable today.
- Yes, use OMEMO encryption on personal chats. But when it comes to group chats, OMEMO is not necessarily the right move.
- If you don't need privacy in an XMPP group, then don't create a private group, but rather a _public_ group (the safer choice for reliability of message delivery). No OMEMO is possible in a public group, and the messages propagating around will be reliable, even to clients who vanish and re-appear after prolonged absences.
- If you really need OMEMO encryption in a group chat, create a _private_ group, not a public group. **Clients who vanish from the group for prolonged periods may miss out on some of the messages when they return (say, a few weeks later)**.
- I kept a wiki with several more quirks noted, which came up, and felt confusing and frustrating to my (non-geek) friends using XMPP.

As to your Apple-ecosystem-confined friends, at this moment in time, maybe talk to them 1:1 in #Fluffychat/Matrix, which affords encryption, and is all #OpenSource, like everything above. (Groups in #Matrix have a track record of failing for everybody in them very badly every 2 or 3 years or so.)

*

Hello!

Does anyone know of a public Prosody XMPP server? In light of recent events in Matrix I wanted to try XMPP.

Also could someone explain OMEMO encryption to me? I know Prosody supports it, but is it on by default?

Thanks!

EDIT: Found an instance

#XMPP#Matrix#OMEMO
*
Jetzt habe ich etwas mehr Zeit,... also,... 🙂

Wenn man sich entscheiden sollte, einen Account bei einem Anbieter zu erstellen, muss man bei der Wahl etwas aufpassen. Ein #XMPP #Server muss gut konfiguriert sein, wenn man die "modernen Funktionen" nutzen will. Um ein Beispiel zu nennen:
Möchte man Nachrichten auf unterschiedlichen Geräten lesen und diese auch, wenn das Gerät offline war, dann muss der Server eben ein bestimmtes Setup haben. Fileupload von 10 MB ist bei den ganzen Katzenvideos auch nicht mehr ausreichend. 🙂

Ich sag es nur, weil Benutzer schon schlechte Server gewählt haben und dann der Meinung waren, XMPP erfüllt nicht ihren Anforderungen. Das ist immer Schade, weil es oft sicherlich nicht so ist.

Möchte man seinen eigenen Server für Familie auf einem #Debian System betreiben, dann kann man sich Prosody ansehen. #Prosody hat eine sehr gute Dokumentation. https://prosody.im/doc Da es am Anfang jedoch vielleicht etwas "viel" sein kann, habe ich mal angefangen meine Konfiguration im Wiki zu beschreiben: https://wiki.debian.org/Prosody/HowTo Am besten mal in Debian Backports gucken, dort liegt eine neuere Version als in stable.

Es besteht auch die Möglichkeit bei XMPP Provider seine eigene Domain zu hosten.

Zu #snikket kann ich selber nicht sagen, weil ich es mir nicht angesehen habe. Man macht damit aber sicherlich nichts falsch.

Ejabberd war auf einem Debian System schnell konfiguriert. Wenn ich mich richtig erinnere, dann musste man gar nicht so viel konfigurieren. Soweit ich weiß, fehlt es hier aber an Funktionen wie "Einladungen" - was eben im privaten Bereich schon sehr hilfreich ist. Die Doku war auch sehr gut und man hatte auch eine gute Beschreibung vom Datenbank Schema.

Mit Smarthome kenne ich mich nicht aus, aber wenn man etwas mit XMPP "spielen" will, dann man sich xmppc und go-sendxmpp ansehen. Alternativ hätte ich auch einen modularen Bot anzubieten, aber da muss man vielleicht noch etwas programmieren.

Morgens um 6 und um 14 Uhr bekomme ich meine Termine per chat:

0 6 * * * xmppc -m message chat me@dein.server.local "`gcal -c`"

CC: @Monal@fosstodon.org [fosstodon.org] @zeank@mastodon.social [mastodon.social] @aardjon@social.tchncs.de [social.tchncs.de] @ebillen@nrw.social [nrw.social] @snikket_im@fosstodon.org [fosstodon.org]
prosody.imDocumentation – Prosody IMIndex of documentation topics

@vascorsd I had something similar to that happen to me recently as well. I'm using a #prosody server, and I have my:

archive_expires_after = "5w"
... set in /etc/prosody/prosody.cfg.lua

Messages should be archived for 5 weeks.

Then messages sent in Gajim on one linux laptop were lost, when a second #Linux laptop who was subscribed to the same group, was turned off (absent from receiving messages) for 3 weeks. 2.75 of the 3 weeks worth of the group messages (where the laptop was turned off) silently never showed up, when #Gajim was re-opened on the second laptop.

This bodes very badly for me recommending XMPP to others. I now consider #DeltaChat to be a secondary choice, should something happen to #Signal (which is currently my privacy-respecting Messaging app goto).

Other clients who chatted in that same group, BTW: the latest stable #Monal in #iPadOS, and #Conversations in #Android

Prosody version is 13.0.0-1~bpo12+1, backend is sqlite, Gajim is 2.1.1. It was a private MUC, and OMEMO was used as much as possible.

#XMPP
*

For those (all 2 of you) wondering what happened to my #snac instance, I decided that the limitations while initially well intentioned, were now less limiting due to the scope of the project and features being added over time - meaning it was almost back to a full-featured platform and I might as well be back on something like this.

So #Akkoma was, for me, the logical choice spin up. I see in the documentation it has #ejabberd integration, so might yet utilise that so I can sign into #xmpp with the same account, which would be kinda cool.

I am running both #prosody and #ejabberd for testing and am unsure which I prefer as yet. Possibly ejabberd for the webmin, which is quite nice.

*
TrendingLive feeds
About