realaravinth/ff-spec
1
0
Fork 0
mirror of https://github.com/forgefedv2/spec.git synced 2024-06-02 10:21:24 +05:30
Code Issues Projects Releases Wiki Activity

use new name

Browse source
This commit is contained in:
mscherer 2022-01-14 11:08:55 +01:00 committed by GitHub
parent 88d5f64e56
commit f11de0f3c2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
rfc/2-rooms-and-events.md/2-rooms-and-events.md
View file

@ -2,7 +2,7 @@
## Summary ## Summary
This RFC proposes a model of sharing data in the Forge Fed protocol This RFC proposes a model of sharing data in the Forgeflux protocol
through a concept of rooms and events. A room can be subscribed to, through a concept of rooms and events. A room can be subscribed to,
unsubscribed from and can contain nested rooms, which themselves are unsubscribed from and can contain nested rooms, which themselves are
fully capable as parent rooms. Events are used to describe various types fully capable as parent rooms. Events are used to describe various types
@ -48,7 +48,7 @@ instance `f.event.patch`.
## Rooms ## Rooms
Rooms are the basic channels of communication in the Forge Fed protocol. Rooms are the basic channels of communication in the Forgeflux protocol.
All forge-activity should be modeled based on rooms. Rooms are All forge-activity should be modeled based on rooms. Rooms are
identified based on the `main forge` but all `main interfaces` should be identified based on the `main forge` but all `main interfaces` should be
capable of accommodating subscribing non-native interfaces. capable of accommodating subscribing non-native interfaces.