home.social

Search

574 results for “liberachat”

  1. #TheBullhorn issue 28 is now available! There's plenty of updates to collections and community documentation, the move to #LiberaChat IRC network, plus we're looking for more maintainers & contributors! Read on for the details: bit.ly/thebullhorn28

    #Ansible #Community #newsletter

  2. #TheBullhorn issue 28 is now available! There's plenty of updates to collections and community documentation, the move to #LiberaChat IRC network, plus we're looking for more maintainers & contributors! Read on for the details: bit.ly/thebullhorn28

    #Ansible #Community #newsletter

  3. > This report makes it clear that it is now time for all projects to move off #Freenode #IRC. www.devever.net/~hl/freenode_a…

    > You can move to #LiberaChat, to #OFTC, to #Rizon, etc. Or use #Matrix or an #XMPP MUC instead of IRC. Just don't "wait and see" and be surprised when your channel is targeted.
    nu.federati.net/notice/3367257

    /by @lnxw48a1
  4. there's a curious thing on IRC these days where a user will join, advertise itself as a language model, but in such a way (namely: slowly) and with a VERSION reply that suggests they are just a human banging out text the old-fashioned way

    anyway, I'm grateful to @liberachat staff for promptly k-lining such an account just now. while the network isn't opposed to such a bot, the channel where I saw this is explicitly a "no bots of any kind" space and there are some coming policy changes

    <3 good ircops

  5. This is an example of a marketplace listing in Flohmarkt.

    What "I" did here...

    - Went to the "All" tab over at Flensmarkt - Much like PeerTube, there's a Home, Local, and All tab, the latter of which includes items from other instances that you've manually federated with within the radius you've specified from your location.
    - Next, there's a choice to make if you're interested in an item. You can register for a local account (I don't see any reason to do that unless you want to post a listing on that particular server), or you can remotely add yourself (like I did). Since the remote features don't quite seamlessly work with Mitra, I tried this from a masto server - no joy. I tried it from another masto server (a masto fork) - no problem this time, even on an older version of masto. That was humorous to me, as I've a bit of disdain for mastopub servers and found it amusing that even some of the instances running the very latest version of masto won't work, while older one's based on forks do; but I've got a twisted sense of humor.
    - So next, you can engage with the seller directly from your local instance on most Fediverse platforms (support is added for various additional Fediverse platforms all the time). In this case, (visible because I chose the "All" tab), the particular item was from yet another #Fohmarkt server elsewhere - this is a very nice feature, like #DeSoc #eBay!!!
    - From there, once you boost the item in the listing, others can see it in their streams, boost it further, make arrangements directly with the seller, etc. Kinda Kewl.

    This is different from how most other attempts to deliver a marketplace into the #Fediverse. Usually, what I've seen is someone trying to integrate the functionality local to a platform, which networks (via ActivityPub federation) only with other like platforms. That's not a Fediverse solution - that's a platform solution and leaves everyone else on the fediverse not running that particular platform disenfranchised.

    For example, using the Epicyon server platform as an example, it is first to be understood that this particular server platform is designed for very small numbers of user accounts per each instance. You also have to manually contact the admin of remote Epicyon servers yourself (or be contacted by them), then mutually agree to federate each other's marketplaces separately and distinct from any wider federation configurations your server has. Considering the inconveniences with locating other Epicyon instances that may or may not have enabled and made use of their marketplaces and establishing a mutual publishing agreement, coupled with the likelihood that each of your instances between 1 and 10 users, posting an item in the marketplace has a pretty high probability of being more effort than its worth - especially since it dosn't federate with any other Fediverse platforms.

    Others follow a similar design, but also generally operate like normal #ActivityPub federation using a blacklist method, as well as being able to accommodate potentially hundreds, or even thousands of users per each instance (yeah, I know, semi-monolithic); so even if those marketplaces didn't already automatically federate across the Fediverse with all instances of other like server platforms, it's still a huge improvement over the previously discussed smolweb platform's model.

    But they're still not Fediverse wide...

    This is where Flohmarkt really starts to shine - it's fully Federating (Still a WIP wrt some platforms - see the wiki for particulars) across the entire #ActivityPub portion of the Fediverse.

    You can check for the latest particulars on Flohmarkt's current Federation status if you're interested in your particular Fediverse platform and level of interoperation with Flohmarkt instances.

    I do have some criticisms of the particular functionality in federating that the developers have chosen to incorporate, however. Basically, The server admin still needs to manually federate item listings between the local instance and other remote Flohmarkt servers. It doesn't need to be this way however, but one must concede that after going over the documentation and seeing that the concern's of the dev team are over unchecked spam, phishing, poor quality ads, etc., I find it to be a very reasonable concern, although I'm still not comfortable with how the Dev team has hard-coded this conditional into the server's capability, when a slightly different approach might afford self-hosters much greater flexibility and incintive for adoption; namely:

    - Make the current model the default
    - Enable other configurations for federating between other Flohmarkt servers (and eventually, other platform marketplaces) via either simple configuration files, runtime arguments, or via a GUI in an admin control panel, including that of an uninhibited fully blacklist model of sharing listings between Flohmarkt servers.

    I generally tend to think that hard-wired, opinionated configuration choices are a less than ideal (usually bad idea) than acknowledging issues surrounding such decisions and then choosing a default while affording server admins (or users themselves) of being able to manage the options for themselves. This is one of those cases where I feel it could make a huge difference in the viabilty and adoption potential for this, "Strictly Federating Marketplace" Fediverse platform.

    The other (very minor) criticism I have for Flohmarkt is the pin & string radius solution as it is currently implemented:

    - It's determined by the server admin, instance wide
    - It's determined by the server location, or some other arbitrarily decided locale

    The radius is a great idea, but I think the following would go a long way towards improving the utility of this feature set:

    - The server admin decides whether to enable user-level radius configs or server level, as is the case at this time.
    - Local users determine, and have control over whether an established is applied to either their entire user profile's repertoire of items listed, or on a per item basis.
    - If he user chooses a per item radius, each listing could have a different radius established.
    - The local users have location radius specifications that can be based on different criteria, such as pinning a location on a map of their choice, by country (the free IP2Location databases can accommodate this behavior).
    - The user's particular radius settings for each listing must be preserved and observed by all federating remote Flohmarkt server instances (but not by individual remote user shares/boosts, which should remain unrestricted).

    This Radius feature is extremely powerful and I think that every effort of the development team to exploit the potential of this feature set should be a major consideration. Eventually, Flohmarkt servers will federate with other server platform types, exchanging listings between say, Flohmarkt servers and Friendica servers, etc.. but the awesome power unleashed through following and boosting capabilities that are already fully available to remote users to share with others holds the potential at this very time to make Flohmarkt item listings ubiquitous across the entire Fediverse, ... And that is really kewl :)

    Well, I'd rather tease your interest and see you go checkout more for yourself rather than feed you everything you wanna know about a really kewl #social_commerce communications tool - you really should experience how kewl it is for yourself.

    I couldn't locate a #Matrix support room for Flohmarkt like most contemporary software products maintain in the FOSS world, but the more traditional irc chan #flohmarkt at #LiberaChat is readily available, and of course, there's the issue tracker at the Codeberg repo I previously linked to above.

    What are your thoughts and impressions on this novel approach to embedding the marketplace commerce structure into potentially everyone's social streams in the form of both a dedicated platform and as passive feeds via the intervention of other #Fedizens who share and boost individual items and listings in Flohmarkt?

    I hope that helps! Enjoy!

    #tallship #FOSS #Marketplace #eBay #I_can_haz_Cheezburgerz? 🍔
    @grindhold @me @flohmarkt_support #flohmarkt_support

    .

    RE: https://fedi.markets/users/Yonggan/items/f7f7f8d1-6279-4249-890a-bdd97340d218

    @Yonggan

  6. This is an example of a marketplace listing in Flohmarkt.

    What "I" did here...

    - Went to the "All" tab over at Flensmarkt - Much like PeerTube, there's a Home, Local, and All tab, the latter of which includes items from other instances that you've manually federated with within the radius you've specified from your location.
    - Next, there's a choice to make if you're interested in an item. You can register for a local account (I don't see any reason to do that unless you want to post a listing on that particular server), or you can remotely add yourself (like I did). Since the remote features don't quite seamlessly work with Mitra, I tried this from a masto server - no joy. I tried it from another masto server (a masto fork) - no problem this time, even on an older version of masto. That was humorous to me, as I've a bit of disdain for mastopub servers and found it amusing that even some of the instances running the very latest version of masto won't work, while older one's based on forks do; but I've got a twisted sense of humor.
    - So next, you can engage with the seller directly from your local instance on most Fediverse platforms (support is added for various additional Fediverse platforms all the time). In this case, (visible because I chose the "All" tab), the particular item was from yet another #Fohmarkt server elsewhere - this is a very nice feature, like #DeSoc #eBay!!!
    - From there, once you boost the item in the listing, others can see it in their streams, boost it further, make arrangements directly with the seller, etc. Kinda Kewl.

    This is different from how most other attempts to deliver a marketplace into the #Fediverse. Usually, what I've seen is someone trying to integrate the functionality local to a platform, which networks (via ActivityPub federation) only with other like platforms. That's not a Fediverse solution - that's a platform solution and leaves everyone else on the fediverse not running that particular platform disenfranchised.

    For example, using the Epicyon server platform as an example, it is first to be understood that this particular server platform is designed for very small numbers of user accounts per each instance. You also have to manually contact the admin of remote Epicyon servers yourself (or be contacted by them), then mutually agree to federate each other's marketplaces separately and distinct from any wider federation configurations your server has. Considering the inconveniences with locating other Epicyon instances that may or may not have enabled and made use of their marketplaces and establishing a mutual publishing agreement, coupled with the likelihood that each of your instances between 1 and 10 users, posting an item in the marketplace has a pretty high probability of being more effort than its worth - especially since it dosn't federate with any other Fediverse platforms.

    Others follow a similar design, but also generally operate like normal #ActivityPub federation using a blacklist method, as well as being able to accommodate potentially hundreds, or even thousands of users per each instance (yeah, I know, semi-monolithic); so even if those marketplaces didn't already automatically federate across the Fediverse with all instances of other like server platforms, it's still a huge improvement over the previously discussed smolweb platform's model.

    But they're still not Fediverse wide...

    This is where Flohmarkt really starts to shine - it's fully Federating (Still a WIP wrt some platforms - see the wiki for particulars) across the entire #ActivityPub portion of the Fediverse.

    You can check for the latest particulars on Flohmarkt's current Federation status if you're interested in your particular Fediverse platform and level of interoperation with Flohmarkt instances.

    I do have some criticisms of the particular functionality in federating that the developers have chosen to incorporate, however. Basically, The server admin still needs to manually federate item listings between the local instance and other remote Flohmarkt servers. It doesn't need to be this way however, but one must concede that after going over the documentation and seeing that the concern's of the dev team are over unchecked spam, phishing, poor quality ads, etc., I find it to be a very reasonable concern, although I'm still not comfortable with how the Dev team has hard-coded this conditional into the server's capability, when a slightly different approach might afford self-hosters much greater flexibility and incintive for adoption; namely:

    - Make the current model the default
    - Enable other configurations for federating between other Flohmarkt servers (and eventually, other platform marketplaces) via either simple configuration files, runtime arguments, or via a GUI in an admin control panel, including that of an uninhibited fully blacklist model of sharing listings between Flohmarkt servers.

    I generally tend to think that hard-wired, opinionated configuration choices are a less than ideal (usually bad idea) than acknowledging issues surrounding such decisions and then choosing a default while affording server admins (or users themselves) of being able to manage the options for themselves. This is one of those cases where I feel it could make a huge difference in the viabilty and adoption potential for this, "Strictly Federating Marketplace" Fediverse platform.

    The other (very minor) criticism I have for Flohmarkt is the pin & string radius solution as it is currently implemented:

    - It's determined by the server admin, instance wide
    - It's determined by the server location, or some other arbitrarily decided locale

    The radius is a great idea, but I think the following would go a long way towards improving the utility of this feature set:

    - The server admin decides whether to enable user-level radius configs or server level, as is the case at this time.
    - Local users determine, and have control over whether an established is applied to either their entire user profile's repertoire of items listed, or on a per item basis.
    - If he user chooses a per item radius, each listing could have a different radius established.
    - The local users have location radius specifications that can be based on different criteria, such as pinning a location on a map of their choice, by country (the free IP2Location databases can accommodate this behavior).
    - The user's particular radius settings for each listing must be preserved and observed by all federating remote Flohmarkt server instances (but not by individual remote user shares/boosts, which should remain unrestricted).

    This Radius feature is extremely powerful and I think that every effort of the development team to exploit the potential of this feature set should be a major consideration. Eventually, Flohmarkt servers will federate with other server platform types, exchanging listings between say, Flohmarkt servers and Friendica servers, etc.. but the awesome power unleashed through following and boosting capabilities that are already fully available to remote users to share with others holds the potential at this very time to make Flohmarkt item listings ubiquitous across the entire Fediverse, ... And that is really kewl :)

    Well, I'd rather tease your interest and see you go checkout more for yourself rather than feed you everything you wanna know about a really kewl #social_commerce communications tool - you really should experience how kewl it is for yourself.

    I couldn't locate a #Matrix support room for Flohmarkt like most contemporary software products maintain in the FOSS world, but the more traditional irc chan #flohmarkt at #LiberaChat is readily available, and of course, there's the issue tracker at the Codeberg repo I previously linked to above.

    What are your thoughts and impressions on this novel approach to embedding the marketplace commerce structure into potentially everyone's social streams in the form of both a dedicated platform and as passive feeds via the intervention of other #Fedizens who share and boost individual items and listings in Flohmarkt?

    I hope that helps! Enjoy!

    #tallship #FOSS #Marketplace #eBay #I_can_haz_Cheezburgerz? 🍔
    @grindhold @me @flohmarkt_support #flohmarkt_support

    .

    RE: https://fedi.markets/users/Yonggan/items/f7f7f8d1-6279-4249-890a-bdd97340d218

    @Yonggan

  7. This is an example of a marketplace listing in Flohmarkt.

    What "I" did here...

    - Went to the "All" tab over at Flensmarkt - Much like PeerTube, there's a Home, Local, and All tab, the latter of which includes items from other instances that you've manually federated with within the radius you've specified from your location.
    - Next, there's a choice to make if you're interested in an item. You can register for a local account (I don't see any reason to do that unless you want to post a listing on that particular server), or you can remotely add yourself (like I did). Since the remote features don't quite seamlessly work with Mitra, I tried this from a masto server - no joy. I tried it from another masto server (a masto fork) - no problem this time, even on an older version of masto. That was humorous to me, as I've a bit of disdain for mastopub servers and found it amusing that even some of the instances running the very latest version of masto won't work, while older one's based on forks do; but I've got a twisted sense of humor.
    - So next, you can engage with the seller directly from your local instance on most Fediverse platforms (support is added for various additional Fediverse platforms all the time). In this case, (visible because I chose the "All" tab), the particular item was from yet another #Fohmarkt server elsewhere - this is a very nice feature, like #DeSoc #eBay!!!
    - From there, once you boost the item in the listing, others can see it in their streams, boost it further, make arrangements directly with the seller, etc. Kinda Kewl.

    This is different from how most other attempts to deliver a marketplace into the #Fediverse. Usually, what I've seen is someone trying to integrate the functionality local to a platform, which networks (via ActivityPub federation) only with other like platforms. That's not a Fediverse solution - that's a platform solution and leaves everyone else on the fediverse not running that particular platform disenfranchised.

    For example, using the Epicyon server platform as an example, it is first to be understood that this particular server platform is designed for very small numbers of user accounts per each instance. You also have to manually contact the admin of remote Epicyon servers yourself (or be contacted by them), then mutually agree to federate each other's marketplaces separately and distinct from any wider federation configurations your server has. Considering the inconveniences with locating other Epicyon instances that may or may not have enabled and made use of their marketplaces and establishing a mutual publishing agreement, coupled with the likelihood that each of your instances between 1 and 10 users, posting an item in the marketplace has a pretty high probability of being more effort than its worth - especially since it dosn't federate with any other Fediverse platforms.

    Others follow a similar design, but also generally operate like normal #ActivityPub federation using a blacklist method, as well as being able to accommodate potentially hundreds, or even thousands of users per each instance (yeah, I know, semi-monolithic); so even if those marketplaces didn't already automatically federate across the Fediverse with all instances of other like server platforms, it's still a huge improvement over the previously discussed smolweb platform's model.

    But they're still not Fediverse wide...

    This is where Flohmarkt really starts to shine - it's fully Federating (Still a WIP wrt some platforms - see the wiki for particulars) across the entire #ActivityPub portion of the Fediverse.

    You can check for the latest particulars on Flohmarkt's current Federation status if you're interested in your particular Fediverse platform and level of interoperation with Flohmarkt instances.

    I do have some criticisms of the particular functionality in federating that the developers have chosen to incorporate, however. Basically, The server admin still needs to manually federate item listings between the local instance and other remote Flohmarkt servers. It doesn't need to be this way however, but one must concede that after going over the documentation and seeing that the concern's of the dev team are over unchecked spam, phishing, poor quality ads, etc., I find it to be a very reasonable concern, although I'm still not comfortable with how the Dev team has hard-coded this conditional into the server's capability, when a slightly different approach might afford self-hosters much greater flexibility and incintive for adoption; namely:

    - Make the current model the default
    - Enable other configurations for federating between other Flohmarkt servers (and eventually, other platform marketplaces) via either simple configuration files, runtime arguments, or via a GUI in an admin control panel, including that of an uninhibited fully blacklist model of sharing listings between Flohmarkt servers.

    I generally tend to think that hard-wired, opinionated configuration choices are a less than ideal (usually bad idea) than acknowledging issues surrounding such decisions and then choosing a default while affording server admins (or users themselves) of being able to manage the options for themselves. This is one of those cases where I feel it could make a huge difference in the viabilty and adoption potential for this, "Strictly Federating Marketplace" Fediverse platform.

    The other (very minor) criticism I have for Flohmarkt is the pin & string radius solution as it is currently implemented:

    - It's determined by the server admin, instance wide
    - It's determined by the server location, or some other arbitrarily decided locale

    The radius is a great idea, but I think the following would go a long way towards improving the utility of this feature set:

    - The server admin decides whether to enable user-level radius configs or server level, as is the case at this time.
    - Local users determine, and have control over whether an established is applied to either their entire user profile's repertoire of items listed, or on a per item basis.
    - If he user chooses a per item radius, each listing could have a different radius established.
    - The local users have location radius specifications that can be based on different criteria, such as pinning a location on a map of their choice, by country (the free IP2Location databases can accommodate this behavior).
    - The user's particular radius settings for each listing must be preserved and observed by all federating remote Flohmarkt server instances (but not by individual remote user shares/boosts, which should remain unrestricted).

    This Radius feature is extremely powerful and I think that every effort of the development team to exploit the potential of this feature set should be a major consideration. Eventually, Flohmarkt servers will federate with other server platform types, exchanging listings between say, Flohmarkt servers and Friendica servers, etc.. but the awesome power unleashed through following and boosting capabilities that are already fully available to remote users to share with others holds the potential at this very time to make Flohmarkt item listings ubiquitous across the entire Fediverse, ... And that is really kewl :)

    Well, I'd rather tease your interest and see you go checkout more for yourself rather than feed you everything you wanna know about a really kewl #social_commerce communications tool - you really should experience how kewl it is for yourself.

    I couldn't locate a #Matrix support room for Flohmarkt like most contemporary software products maintain in the FOSS world, but the more traditional irc chan #flohmarkt at #LiberaChat is readily available, and of course, there's the issue tracker at the Codeberg repo I previously linked to above.

    What are your thoughts and impressions on this novel approach to embedding the marketplace commerce structure into potentially everyone's social streams in the form of both a dedicated platform and as passive feeds via the intervention of other #Fedizens who share and boost individual items and listings in Flohmarkt?

    I hope that helps! Enjoy!

    #tallship #FOSS #Marketplace #eBay #I_can_haz_Cheezburgerz? 🍔
    @grindhold @me @flohmarkt_support #flohmarkt_support

    .

    RE: https://fedi.markets/users/Yonggan/items/f7f7f8d1-6279-4249-890a-bdd97340d218

    @Yonggan

  8. My current WeeChat setup

    Since it's come up in conversation a couple of times in the past week (waves at @snowdusk__ and @yarmo), here's a #screenshot of my current #WeeChat setup (though with different buffers selected than my usual arrangement).

    "What am I looking at on the screenshot?"

    A buffer list ¹ on the left. Buffers represent the channels, private message streams and status timelines from the various chat media you are connected to.
    Side the buffer list are a variety of horizontally and vertically panes, which @weechat called 'windows', each window showing the contents of one
    ² of the buffers.

    "What buffers are visible in these window panes?"

    From top left to bottom right these are:

    "What's making it work?"

    All running in a #tmux terminal multiplexer session, running under #WSL2 on #Windows, in the #WindowsTerminalPreview #terminal client.

    (Repost to fix an at-mention...)

    Footnotes

    ¹ though I still use buffers.pl script rather than the built-in buflist plugin because I'm too lazy to migrate my settings to make it look and act in the way I've gotten used to.
    ² or more, as buffers can be merged, displaying the contents of each of the merged buffers chronologically in the same window pane.

    Hashtags

    #Battlestations #chat #chatClients #IRCClients #IRCClient #InternetRelayChat #MultiProtocol #FOSS #FLOSS

  9. My current WeeChat setup

    Since it's come up in conversation a couple of times in the past week (waves at @snowdusk__ and @yarmo), here's a #screenshot of my current #WeeChat setup (though with different buffers selected than my usual arrangement).

    "What am I looking at on the screenshot?"

    A buffer list ¹ on the left. Buffers represent the channels, private message streams and status timelines from the various chat media you are connected to.
    Side the buffer list are a variety of horizontally and vertically panes, which @weechat called 'windows', each window showing the contents of one
    ² of the buffers.

    "What buffers are visible in these window panes?"

    From top left to bottom right these are:

    "What's making it work?"

    All running in a #tmux terminal multiplexer session, running under #WSL2 on #Windows, in the #WindowsTerminalPreview #terminal client.

    (Repost to fix an at-mention...)

    Footnotes

    ¹ though I still use buffers.pl script rather than the built-in buflist plugin because I'm too lazy to migrate my settings to make it look and act in the way I've gotten used to.
    ² or more, as buffers can be merged, displaying the contents of each of the merged buffers chronologically in the same window pane.

    Hashtags

    #Battlestations #chat #chatClients #IRCClients #IRCClient #InternetRelayChat #MultiProtocol #FOSS #FLOSS

  10. @osuosl will live on!

    osuosl.org/blog/osl-future-upd

    Huge congrats to @ramereth and the team for securing their necessary funding.

    If you or your organization were still considering supporting , don't let this good news stop you. Help it thrive, not just survive!

  11. @osuosl will live on!

    osuosl.org/blog/osl-future-upd

    Huge congrats to @ramereth and the team for securing their necessary funding.

    If you or your organization were still considering supporting #OSUOSL, don't let this good news stop you. Help it thrive, not just survive!

  12. @osuosl will live on!

    osuosl.org/blog/osl-future-upd

    Huge congrats to @ramereth and the team for securing their necessary funding.

    If you or your organization were still considering supporting #OSUOSL, don't let this good news stop you. Help it thrive, not just survive!

  13. @osuosl will live on!

    osuosl.org/blog/osl-future-upd

    Huge congrats to @ramereth and the team for securing their necessary funding.

    If you or your organization were still considering supporting #OSUOSL, don't let this good news stop you. Help it thrive, not just survive!

  14. @osuosl will live on!

    osuosl.org/blog/osl-future-upd

    Huge congrats to @ramereth and the team for securing their necessary funding.

    If you or your organization were still considering supporting #OSUOSL, don't let this good news stop you. Help it thrive, not just survive!

  15. If you are reading this post, you have benefited from OSUOSL. Projects supported by them power today's Internet architecture.

    We know that OSUOSL is worth saving. But we need organizations that rely on the Internet to get on the same page.

    If you're in the tech industry, ask your employer to arrange an ongoing sponsorship of the program now, before it is too late. The clock is ticking.

    libera.chat/news/osuosl-is-wor

  16. If you are reading this post, you have benefited from OSUOSL. Projects supported by them power today's Internet architecture.

    We know that OSUOSL is worth saving. But we need organizations that rely on the Internet to get on the same page.

    If you're in the tech industry, ask your employer to arrange an ongoing sponsorship of the program now, before it is too late. The clock is ticking.

    libera.chat/news/osuosl-is-wor

    #OSUOSL

  17. If you are reading this post, you have benefited from OSUOSL. Projects supported by them power today's Internet architecture.

    We know that OSUOSL is worth saving. But we need organizations that rely on the Internet to get on the same page.

    If you're in the tech industry, ask your employer to arrange an ongoing sponsorship of the program now, before it is too late. The clock is ticking.

    libera.chat/news/osuosl-is-wor

    #OSUOSL

  18. If you are reading this post, you have benefited from OSUOSL. Projects supported by them power today's Internet architecture.

    We know that OSUOSL is worth saving. But we need organizations that rely on the Internet to get on the same page.

    If you're in the tech industry, ask your employer to arrange an ongoing sponsorship of the program now, before it is too late. The clock is ticking.

    libera.chat/news/osuosl-is-wor

    #OSUOSL

  19. If you are reading this post, you have benefited from OSUOSL. Projects supported by them power today's Internet architecture.

    We know that OSUOSL is worth saving. But we need organizations that rely on the Internet to get on the same page.

    If you're in the tech industry, ask your employer to arrange an ongoing sponsorship of the program now, before it is too late. The clock is ticking.

    libera.chat/news/osuosl-is-wor

    #OSUOSL

  20. Libera.Chat would not be what we are today, if not for OSL's sponsorship of the network before us.

    OSL has been an integral part of open source and open culture project support for a very long time. They support projects we use, learn from, and contribute to. Many of these projects call Libera.Chat home.

    Nonprofits, businesses, governments, and you all depend on projects OSL sponsors. If not directly, then somewhere upstream.

    OSL is worth saving.

    osuosl.org/blog/osl-future/

  21. Shame, it looks like Libera just temporarily banned the IRC Today bouncer.

    > You are banned from this server- The service you are using is unstable and flooding channels with reconnects. Please contact the administrator and have them email [email protected] when fixed. (2026/3/30 20.41)

    So no IRC today for me I guess. #libera #irc #irctoday

  22. Shame, it looks like Libera just temporarily banned the IRC Today bouncer.

    > You are banned from this server- The service you are using is unstable and flooding channels with reconnects. Please contact the administrator and have them email [email protected] when fixed. (2026/3/30 20.41)

    So no IRC today for me I guess. #libera #irc #irctoday

  23. Shame, it looks like Libera just temporarily banned the IRC Today bouncer.

    > You are banned from this server- The service you are using is unstable and flooding channels with reconnects. Please contact the administrator and have them email [email protected] when fixed. (2026/3/30 20.41)

    So no IRC today for me I guess. #libera #irc #irctoday

  24. Shame, it looks like Libera just temporarily banned the IRC Today bouncer.

    > You are banned from this server- The service you are using is unstable and flooding channels with reconnects. Please contact the administrator and have them email [email protected] when fixed. (2026/3/30 20.41)

    So no IRC today for me I guess. #libera #irc #irctoday