#libreserver — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #libreserver, aggregated by home.social.
-
In their infinite wisdom the Google Gods have changed the download url for golang. This has now been changed in #LibreServer.
-
In their infinite wisdom the Google Gods have changed the download url for golang. This has now been changed in #LibreServer.
-
In their infinite wisdom the Google Gods have changed the download url for golang. This has now been changed in #LibreServer.
-
RETURN OF THE IRC
IRC returns to #LibreServer with Ergo https://github.com/ergochat/ergo. This enables you to do no-nonsense text chat by ssh'ing to the server and then selecting "run an app" and "ergo". Hence you can retain a small scale chat between members on the server, with a reasonable degree of security.
Not so long ago I thought that Matrix had effectively replaced IRC, but based upon recent experience Matrix isn't yet ready for some of the scenarios which IRC covers, and the politics of Matrix also looks shaky with it's support of governments and the kinds of things that governments do (looking at you, USA). IRC doesn't come with that sort of baggage. -
RETURN OF THE IRC
IRC returns to #LibreServer with Ergo https://github.com/ergochat/ergo. This enables you to do no-nonsense text chat by ssh'ing to the server and then selecting "run an app" and "ergo". Hence you can retain a small scale chat between members on the server, with a reasonable degree of security.
Not so long ago I thought that Matrix had effectively replaced IRC, but based upon recent experience Matrix isn't yet ready for some of the scenarios which IRC covers, and the politics of Matrix also looks shaky with it's support of governments and the kinds of things that governments do (looking at you, USA). IRC doesn't come with that sort of baggage. -
RETURN OF THE IRC
IRC returns to #LibreServer with Ergo https://github.com/ergochat/ergo. This enables you to do no-nonsense text chat by ssh'ing to the server and then selecting "run an app" and "ergo". Hence you can retain a small scale chat between members on the server, with a reasonable degree of security.
Not so long ago I thought that Matrix had effectively replaced IRC, but based upon recent experience Matrix isn't yet ready for some of the scenarios which IRC covers, and the politics of Matrix also looks shaky with it's support of governments and the kinds of things that governments do (looking at you, USA). IRC doesn't come with that sort of baggage. -
@mikemccaffrey
> You really need to differentiate between traditional data centers and AI data centersThat's a distinction without a difference. AWS is just as socially harmful as "AI" or crypto-mining. More relevant dichotomies might be;
* hyperscale vs. human-scale (a PC is a closet running @yunohost or #LibreServer is kind of a datacentre). * corporate-owned vs. co-op owned/ community-owned
* overseas-owned vs. locally-owned
* 100% renewably-powered vs fossil-powered
* etc -
@mikemccaffrey
> You really need to differentiate between traditional data centers and AI data centersThat's a distinction without a difference. AWS is just as socially harmful as "AI" or crypto-mining. More relevant dichotomies might be;
* hyperscale vs. human-scale (a PC is a closet running @yunohost or #LibreServer is kind of a datacentre). * corporate-owned vs. co-op owned/ community-owned
* overseas-owned vs. locally-owned
* 100% renewably-powered vs fossil-powered
* etc -
@mikemccaffrey
> You really need to differentiate between traditional data centers and AI data centersThat's a distinction without a difference. AWS is just as socially harmful as "AI" or crypto-mining. More relevant dichotomies might be;
* hyperscale vs. human-scale (a PC is a closet running @yunohost or #LibreServer is kind of a datacentre). * corporate-owned vs. co-op owned/ community-owned
* overseas-owned vs. locally-owned
* 100% renewably-powered vs fossil-powered
* etc -
@mikemccaffrey
> You really need to differentiate between traditional data centers and AI data centersThat's a distinction without a difference. AWS is just as socially harmful as "AI" or crypto-mining. More relevant dichotomies might be;
* hyperscale vs. human-scale (a PC is a closet running @yunohost or #LibreServer is kind of a datacentre). * corporate-owned vs. co-op owned/ community-owned
* overseas-owned vs. locally-owned
* 100% renewably-powered vs fossil-powered
* etc -
Added more integration between blogging on Epicyon and #Gemini protocol on #LibreServer. So if you make a blog post on Epicyon it will also be converted to Gemini format and appear on your Gemini site.
-
Added more integration between blogging on Epicyon and #Gemini protocol on #LibreServer. So if you make a blog post on Epicyon it will also be converted to Gemini format and appear on your Gemini site.
-
Added more integration between blogging on Epicyon and #Gemini protocol on #LibreServer. So if you make a blog post on Epicyon it will also be converted to Gemini format and appear on your Gemini site.
-
Replaced eth0 in the next version of #LibreServer with the fancy new network device naming convention.
-
Replaced eth0 in the next version of #LibreServer with the fancy new network device naming convention.
-
Replaced eth0 in the next version of #LibreServer with the fancy new network device naming convention.
-
Found a critical bug when testing the next version of #LibreServer. The eth0 hack which worked in Debian 12 no longer appears to work in Debian 13, and this can mean that the ethernet connection dies, with resulting zero access to anything including the local network.
-
Found a critical bug when testing the next version of #LibreServer. The eth0 hack which worked in Debian 12 no longer appears to work in Debian 13, and this can mean that the ethernet connection dies, with resulting zero access to anything including the local network.
-
Found a critical bug when testing the next version of #LibreServer. The eth0 hack which worked in Debian 12 no longer appears to work in Debian 13, and this can mean that the ethernet connection dies, with resulting zero access to anything including the local network.
-
Breaking on through to the other side of the Debian upgrade...
#LibreServer -
Breaking on through to the other side of the Debian upgrade...
#LibreServer -
Breaking on through to the other side of the Debian upgrade...
#LibreServer -
#LibreServer test install on Armbian went all the way through without crashing, and the firewall looks like it's working.
-
#LibreServer test install on Armbian went all the way through without crashing, and the firewall looks like it's working.
-
#LibreServer test install on Armbian went all the way through without crashing, and the firewall looks like it's working.
-
Fixing the #Mumble configuration in the next version of #LibreServer. I notice that the location of its ini file had moved.
Note to maintainers: please keep the locations of essential files in the same place. -
Fixing the #Mumble configuration in the next version of #LibreServer. I notice that the location of its ini file had moved.
Note to maintainers: please keep the locations of essential files in the same place. -
Fixing the #Mumble configuration in the next version of #LibreServer. I notice that the location of its ini file had moved.
Note to maintainers: please keep the locations of essential files in the same place. -
Fixed some snafus with the #Forgejo app configuration on the next version of #LibreServer
-
Fixed some snafus with the #Forgejo app configuration on the next version of #LibreServer
-
Fixed some snafus with the #Forgejo app configuration on the next version of #LibreServer
-
Added channel binding support for #xmpp in the next version of #LibreServer.
-
Added channel binding support for #xmpp in the next version of #LibreServer.
-
Added channel binding support for #xmpp in the next version of #LibreServer.
-
Tested onion email on the next version of #LibreServer, and that appears to be working.
I also tested the meli email client, but it seems buggy and not ready for production. Being written in Rust does not preclude buggyness. -
Tested onion email on the next version of #LibreServer, and that appears to be working.
I also tested the meli email client, but it seems buggy and not ready for production. Being written in Rust does not preclude buggyness. -
Tested onion email on the next version of #LibreServer, and that appears to be working.
I also tested the meli email client, but it seems buggy and not ready for production. Being written in Rust does not preclude buggyness. -
Added LLM user agent blocking in the next version of #LibreServer. Such methods are never going to be perfect, but they may reduce the amount of wasted bandwidth and CPU.
-
Added LLM user agent blocking in the next version of #LibreServer. Such methods are never going to be perfect, but they may reduce the amount of wasted bandwidth and CPU.
-
Added LLM user agent blocking in the next version of #LibreServer. Such methods are never going to be perfect, but they may reduce the amount of wasted bandwidth and CPU.
-
Preparing the firewall for #IPv6. In previous versions of #LibreServer IPv6 was turned off, but I am going to try to support it in the next version.
-
Preparing the firewall for #IPv6. In previous versions of #LibreServer IPv6 was turned off, but I am going to try to support it in the next version.
-
Preparing the firewall for #IPv6. In previous versions of #LibreServer IPv6 was turned off, but I am going to try to support it in the next version.
-
Tested #Mumble server on the next version of #LibreServer.
-
Tested #Mumble server on the next version of #LibreServer.
-
Tested #Mumble server on the next version of #LibreServer.
-
Tested #Flightgear multiplayer server on the next version of #LibreServer.
-
Tested #Flightgear multiplayer server on the next version of #LibreServer.
-
Tested #Flightgear multiplayer server on the next version of #LibreServer.
-
#Crossfire server tested on the next version of #LibreServer.
https://crossfire.real-time.com