- 3 Posts
- 4 Comments
Joined 4 months ago
Cake day: June 11th, 2026
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
11·4 months agoThe main repository of this project is https://github.com/igniterealtime/Openfire License: Apache-2
Current version is v5.1.0 (2026-06-03)
The feature was implemented since v4.6.0 (2020-10-16)
«[OF-2030] - Add support for XEP-0289: Federated MUC for Constrained Environments»uninteresting notes about OF-2030
(i don’t see that link under OF-2030 - https://issues.igniterealtime.org/browse/OF-2030, and
web.archive org don’t saved it
https://download.igniterealtime.org/openfire/docs/4.6.0/changelog.html«
Loading... https://issues.igniterealtime.org/browse/OF-2030 | 17:30:40 September 20, 2022 Got an HTTP 301 response at crawl time Redirecting to... https://igniterealtime.atlassian.net/browse/OF-2030»
The link https://igniterealtime.atlassian.net/browse/OF-2030
is unavailable at web archive org https://web.archive.org/web/20220922044149/https://igniterealtime.atlassian.net/browse/OF-2030 says:426 Upgrade Required
« Похоже, на этом сайте есть проблема
https://web.archive.org/web/20220922044149if_/https://igniterealtime.atlassian.net/browse/OF-2030 вернул ошибку.
Код ошибки: 426 Upgrade Required
Проверьте, правильно ли вы ввели адрес веб-сайта.
», but available in the internet.
Contain almost no information, except that Guus der Kinderen is the author of implementation
1·4 months agoAn additional problem - the site https://lemmyverse.link/ is available only partially (requires VPN to work).
So my new idea is to deploy
https://github.com/RikudouSage/lemmyverse.link
into my website locally, and give 2 links - the relative (via local redirector) and the direct one (as a fallback).the relative link on forein server will became broken, until they also install such redirector into the same path.
After that the link will always lead to local server and redirect to preferred server of user.
Проверяем:
https://лемми.опенсорс.рус/post/15
I think that this is because the protocol doesn’t contain means of routing (similar to “SEEN-BY” fields). But that is solvable with some coding. And current implementation will work in restricted (controlled) tree-like topologies. I think this is negotiable, and there are no too much nodes, so agreements are possible.