Happy #GlobalSwitchDay

[solarpunker@slrpnk.net]

SimpleX is better, you don't even need a phone number.

[solarpunker@slrpnk.net]

[syrc@lemmy.world]

[dicjacobus@lemmy.world]

[solarpunker@slrpnk.net]

[solarpunker@slrpnk.net]

[solarpunker@slrpnk.net]

The best number-free protocol is SimpleX atm

[phx@lemmy.ca]

[whyjiffie@sh.itjust.works]

It's been here the a long time actually

[whyjiffie@sh.itjust.works]

[whyjiffie@sh.itjust.works]

I haven't heard of it yet but it's very interesting! link for those who struggle to find it among german search results

[whyjiffie@sh.itjust.works]

or they can also disable submitting issues for now

[whyjiffie@sh.itjust.works]

anti? is it against libre software? because it doesn't seem so

[whyjiffie@sh.itjust.works]

sender, recipient, chatroom, what kind of event you sent (message, emoji, reaction, vote), if you responded to a message, room privilege changes, etc

but it's a question how big of a problem is that. they want to tackle it in the future, but that's far away for now I think

[whyjiffie@sh.itjust.works]

Matrix still lacks some signature fearures of discord that its users like, like one-click voice channels (I heard Element is experimenting with it with video) and guild/channel-level roles. role based access control is being planned for a long time, but it doesn't really go forward unfortunately

[stevo887@lemmings.world]

I saw someone suggest Yandex as a Google substitute in de-Google thread recently...lol

[jollyrogue@lemmy.ml]

Matrix servers keep a copy of any remote room an account on the server has joined, and it’s possible to recreate a room from the copies held on different servers. There are more details I don’t remember, but at a high level that’s how it’s distributed.

Storing messages of remote rooms in addition to local rooms is why people complain about the storage requirements of Matrix servers. They don’t realize it’s distributed.

[doctorbllk@programming.dev]

It's also a pretty rough experience tbh. It took about 2 days for me to gain access after signing up. Only usable via the Android sdk or iOS beta app. The infrastructure just isn't there yet.

[kalcifer@sh.itjust.works]

I wish Boost understood the collapsible spoilers.

On my client, it’s all expanded and I see all the formatting characters.

Ah dang, that's good to know (though I'm not sure what to do as an alternative) — I was unaware that the collapsible spoilers weren't supported on Boost. I guess that means that Lemmy's markdown formatting hasn't entirely been standardized across the service. I personally have encountered some inconsistency on the Tesseract UI with CommonMark Autolink ^[2]^ formatting where the autolinks don't even render ^[1]^.

::: spoiler References

1. "Kalcifer" @[email protected]. To: ["Happy #GlobalSwitchDay". @[email protected]. "Fediverse" [email protected]. Tesseract. sh.itjust.works. Published: 2025-02-01T07:08:40Z. Accessed: 2025-02-02T04:40Z. https://tesh.itjust.works/post/sh.itjust.works/32046509.]. Published: 2025-02-01T09:20:14Z. Accessed: 2025-02-02T04:42Z. https://sh.itjust.works/post/32046509/16425699.
   • Raw Text:

     Signal isn't federated ^[1][2][3.1]^; it's decentralized ^[1][2][3.2]^. Though, for all practical purposes, I would generally argue that it's centralized. 
     
     ::: spoiler References
     1. Signal-Server. signalapp. Github. Published: 2025-01-31T15:34:14.000Z. Accessed: 2025-02-01T09:24Z. <https://github.com/signalapp/Signal-Server>.
        - This is the source code for the server that Signal uses.
     2. "Signal (software)". Wikipedia. Published: 2025-01-06T09:34Z. Accessed: 2025-02-1T09:30Z. <https://en.wikipedia.org/wiki/Signal_(software)>.
        - ¶"Architecture". ¶"Servers".
          > Signal relies on centralized servers that are maintained by Signal Messenger. In addition to routing Signal's messages, the servers also facilitate the discovery of contacts who are also registered Signal users and the automatic exchange of users' public keys. […]
     3. "Reflections: The ecosystem is moving". moxie0. Signal Blog. Published: 2016-05-10. Accessed: 2025-02-01T09:40Z.  <https://signal.org/blog/the-ecosystem-is-moving/>.
        1. ¶5. to ¶"Stuck in time". ¶3-6
           > One of the controversial things we did with Signal early on was to build it as an unfederated service. Nothing about any of the protocols we’ve developed requires centralization; it’s entirely possible to build a federated Signal Protocol-based messenger, but I no longer believe that it is possible to build a competitive federated messenger at all. […] [interoperable protocols] [have] taken us pretty far, but it’s undeniable that once you federate your protocol, it becomes very difficult to make changes. And right now, at the application level, things that stand still don’t fare very well in a world where the ecosystem is moving. […] Early on, I thought we’d federate Signal once its velocity had subsided. Now I realize that things will probably never slow down, and if anything the velocity of the entire landscape seems to be steadily increasing.
        2. ¶"Stuck in time". "Federation and control". ¶6.
           > An open source infrastructure for a centralized network now provides almost the same level of control as federated protocols, without giving up the ability to adapt. If a centralized provider with an open source infrastructure ever makes horrible changes, those that disagree have the software they need to run their own alternative instead. It may not be as beautiful as federation, but at this point it seems that it will have to do.
     :::
     

     • Rendered:

     

     • In the rendered text there are no links; however, there should be links at the end, as is shown by the CommonMark autolinks in the raw text.
2. "CommonMark Spec". John MacFarlane. CommonMark. Version: 0.31.2. Published: 2024-01-28. Accessed: 2025-02-02T04:51Z. https://spec.commonmark.org/0.31.2/#uri-autolink.
   • §6.5 "Autolinks". ¶2.

     A URI autolink consists of <, followed by an absolute URI followed by >. It is parsed as a link to the URI, with the URI as the link’s label.
     :::

[kalcifer@sh.itjust.works]

Dang . See my comment for a related response.

I recommend reporting the bug to the Sync devs to fix their Markdown formatting to improve feature compatibility between them and the Lemmy UI.