Real width of the image is 2.6 mm
#microscopy #microscopyart #magnification #zoom #lens #chemistry #dendrite #dendrites #dendritic #hydrogencarbonate #bakingsoda #doityourself
@etienne @silmathoron Yes I have actively used Matrix in the past, with the server running as a Docker container on a VPS. It was pretty awesome for the most part, and I even contributed some accessibility fixes to the Element client app on iOS. Was not aware of these latest shenanigans, quite unfortunate for sure. #Matrix is still an open protocol though, and you can use other server implementations such as #Dendrite. https://github.com/element-hq/dendrite
Dendrite seems the most promising, but it feels like even Element themselves have given up on it in favour of Synapse.
Synapse is written in Python and entirely single threaded.
There are ways around it's slowness like workers and sliding sync, but that makes it so many components that you almost have no choice than running a container which brings its own set of potential failure points.
2/3
Oh, this is just great.
I've been running an #dendrite #matrix server for several months.
Now it's marked as archived/read-only.
https://github.com/matrix-org/dendrite
Apparently it's further developed by Element.
I just wonder whether I can "simply migrate" my Docker-Compose setup.
Urgh. Back to #XMPP, it is, I guess. (Or maybe Signal, though I see that't not an option for everyone).
Welcher Matrix-Client?
Hallo Matrix-User, welche Desktop- / Web- / Mobile - Clients könnt ihr für den Messenger empfehlen? Es gibt ja verflixt viele zur Auswahl ... Welche sind eure Favoriten? Und wenn ja, warum?
#Matrix #synapse #Element #messenger #Messenger-Matrix #chat #OpenSource @linux @linux #FragDasFediverse #linux #schildi #fluffychat #commet #Cinny #conduit #dendrite
Happy and thrill to announce #hispagatos has moved from matrix #dendrite server to a #matrix #conduit server for people who had accounts please check #usenet for details http://newsgrouper.org.uk/hispagatos.comunicados/112/raw
I've installed Dendrite (Docker) and everything went smoothly except joining rooms. When I click join I get:
com.squareup.moshi.JsonDataException: Required value 'roomid' (JSON name 'room_id') missing at $".
Github issue: https://github.com/matrix-org/dendrite/issues/2284#issuecomment-1072030536
Logs: https://monogr.ph/66e7726fda4107196d7f948b
Is there any known solution to this?
Edit: Got rid of Dendrite and now using Conduwuit.
I love the idea of Dendrite, and it may well become the best server one day. I chose Synapse though, mainly just because the level of work and maturity that's gone into it.
Hopefully one day Dendrite will become Element's official server and the development focus there will increase.
Major caveat on this opinion though: I use synapse but have never tried Dendrite yet. It may be awesome, and I just don't know it yet...
Dendrite: ci ho provato. Ho bestemmiato. E ho rinunciato.
Magari ci risentiamo tra due annetti eh... anche se sarai ancora in beta
#matrix is so silly, even when enabling matrix.org as perspective key fetcher, #dendrite will send every. single. key. request. as a separate HTTP request. No wonder everything takes for-fucking-ever …
Where are people who know how to design systems, and why are they not designing our most important communication stacks?
Thinking about dropping Facebook - but for practical reasons I would still need to use Messenger.
Fine - I'll just bridge that into my #Matrix server with one of the excellent #Mautrix bridges.
"The homeserver is outdated (supported spec versions are below minimum required by bridge) bridge_requires=v1.4 server_supports=v1.2"
... right. I'm using #Dendrite, which is completely unsupported nowadays. No migration path to any other Matrix servers exist, which means all the users would need to manually be recreated and lose everything and yeah not happening.
@element really need to rethink how they're spending resources here. They're going to lose evangelists like this.
Finally got my matrix server back up and running.
In the directory with my config etc, there was a `README`, that said "Turning this down until Dendrite comes available!". Many years later and looks like that dream is dead </3
So jetzt läuft eine #sharkey und eine #friendica Instanz schon auf #docker und diverse andere nicht #fediverse Dinge
Jetzt fehlt eigentlich nur noch das ich ein #pixelfed und einen #synapse oder #dendrite Server mit Docker zum laufen bekomme.
#admin #gedankenspiele
Harvard claims breakthrough in anode behavior of solid state lithium batteries - One of the biggest issues facing the solid-state lithium-based batteries we all de... - https://hackaday.com/2024/03/06/harvard-claims-breakthrough-in-anode-behavior-of-solid-state-lithium-batteries/ #harvarduniversity #lithiumbattery #batteryhacks #siliconanode #solidstate #pouchcell #dendrite
Anyone out there which is running a #matrix server? I have some questions...
I'm running a synapse based server. Now I learned about "sliding sync". And I have no idea what to do. Do I need an extra service for this? Will this be implemented into #synapse at some point? Do I need to change my #element webclient to #elementx?
On a complete different field: How do I get phone number and SMS verification to work?
Is #dendrite the better/easier solution?
Please feel free to share/forward if you know someone which runs a matrix server or operates a #matrixchat
Following up on last month's news about Synapse and Dendrite, @element has begun implementing its planned forks, starting with Synapse.
We recommend reading their latest blog post for details: https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/
The Foundation is pleased to see that, not only do the forked projects remain under an open source license, but Element binds itself, through the CLA, to keeping 3rd party contributions in the open source commons.
So #Element decided to:
1. fork the server-side projects #Synapse, #Dendrite and closely related projects from the @matrix Foundation.
2. use AGPL-3.0 as the default license for ongoing development
3. implement a #CLA (Contributor License Agreement) in order to "own all copyright" (simplified) from future contributors
https://element.io/blog/element-to-adopt-agplv3/
The blog post specifically mentions proprietary forks they may create. What does this mean?
[ 3/7]