diff --git a/v3/assets/groups/profile.png b/v3/assets/groups/profile.png
new file mode 100644
index 0000000..6f88e91
Binary files /dev/null and b/v3/assets/groups/profile.png differ
diff --git a/v3/feed.rss b/v3/feed.rss
index ddd174e..99f8d00 100644
--- a/v3/feed.rss
+++ b/v3/feed.rss
@@ -2,10 +2,30 @@
We haven't implemented federation of Groups yet, but group tags and discussion +on how unbounded groups can be federated via ActivityPub has already started.
+ +Concerning federation of traditional groups, we will port our logic from v2 and +translate following the same rules as AndStatus because they work, as yvolk beautifully stated :)
+ +Finally, also note that the group actors now have "self-tags", as the other actors, which was a milestone.
+ + + +]]>https://gnusocial.rocks/v3/updates-local-groups.html +The Oomox plugin main class catches the "PopulateProfileSettingsTabs" event upon visiting user panel.
- -public function onPopulateProfileSettingsTabs(Request $request, array &$tabs): bool
-{
- $tabs[] = [
- 'title' => 'Light theme colours',
- 'desc' => 'Change the theme colours.',
- 'controller' => C\Oomox::oomoxSettingsLight($request),
- ];
-
- $tabs[] = [
- 'title' => 'Dark theme colours',
- 'desc' => 'Change the theme colours.',
- 'controller' => C\Oomox::oomoxSettingsDark($request),
- ];
-
- return Event::next;
-}
-
-
-As made evident by the code, two new tabs are added to profile settings, light and dark theme colours. -Since the page styling follows the system theme, actors may want to style each theme differently, therefore they are treated separately.
- -The actor's defined colours are then saved in the respective entity and cached. -Finally, the colour preferences are used to render the corresponding CSS file which defines the various colour variables used:
- -public function oomoxCSS(): Response
-{
- $user = Common::ensureLoggedIn();
-
- $oomox_table = PluginOomox::getEntity($user);
- if (is_null($oomox_table)) {
- throw new ClientException(_m('No custom colours defined', 404));
- }
-
- $content = Formatting::twigRenderFile('/oomox/root_override.css.twig', ['oomox' => $oomox_table]);
- return new Response($content, status: 200, headers: ['content-type' => 'text/css']);
-}
-
-
-Please note, upon rendering for the first time, page render may be blocked until the resulting file is served. Nonetheless, subsequent page renders -won't experience the issue again. That is, if the file is cached by the browser.
- -Tabs added using the "PopulateProfileSettingsTabs" event: -
- -Changing the dark theme colours! -
- -The result of given changes, please note it's no longer a 'dark' theme. -Given a valid colour, it's the actor's responsibility whether or not the colours make sense. So, go wild! -
- - - - - - - - - - - - - - - - - -]]>We haven't implemented federation of Groups yet, but group tags and discussion +on how unbounded groups can be federated via ActivityPub has already started.
+ +Concerning federation of traditional groups, we will port our logic from v2 and +translate following the same rules as AndStatus because they work, as yvolk beautifully stated :)
+ +Finally, also note that the group actors now have "self-tags", as the other actors, which was a milestone.
+ + + + +