- From: Han Wammes <han@wammes.org>
- Date: Tue, 17 Jan 2023 12:15:33 +0100
- To: Matthias Evering <me@evering.eu>
- Cc: public-solid <public-solid@w3.org>
I would appreciate if we would come up with our own service for two reasons: 1. Eat your own dogfood 2. If we want to distinguish Solid from the rest (mastodon, matrix, …) we need to ensure to start leveraging our USP’s i.e. true contextual data interoperability (versus file exchange). Best regards, Han Wammes Solid Community NL > Op 17 jan. 2023, om 12:00 heeft Matthias Evering <me@evering.eu> het volgende geschreven: > > Am 17.01.2023, 11:34 Uhr, schrieb Melvin Carvalho <melvincarvalho@gmail.com>: > >> The Gitter service is ending on 6th Feb >> https://blog.gitter.im/2023/01/16/gitter-is-going-fully-native-matrix-in-feb-2023/ > > they say we need a logout/login but functionality will stay around if I understand right. > >> 1. What about the history > > see https://github.com/solid-contrib/gitter-solid/issues/34 > > I wonder if the various history links will sill work, and for how long > >> 2. New chat area >> Gitter is encouraging a transition to the Matrix/Element service. > > does that mean we need a Matrix account or anything ? > > Perhaps we could start a single room, say, on Mattias' solidweb which is a > running grass roots solid server. > > I will participate in these efforts if the community wants. > >> We would need to circulate an agreed upon URL for this to work. > > we can make a dedicated pod for that purpose and freely choose any URL. > it would look like `https://chatpod.solidweb.org/public/container` > >> It could be beneficial to consider using Solid for chat, though based on >> the current low volume of chat on gitter it may not be a major concern. > >> Thoughts ? > > let's try to prepare best for feb. 6th. I have sympathy for eating own dogfood. > > Matthias > -- > Matthias Evering (@ewingson) >
Received on Tuesday, 17 January 2023 11:18:10 UTC