I’m getting more curious about federated chat applications – it feels like a very active area of development, and yet chat feels so old – how long as XMPP been around? So it’s interesting to me that chat apps are cropping up in my news feeds. What caught my eye is that this system appears to be federated. This is essentially a press release from RocketChat and published on. “Why Choose Rocket.Chat for Your Open Source Chat Tool.” Opensource.Com. What immediately catches my eye is the forceful statement from Tantek Çelik, of Mozilla: “we don’t want to see a big company or 2-3 get a monopolistic control in this space.” Thinking about that from the outset likely affected the ultimate design. This somewhat innocuous-looking site is the start of something big – the transcript first meeting of the Social Web Working Group, held over IRC.
This is the press release from the W3C announcing the start of the Social Web Working Group, which I understand gave us ActivityPub, the protocol that supports contemporary federated social media systems such as Mastodon. “W3C Launches Push for Social Web Application Interoperability.” 2014. So once again, don’t count on these posts as a news feed, but more a window into my thinking as I research my FOSS alternative social media book.
#Rocketchat dark mode code
Improve the side view of the current room's conversation - code fences, images, etc.This week’s FOSS finds: I’m starting to look back at the early days of ActivityPub, and chat apps get some coverage.This allows you to set the ROCKET_* environment variables per directory, and gives you the best of both worlds. You can also use a utility such as direnv, which you can get here: You can also set your Rocket.Chat credentials using environment variables: This way, you can connect to your work server when on a work project, and a private server for a private project. You can connect to different Rocket.Chat servers for various projects, simply put the rocketCode settings in your workspace settings.
Using Environment Variables and/or the workspace
#Rocketchat dark mode password
rocketCode.password: Your Rocket.Chat password.rocketCode.apiPath: The path of the Rocket.Chat API, currently api/v1 - you shouldn't need to change this.rverUrl: The URL of the Rocket.Chat server, e.g.This extension contributes the following settings: Key BindingsĬurrently, only Ctrl-Shift-Enter ( Cmd-Shift-Enter on Mac), which either sends the selection to the current room, or else asks you for a message to send. View the conversation in the current room in an editor pane (similar to Markdown preview).Post code snippet to the current room (if text is selected in the editor, it will be included in a code fence).Post a message to the current room (if nothing is selected in the current editor).switch between joined channels, groups and instant messages (aka rooms).The Extension loads when you call the "Rocket.Code login" command from the palette. It supports channels, groups and instant messages, as well as posting code snippets. This Extension lets you post to Rocket.Chat from within Visual Studio Code.
0 kommentar(er)
