palordrolap@fedia.io said in Heroes & Villains of software development: > You don’t know how to do something in raw JavaScript. You’re not even sure you should. You find a library / module / package / whatever-the-name-is-this-week on the Internet. You paste it into your code. Your code now works. Your code is now 1MB larger. This web app is heavy, man.
npm install left-pad :D
Don’t quite understand the JavaScript one.
Definitely an overreaction lol.
But why are you not sold on Gemini? I mean, does it even need selling? Does Gopher need a selling point? They’re both deliberately simple protocols that work basically only on text. Gemini itself was conceived as an alternative to the modern web, deliberately simple in most ways, but not as simple as Gopher.
leetnewb@beehaw.org 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).
unknowing8343@discuss.tchncs.de 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.
@noodlejetski@lemm.ee Did not know that. Must be very recent.
@unknowing8343@discuss.tchncs.de 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.
@saltarello@lemmy.world funnily enough, I switched from Linkwarden to Hoarder. I like the smart lists. Just bookmark everything, check it later.
@hendrik@palaver.p3x.de no. I use the app service one. It works well, but it’s basically for bridging public channels. The Mautrix bridges all work very well. I’ve used the Facebook one in the past. It’s just the limits those platforms put on the bridge (e.g. banning or locking account) that can be a problem. If your bridge is connecting from the same place as you normally connect to Discord from, you should be fine.
@hendrik@palaver.p3x.de which discord bridge? For Matrix? The one that operates as a Discord bot works perfectly. Don’t know about the ones that want your login token.
There are several on F-Droid. There’s Energize and Food You, which integrate with some external food databases.