home.social

#irssi — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #irssi, aggregated by home.social.

fetched live
  1. Time to brush up on my knowledge of #Irssi (don't ask).

  2. Time to brush up on my knowledge of #Irssi (don't ask).

  3. Time to brush up on my knowledge of #Irssi (don't ask).

  4. Time to brush up on my knowledge of #Irssi (don't ask).

  5. The BitchX is Back!

    No, not the Elton John song from the seventies - The #IRC client (considered the most popular before #Irssi and #weechat) back in the late 90's on #DALnet and into the 2000's.

    But there's a twist, this is an entirely revamped beast, kinda like finding an old Model A Ford that's so rusted out even the axles are seized up and the doors are paper thin with shattered windows, and plenty of bullet holes in the body...

    ... and then restoring it back to factory showroom floor condition. Except for the engine - a rusted hunk of metal that was replaced with a brand new Chevy 454 Big Block V8; something really contemporary that you might not expect. I'll leave you to discover what that is by visiting the link where the maintainer explains everything :)

    And remember, you too can once again be Too Lame to run BitchX!

    #tallship #BitchX #ncurses #TUI #FOSS #ANSI_Art

  6. The BitchX is Back!

    No, not the Elton John song from the seventies - The #IRC client (considered the most popular before #Irssi and #weechat) back in the late 90's on #DALnet and into the 2000's.

    But there's a twist, this is an entirely revamped beast, kinda like finding an old Model A Ford that's so rusted out even the axles are seized up and the doors are paper thin with shattered windows, and plenty of bullet holes in the body...

    ... and then restoring it back to factory showroom floor condition. Except for the engine - a rusted hunk of metal that was replaced with a brand new Chevy 454 Big Block V8; something really contemporary that you might not expect. I'll leave you to discover what that is by visiting the link where the maintainer explains everything :)

    And remember, you too can once again be Too Lame to run BitchX!

    #tallship #BitchX #ncurses #TUI #FOSS #ANSI_Art

  7. The BitchX is Back!

    No, not the Elton John song from the seventies - The #IRC client (considered the most popular before #Irssi and #weechat) back in the late 90's on #DALnet and into the 2000's.

    But there's a twist, this is an entirely revamped beast, kinda like finding an old Model A Ford that's so rusted out even the axles are seized up and the doors are paper thin with shattered windows, and plenty of bullet holes in the body...

    ... and then restoring it back to factory showroom floor condition. Except for the engine - a rusted hunk of metal that was replaced with a brand new Chevy 454 Big Block V8; something really contemporary that you might not expect. I'll leave you to discover what that is by visiting the link where the maintainer explains everything :)

    And remember, you too can once again be Too Lame to run BitchX!

    #tallship #BitchX #ncurses #TUI #FOSS #ANSI_Art

  8. I've been whole afternoon installing and configuring the irc client #irssi.

    I saw that #HexChat is discontinued, if I miss remember the dev abandoned the #project due lack of help I think...

    Never touched the #IRC protocol. Into my house the Internet came around 2004 and in that time I was 11 yrs old and #Messenger in that time hit so hard.

    Now, I have got the itch to try it and leave it in background with opened channels like #spectrwm, #debian, #irssi, etc.

    To answer possible solutions to other users asking his troubles with linux, irssi, debian, or troubles of mine too.

  9. posting from #irssi via znc, bitlbee, and the bitlbee-mastodon plugin by @kensanata #irc

  10. posting from #irssi via znc, bitlbee, and the bitlbee-mastodon plugin by @kensanata #irc

  11. posting from #irssi via znc, bitlbee, and the bitlbee-mastodon plugin by @kensanata #irc

  12. posting from #irssi via znc, bitlbee, and the bitlbee-mastodon plugin by @kensanata #irc

  13. posting from #irssi via znc, bitlbee, and the bitlbee-mastodon plugin by @kensanata #irc

  14. I'm surprised of my own muscle-memory using again after at least 8 years of neglecting IRC. Happy to see there are still some folks around on

  15. I'm surprised of my own muscle-memory using #irssi again after at least 8 years of neglecting IRC. Happy to see there are still some folks around on #liberaChat

  16. Me gustaría hacer una consulta a los #linuxeros; no se si han escuchado #irssi chat en #linux o #termux, si la han usado ¿cual es su experiencia, y si recomiendan usarlo o recomiendan otro chat? Quiero instalar un servicio de chat en termux y no estoy segura cual usar.

  17. Me gustaría hacer una consulta a los #linuxeros; no se si han escuchado #irssi chat en #linux o #termux, si la han usado ¿cual es su experiencia, y si recomiendan usarlo o recomiendan otro chat? Quiero instalar un servicio de chat en termux y no estoy segura cual usar.

  18. Me gustaría hacer una consulta a los #linuxeros; no se si han escuchado #irssi chat en #linux o #termux, si la han usado ¿cual es su experiencia, y si recomiendan usarlo o recomiendan otro chat? Quiero instalar un servicio de chat en termux y no estoy segura cual usar.

  19. Me gustaría hacer una consulta a los #linuxeros; no se si han escuchado #irssi chat en #linux o #termux, si la han usado ¿cual es su experiencia, y si recomiendan usarlo o recomiendan otro chat? Quiero instalar un servicio de chat en termux y no estoy segura cual usar.

  20. I'm looking for Irssi users who want to test drive a script which adds IRCv3 typing notifications support.

    codeberg.org/Juerd/irssi-typin

    :boost_ok:

    #irssi #irc #ircv3

  21. I'm looking for Irssi users who want to test drive a script which adds IRCv3 typing notifications support.

    codeberg.org/Juerd/irssi-typin

    :boost_ok:

    #irssi #irc #ircv3

  22. I'm looking for Irssi users who want to test drive a script which adds IRCv3 typing notifications support.

    codeberg.org/Juerd/irssi-typin

    :boost_ok:

    #irssi #irc #ircv3

  23. I'm looking for Irssi users who want to test drive a script which adds IRCv3 typing notifications support.

    codeberg.org/Juerd/irssi-typin

    :boost_ok:

    #irssi #irc #ircv3

  24. #h4ckseed Nueva entrada

    Chat en Termux

    Por necesidades actuales en mi vida, muchas veces paro mas en el smartphone que en la desktop o laptop. Así que muchas veces se extraña el interprete de terminal de toda la vida, y por supuesto la socialización con los colegas del mundillo.

    #termux #irc #irssi #android

    h4ckseed.wordpress.com/2026/02

  25. #h4ckseed Nueva entrada

    Chat en Termux

    Por necesidades actuales en mi vida, muchas veces paro mas en el smartphone que en la desktop o laptop. Así que muchas veces se extraña el interprete de terminal de toda la vida, y por supuesto la socialización con los colegas del mundillo.

    #termux #irc #irssi #android

    h4ckseed.wordpress.com/2026/02

  26. #h4ckseed Nueva entrada

    Chat en Termux

    Por necesidades actuales en mi vida, muchas veces paro mas en el smartphone que en la desktop o laptop. Así que muchas veces se extraña el interprete de terminal de toda la vida, y por supuesto la socialización con los colegas del mundillo.

    #termux #irc #irssi #android

    h4ckseed.wordpress.com/2026/02

  27. #h4ckseed Nueva entrada

    Chat en Termux

    Por necesidades actuales en mi vida, muchas veces paro mas en el smartphone que en la desktop o laptop. Así que muchas veces se extraña el interprete de terminal de toda la vida, y por supuesto la socialización con los colegas del mundillo.

    #termux #irc #irssi #android

    h4ckseed.wordpress.com/2026/02

  28. #h4ckseed Nueva entrada

    Chat en Termux

    Por necesidades actuales en mi vida, muchas veces paro mas en el smartphone que en la desktop o laptop. Así que muchas veces se extraña el interprete de terminal de toda la vida, y por supuesto la socialización con los colegas del mundillo.

    #termux #irc #irssi #android

    h4ckseed.wordpress.com/2026/02

  29. Hi ya'll! Long time no see, Mastodon-peeps 🤓☕️

    Anyways! Discord is about to start requiring strong identity verification from users if they’re on a server with age restrictions. Verification would happen, for example, via an ID card. Quite a move from a company that leaked the data of 70,000 users a couple of months ago.

    This has sparked a lot of discussion today across several different groups. Tighter legislation in various countries has surely influenced Discord’s stance, but one could argue they might have chosen a different path.

    This piece of news served as inspiration to reflect on the resilience of commercial solutions. The idea of moving fully toward open-source solutions often crosses my mind, and in many cases I’ve taken steps closer to that world - though not always.

    Maybe the biggest pain point for me when adopting new (or old) technology is how many others come along. There’s little point in switching, say, to a new and more secure messaging app if hardly anyone else does.

    At the same time, that’s very human, and also frustrating, because you’d think people would care more about more secure solutions.

    Examples:
    ⬛️ Threads vs 🟪 Mastodon,
    🟩 WhatsApp vs 🟦 Signal.

    In both pairs you have seemingly similar services built on very different foundations. I use all of them myself. Why? Because when choosing technology, other people’s presence weighs surprisingly heavily on the scales.

    But what about Discord’s fate?

    Since the enshittification there seems to be moving at full speed already, I think it’s entirely reasonable to consider alternatives for the future. Open-source solutions would again be extremely solid here. Why 'again', you might ask? Because before Discord, we already had good, functional software:

    irssi & mumble

    But why go back to those? Because they simply seem to work - year after year, decade after decade.

    #SocialMedia #OpenSource #Discord #irssi #mumble #InfoSec

  30. Hi ya'll! Long time no see, Mastodon-peeps 🤓☕️

    Anyways! Discord is about to start requiring strong identity verification from users if they’re on a server with age restrictions. Verification would happen, for example, via an ID card. Quite a move from a company that leaked the data of 70,000 users a couple of months ago.

    This has sparked a lot of discussion today across several different groups. Tighter legislation in various countries has surely influenced Discord’s stance, but one could argue they might have chosen a different path.

    This piece of news served as inspiration to reflect on the resilience of commercial solutions. The idea of moving fully toward open-source solutions often crosses my mind, and in many cases I’ve taken steps closer to that world - though not always.

    Maybe the biggest pain point for me when adopting new (or old) technology is how many others come along. There’s little point in switching, say, to a new and more secure messaging app if hardly anyone else does.

    At the same time, that’s very human, and also frustrating, because you’d think people would care more about more secure solutions.

    Examples:
    ⬛️ Threads vs 🟪 Mastodon,
    🟩 WhatsApp vs 🟦 Signal.

    In both pairs you have seemingly similar services built on very different foundations. I use all of them myself. Why? Because when choosing technology, other people’s presence weighs surprisingly heavily on the scales.

    But what about Discord’s fate?

    Since the enshittification there seems to be moving at full speed already, I think it’s entirely reasonable to consider alternatives for the future. Open-source solutions would again be extremely solid here. Why 'again', you might ask? Because before Discord, we already had good, functional software:

    irssi & mumble

    But why go back to those? Because they simply seem to work - year after year, decade after decade.

    #SocialMedia #OpenSource #Discord #irssi #mumble #InfoSec

  31. Hi ya'll! Long time no see, Mastodon-peeps 🤓☕️

    Anyways! Discord is about to start requiring strong identity verification from users if they’re on a server with age restrictions. Verification would happen, for example, via an ID card. Quite a move from a company that leaked the data of 70,000 users a couple of months ago.

    This has sparked a lot of discussion today across several different groups. Tighter legislation in various countries has surely influenced Discord’s stance, but one could argue they might have chosen a different path.

    This piece of news served as inspiration to reflect on the resilience of commercial solutions. The idea of moving fully toward open-source solutions often crosses my mind, and in many cases I’ve taken steps closer to that world - though not always.

    Maybe the biggest pain point for me when adopting new (or old) technology is how many others come along. There’s little point in switching, say, to a new and more secure messaging app if hardly anyone else does.

    At the same time, that’s very human, and also frustrating, because you’d think people would care more about more secure solutions.

    Examples:
    ⬛️ Threads vs 🟪 Mastodon,
    🟩 WhatsApp vs 🟦 Signal.

    In both pairs you have seemingly similar services built on very different foundations. I use all of them myself. Why? Because when choosing technology, other people’s presence weighs surprisingly heavily on the scales.

    But what about Discord’s fate?

    Since the enshittification there seems to be moving at full speed already, I think it’s entirely reasonable to consider alternatives for the future. Open-source solutions would again be extremely solid here. Why 'again', you might ask? Because before Discord, we already had good, functional software:

    irssi & mumble

    But why go back to those? Because they simply seem to work - year after year, decade after decade.

    #SocialMedia #OpenSource #Discord #irssi #mumble #InfoSec

  32. Hi ya'll! Long time no see, Mastodon-peeps 🤓☕️

    Anyways! Discord is about to start requiring strong identity verification from users if they’re on a server with age restrictions. Verification would happen, for example, via an ID card. Quite a move from a company that leaked the data of 70,000 users a couple of months ago.

    This has sparked a lot of discussion today across several different groups. Tighter legislation in various countries has surely influenced Discord’s stance, but one could argue they might have chosen a different path.

    This piece of news served as inspiration to reflect on the resilience of commercial solutions. The idea of moving fully toward open-source solutions often crosses my mind, and in many cases I’ve taken steps closer to that world - though not always.

    Maybe the biggest pain point for me when adopting new (or old) technology is how many others come along. There’s little point in switching, say, to a new and more secure messaging app if hardly anyone else does.

    At the same time, that’s very human, and also frustrating, because you’d think people would care more about more secure solutions.

    Examples:
    ⬛️ Threads vs 🟪 Mastodon,
    🟩 WhatsApp vs 🟦 Signal.

    In both pairs you have seemingly similar services built on very different foundations. I use all of them myself. Why? Because when choosing technology, other people’s presence weighs surprisingly heavily on the scales.

    But what about Discord’s fate?

    Since the enshittification there seems to be moving at full speed already, I think it’s entirely reasonable to consider alternatives for the future. Open-source solutions would again be extremely solid here. Why 'again', you might ask? Because before Discord, we already had good, functional software:

    irssi & mumble

    But why go back to those? Because they simply seem to work - year after year, decade after decade.

    #SocialMedia #OpenSource #Discord #irssi #mumble #InfoSec

  33. Hi ya'll! Long time no see, Mastodon-peeps 🤓☕️

    Anyways! Discord is about to start requiring strong identity verification from users if they’re on a server with age restrictions. Verification would happen, for example, via an ID card. Quite a move from a company that leaked the data of 70,000 users a couple of months ago.

    This has sparked a lot of discussion today across several different groups. Tighter legislation in various countries has surely influenced Discord’s stance, but one could argue they might have chosen a different path.

    This piece of news served as inspiration to reflect on the resilience of commercial solutions. The idea of moving fully toward open-source solutions often crosses my mind, and in many cases I’ve taken steps closer to that world - though not always.

    Maybe the biggest pain point for me when adopting new (or old) technology is how many others come along. There’s little point in switching, say, to a new and more secure messaging app if hardly anyone else does.

    At the same time, that’s very human, and also frustrating, because you’d think people would care more about more secure solutions.

    Examples:
    ⬛️ Threads vs 🟪 Mastodon,
    🟩 WhatsApp vs 🟦 Signal.

    In both pairs you have seemingly similar services built on very different foundations. I use all of them myself. Why? Because when choosing technology, other people’s presence weighs surprisingly heavily on the scales.

    But what about Discord’s fate?

    Since the enshittification there seems to be moving at full speed already, I think it’s entirely reasonable to consider alternatives for the future. Open-source solutions would again be extremely solid here. Why 'again', you might ask? Because before Discord, we already had good, functional software:

    irssi & mumble

    But why go back to those? Because they simply seem to work - year after year, decade after decade.

    #SocialMedia #OpenSource #Discord #irssi #mumble #InfoSec

  34. I heard about Discord… really sucks, cuz I'm in a lot of Discord chats, although I mostly use only one channel the most.

    Anyways, I run my own IRC server, anyone can visit.

    To get started, depending on your OS, I recommend a good IRC client.

    On Linux: Konversation for graphical, weechat/irssi for terminal.
    On Windows: Hexchat. At least, that's what I used when I last used Windows.
    On MacOS: I don't recommend paying for an IRC client, but instead installing Homebrew and using the ones listed for Linux above.

    Once you have an irc client, login to the following:
    sparktown.xyz, port 6667(if you don't care about TLS) or 6697(If you do).
    Be sure to set a nick, and if you need help registering, let me know!

    I was going to try to run an XMPP/Jabber server and it initially was going well but then all the options got in the way, lol. I might try again later. Same for Matrix. There's also Signal, Session and Stoat/Revolt chats. Anyways, try out my IRC server if you want, thanks!


    #irc #server #signal #discord #session #stoat #konversation #weechat #hexchat #irssi
  35. Just set up #irssi (an #IRC client) again on my #RaspberryPi at home so that it starts at boot time and runs in the background. I'm hanging around on the #Ardour, #LAD, #LAU and #LinuxAudio channels.

  36. Just set up #irssi (an #IRC client) again on my #RaspberryPi at home so that it starts at boot time and runs in the background. I'm hanging around on the #Ardour, #LAD, #LAU and #LinuxAudio channels.

  37. Just set up #irssi (an #IRC client) again on my #RaspberryPi at home so that it starts at boot time and runs in the background. I'm hanging around on the #Ardour, #LAD, #LAU and #LinuxAudio channels.

  38. Just set up #irssi (an #IRC client) again on my #RaspberryPi at home so that it starts at boot time and runs in the background. I'm hanging around on the #Ardour, #LAD, #LAU and #LinuxAudio channels.

  39. I don't remember why, but apparently i scripted `/shrug` in my #irssi client to run `curl -s shrug.io`.

    Someone did not renew that domain and now redirecting to the godaddy landing page.

    I'm currently spamming people with "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href="/lander"}</script></head></html>".

  40. I don't remember why, but apparently i scripted `/shrug` in my #irssi client to run `curl -s shrug.io`.

    Someone did not renew that domain and now redirecting to the godaddy landing page.

    I'm currently spamming people with "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href="/lander"}</script></head></html>".

  41. I don't remember why, but apparently i scripted `/shrug` in my #irssi client to run `curl -s shrug.io`.

    Someone did not renew that domain and now redirecting to the godaddy landing page.

    I'm currently spamming people with "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href="/lander"}</script></head></html>".

  42. I don't remember why, but apparently i scripted `/shrug` in my #irssi client to run `curl -s shrug.io`.

    Someone did not renew that domain and now redirecting to the godaddy landing page.

    I'm currently spamming people with "<!DOCTYPE html><html><head><script>window.onload=function(){window.location.href="/lander"}</script></head></html>".

  43. I don't remember why, but apparently i scripted `/shrug` in my #irssi client to run `curl -s shrug.io`.

    Someone did not renew that domain and now redirecting to the godaddy landing page.

    I'm currently spamming people with "<!DOCTYPE html><html><head>...".

  44. Well, XDG is more of a guideline. Yes, I'm looking at you, Irssi.

    #irssi #xdg

  45. Well, XDG is more of a guideline. Yes, I'm looking at you, Irssi.

    #irssi #xdg