Ekaterina Broslavskaya ade93e2547 Blogpost: de-mls with Waku (#159)
* feat: add new blog post on de-mls with Waku and update authors list

* adding introduction

* Enhance blog post on decentralized MLS with Waku: added detailed explanations of the MLS protocol, its decentralized adaptation, and Waku's pub-sub architecture. Included insights on key management, user roles, and the actor-based system design for message processing.

* Refine blog post on decentralized MLS with Waku: improved clarity and structure by enhancing explanations of the MLS protocol, Waku's pub-sub architecture, and key management processes. Added sections on message distribution, user roles, and future work, while correcting terminology and formatting for better readability.

* update the structure

* fix references

* editorial updates

* Update publication date and enhance architectural overview in de-MLS with Waku documentation. Added new sections on actor communication and cryptographic key management, along with a new image for better illustration of the architecture.

* Refine de-MLS documentation: clarified the roles of pub-sub topics, streamlined actor responsibilities, and removed outdated code snippets. Focused on Waku integration and user/group actor functionalities for improved understanding.

* Refine de-MLS documentation: improve clarity on message distribution, Waku protocol, and group communication topics

* Update rlog/2024-12-23-de-mls.mdx

Co-authored-by: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com>

* groundbreaking commit

* fix figure

* Update de-mls.mdx

* update image file extension

* small fix

* image update

* fix Docusaurus error

* replace admin as steward

* Update rlog/2024-12-23-de-mls.mdx

Co-authored-by: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com>

* replace all admins

* review fix

* title update

* RFC citation

* grammer fixes and update proposal part

* cite de-MLS RFC

* explicitly mentioning of async feature

* waku integration RFC as a future todo

* adding intro

* transition in intro

* adding use cases

---------

Co-authored-by: seugu <99656002+seugu@users.noreply.github.com>
Co-authored-by: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com>
Co-authored-by: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com>
2025-09-01 13:44:47 +03:00
2023-03-17 12:22:59 +01:00
2023-06-07 22:12:28 +01:00
2025-09-01 13:44:47 +03:00
2023-11-15 21:12:16 +03:30
2023-11-15 21:12:16 +03:30
2023-06-07 22:12:28 +01:00
2023-06-07 22:12:28 +01:00
2023-06-07 22:12:28 +01:00
2025-04-25 15:23:43 +09:00
2025-08-03 18:28:20 +05:30
2025-08-03 18:28:20 +05:30
2025-08-03 18:28:20 +05:30
2025-04-25 15:23:43 +09:00
2025-07-12 00:54:23 +09:00
2025-04-25 15:23:43 +09:00

This repository contains the source for vac.dev.

Vac Research Blog

Adding posts

To publish in the blog, create a .md or mdx file within the rlog directory. Please follow sembr in the .md or .mdx file. You can use Frontmatter to add metadata to your markdown file.

CI/CD

The hosting is done using Caddy server with Git plugin for handling GitHub webhooks.

Information about deployed build can be also found in /build.json available on the website.

Change Process

  1. Create a new working branch from develop: git checkout develop; git checkout -b my-changes.
  2. Make your changes, push them to the origin, and open a Pull Request against the develop branch.
  3. After approval, merge the pull request, and verify the changes on the staging server (e.g., https://dev.vac.dev).
  4. When ready to promote changes to the live website, rebase the master branch on the staging changes: git checkout master; git pull origin master; git rebase origin/develop; git push.

How to Run Locally

  1. Clone this repository
$ git clone git@github.com:vacp2p/vac.dev.git
  1. Install the dependencies:
$ yarn install
  1. Start the website:
$ yarn start
  1. Visit http://localhost:3000/ in your browser

Further Info and Configuration

Note

: The following contains options that go beyond what is needed to add new blog posts. To simply add a blog post, follow the steps listed above.

Blog Setup

The blog utilizes the Docusaurus blog plugin configured in docusaurus.config.js.

[
  '@docusaurus/plugin-content-blog',
  /** @type {import('@docusaurus/plugin-content-blog').PluginOptions} */
  ({
    id: 'blog',
    routeBasePath: '/',
    path: 'posts',
    blogTitle: 'Research Log',
    blogSidebarCount: 0,
    authorsMapPath: 'authors.yml',
    remarkPlugins: [math],
    rehypePlugins: [katex],
  }),
]

A list of authors can be defined in /posts/authors.yml.

For additional customization options, please refer to the Docusaurus Blog Plugin documentation.

Customization

You can find instructions for adding additional documentation sections, implementing localization, and managing versioning on the Docusaurus website.

Please note that theme customization is somewhat restricted; for more detailed instructions on customizing your theme, visit the Logos Docusaurus Theme repository.

Configuration

Edit the docusaurus.config.js file in the repository's root directory, and update the value of the businessUnit field in presets section; below is a list of valid values:

  • Logos
  • Codex
  • Waku
  • Nimbus
  • Nomos
  • VacResearch
  • Acid.info

Example:

presets: [
  [
    '@acid-info/logos-docusaurus-preset',
    {
      businessUnit: 'Codex',
    },
  ],
],

This is typically sufficient for most cases, as the Logos plugins will automatically populate other configurations related to the specified business unit. If you encounter any errors in the information provided by Logos Plugins, please visit the Logos Docusaurus Plugins repository and open an issue.

Description
No description provided
Readme 594 MiB
Languages
MDX 99.3%
JavaScript 0.5%
Nix 0.1%