It's an interesting idea. Could be a way to catch interest and education.
Now to read people hating Mozilla for shutting down a service and focusing on the browser.
Which is what people kept saying they should be doing!
[email protected] said in Is there a way I can make my XMPP Conversations messages synced to my desktop?:
Well, the blog post for it is from January 2025. https://signal.org/blog/a-synchronized-start-for-linked-devices/
So I guess it has not been around too long! But it's interesting they've added it. Sounds like it works similarly to the existing message transfer, but with the addition of multiple encryption keys (similar to how Matrix does it).
[email protected] it also seems that Conversations now has the ability to preserve message history when moving devices. Of course this is different than moving between clients, but it's a step in the right direction.
@[email protected] Did not know that. Must be very recent.
@[email protected] in this case, it was designed explicitly as a security feature. It's not uncommon for end-to-end encrypted services to have this limitation. Signal has it, for example. Only way you can keep your message history with Signal is to migrate it directly from installation to installation, and it doesn't sync old messages when setting up the desktop client.
But, you should be fine if you have a backup of Conversations, at least on Conversations itself.
OMEMO by design does not allow old messages to be decrypted by a new device. However, anything going forward should sync between all XMPP clients that implement proper XEPs. The server also has to support the XEPs. But if you're using OMEMO, then you should also already have the other XEPs required for proper messaging experience. Specifically, the XEP for syncing messages across clients is Message Carbons.
Matrix is able to decrypt past messages on new devices, but that's because it stores your keys (encrypted) on the server and does a bunch of funky key fetching and passing between sessions to allow message decryption from new verified sessions. OMEMO does not have this function.
@[email protected] the original wood was on the island. After it was all chopped down, driftwood became very valuable. A lot of farm fences still use driftwood to this day in Iceland. Otherwise, most lumber is imported. There's a very (very) limited "logging" industry that produces some lumber, but it isn't really at the scale that could support Iceland being self sufficient for lumber.
How would this work on the NodeBB side? Multiple categories associated with one topic?
Ideas for Federation
In my ever-continuing use of NodeBB as a single-user Fediverse instance, here are some things I've noticed. Both things I've already talked about before, and some new things. These are some suggestions for functionality or perhaps plugins.
- Confusion between following remote categories as a user and the synchronization options in category settings as an admin. I think the category synchronization should be repurposed somewhat. The suggestion from @[email protected] was to perhaps rework it as a cross-posting feature.
- Right now, the feature relies on the other ActivityPub endpoint to be able to follow the NodeBB category, which (notably Lemmy) does not always work.
- Making a "proxy user" is a pretty common solution to this, used by Misskey etc. One single system proxy user can follow all remote categories, and then NodeBB itself can handle the synchronization.
- Lack of posts. This is a gener
@[email protected] still an impressive feat, though. Surprised that anything resembling modern software even runs on a system that old now. Probably requires an ancient kernel version and other things. Is there anywhere where they detail this process more specifically? (I only had time to skim the article)
Such a joke of a country.
I am using Futo Keyboard. Downloaded it when it was marketed as open source. Unfortunately found out a few days ago it isn't actually open source. It's still a damn good keyboard, but it's still unfortunate. AGPL exists for a reason. Oh well.
@[email protected] It would be good for outgoing posts if cross posting is used for synced categories. But it doesn't solve the problem of incoming posts. For that, it would make sense to still slot incoming posts based on the sync setup. But there is still the problem of Lemmy not accepting follows from category actors.
@[email protected] Cool, I can now load it. Another question: I have a bunch of lemmy communities (and also a few "null" entries) stuck on "pending" in the category synchronization settings. Pressing remote/delete doesn't do anything. Is there an easy way to get rid of them by editing the database?
Also, are there plans to merge the federation synchronization and new remote category following stuff together into one cohesive set of functionality?
@[email protected] Yes, maybe? https://forum.agnos.is/category/[email protected] for example. Maybe it's not federated? Since I don't see anything about what fediverse handle to use like in the ActivityPub forum.
Yep, shows up now on my end. Maybe check other categories too?
@[email protected] I was able to access it from a Lemmy instance. So it is federating, at least partly. But interesting to know that Mastodon has issues with it...
One thing that might be helpful is that NodeBB gives an invalid ID error when trying to follow the category via the sync function in admin settings. Stack trace shows it's the error being thrown when trying to follow (activitypub.js line 43).
So, this URL does work: https://forum.agnos.is/category/[email protected]
Maybe it has something to do with the activitypub category being a sub-category of nodebb development?
@[email protected] could not run it in dev mode directly because of docker compose, but did set NODE_ENV to development and got verbose logs. Only thing that shows up is:
undefined
2025-05-03T19:35:59.553Z [4567/53] - warn: Route requested but not found: /category/[email protected]