#bitlbee — Public Fediverse posts

I am interested if anyone has (or is working on) a plugin for #bitlbee or #weechat for Bluesky (like the bitlbee plugin for Mastodon). While I'm aware you can use RSS feeds for individual users, I'm wanting a home timeline feed, preferably with ability to reply, but read-only is okay.

I am interested if anyone has (or is working on) a plugin for #bitlbee or #weechat for Bluesky (like the bitlbee plugin for Mastodon). While I'm aware you can use RSS feeds for individual users, I'm wanting a home timeline feed, preferably with ability to reply, but read-only is okay.

so because I don't have anything better to do my current setup looks like this: I am using debian 12 in wsl on windows 11 to connect irssi (#irc client) to my znc bouncer on my Debian VPS that connects to #bitlbee on the same VPS to connect to #discord via purple. All that so I can chat with a friend on discord from the terminal instead of switching to the other window.

And the worst is that it works without a hitch.

so because I don't have anything better to do my current setup looks like this: I am using debian 12 in wsl on windows 11 to connect irssi (#irc client) to my znc bouncer on my Debian VPS that connects to #bitlbee on the same VPS to connect to #discord via purple. All that so I can chat with a friend on discord from the terminal instead of switching to the other window.

And the worst is that it works without a hitch.

@erion @pitermach these are CLI tools, but interesting. #bitlbee can also be used to make protocols accessible, through #pidgin app

@pitermach @erion I mainly use #weechat as an accessible client for #irc and I also use, throught it, #bitlbee to access other protocols.

@rolle
During the better part of a decade I ran all IM in Irssi via the BitlBee gateway. Loved every second of it! :-)

#irssi #bitlbee

I got tired of having to open and look at ten different programs/websites/devices for instant messaging; and decided to centralize all my IM needs on my irc client with #bitlbee and #libpurple.

But telegram and whatsapp make doing that such a headache that i decided to give up after two days of failed set up. I will just minimize the use of those IMs to check once a week and keep using IRC as The One True group chat as i always have done.

> "alternatively keep yourself sane and just stick to a phone for those things... because at this point, it's not even worth fighting for an already lost cause" -- @yakumo_izuru

Any #Pleroma/#Akkoma users out there who have had any luck with the #bitlbee integration, or any other way of #IRC bridging?

I used bitlbee-mastodon on Mastodon before, but it breaks on Pleroma because of streaming API incompatibilities. There seem to be an open issue on Pleroma too which apparently hasn’t been actioned in years.

@zimpenfish suggested here to use the native Bitlbee identica plugin, but I haven’t had any luck with that either.

Is there anyone currently working on these issues, or who has any alternatives at hand, before I try and do some more debugging myself?

@pitermach @dsilverman here we use the website or a gateway #bitlbee from #irc to #mastodon

@jaruzel
Interesting thought. Let's stretch the IRC metaphor: presumably you would /connect to instance(s); would the channels be corresponding to users, tags, or lists that you follow?

I wonder if there's any chance that #Bitlbee might (or might have already) look(ed) into adding #ActivityPub support.

@jaruzel
Interesting thought. Let's stretch the IRC metaphor: presumably you would /connect to instance(s); would the channels be corresponding to users, tags, or lists that you follow?

I wonder if there's any chance that #Bitlbee might (or might have already) look(ed) into adding #ActivityPub support.

@ColinTheMathmo The text-based client #bitlbee w/Mastodon plugin is quite useful in this way. It’s not graphical but every msg gets a 2 char ID and every reply is prefixed w/an arrow showing new ID & parent ID. E.g. your msg looked like this to me: “ColinTheMathmo> [57->5c] @koherecoWatchdog Thank you!…”, so I see your msg (57) replied to my msg (5c).

@ColinTheMathmo The text-based client #bitlbee w/Mastodon plugin is quite useful in this way. It’s not graphical but every msg gets a 2 char ID and every reply is prefixed w/an arrow showing new ID & parent ID. E.g. your msg looked like this to me: “ColinTheMathmo> [57->5c] @koherecoWatchdog Thank you!…”, so I see your msg (57) replied to my msg (5c).

The first open source project I ever contributed to was #Bitlbee, the Instant Messaging gateway.

Remember Instant Messagers? Anyway, turns out the last thing I was using it for was Twitter.

When the free API was turned off on the 6th, the era of Bitlbee ended for me too. Bummer.

The first open source project I ever contributed to was #Bitlbee, the Instant Messaging gateway.

Remember Instant Messagers? Anyway, turns out the last thing I was using it for was Twitter.

When the free API was turned off on the 6th, the era of Bitlbee ended for me too. Bummer.

@mickdarling @jupiter_rowland @fediversenews Yikes! Way to wipe out a big chunk of my buffer. CWs don’t work the same in all clients. In #bitlbee (a text client), we just see the CW as the 1st line, almost like a subject line, then all the content that follows automatically.

@mickdarling @jupiter_rowland @fediversenews Yikes! Way to wipe out a big chunk of my buffer. CWs don’t work the same in all clients. In #bitlbee (a text client), we just see the CW as the 1st line, almost like a subject line, then all the content that follows automatically.

Looks like Bitlbee-Twitter integration is also over now.

#Bitlbee
#TwitterAPI #TwitterIsGoingGreat

Looks like Bitlbee-Twitter integration is also over now.

#Bitlbee
#TwitterAPI #TwitterIsGoingGreat

I really hate the #Mastodon #search function not because it's restricted in what is searchable and what isn't, but because of how impractical it is within those restrictions.

To wit, if I want to find a post of mine containing a specific word or set of words, I'm better off using #grep on my #WeeChat logs than using the search function!

(Why WeeChat logs? Because I have a #Bitlbee bridge set up. I don't actually use it much, but it does come in handy in these circumstances.)

I really hate the #Mastodon #search function not because it's restricted in what is searchable and what isn't, but because of how impractical it is within those restrictions.

To wit, if I want to find a post of mine containing a specific word or set of words, I'm better off using #grep on my #WeeChat logs than using the search function!

(Why WeeChat logs? Because I have a #Bitlbee bridge set up. I don't actually use it much, but it does come in handy in these circumstances.)

Hooray! Not sure what I did different, but recreating the #bitlbee account works, and now I have an easy way to do full text-search on my timeline :)

Hooray! Not sure what I did different, but recreating the #bitlbee account works, and now I have an easy way to do full text-search on my timeline :)

More generally, anyone set up #bitlbee to work with #techlgbt

https://tech.lgbt/@zigdon/109785697918427715

#bitlbee users: anyone tried to chat over mastodon with otr enabled?..

#mastodon plugin and #bitlbee working well now #happynewyear

@peterwidmayer @mrvapor @jeffjarvis @CathieEnglish @MattHodges I use the Mastodon plugin for #Bitlbee, which is a purely text UI inside of an IRC client. Every post gets a 2 char ID & every reply shows an arrow which makes it very easy to see tree w/branches from the linear display. E.g., your post was given a temp ID “[fc]” & when mrvapor replied his post started with “[13->fc]”. This is much easier to follow than the web UI.

For some reason it crashes #bitlbee when I login to #fosstodon @[email protected]

With all the interest in #mastodon I kinda wish the #libpurple #bitlbee or #irssi plugin compatibility wasn't so buggy...

As much as the new influx of users is exciting and positive.. I doubt its going to expand the use of #bitlbee or Irssi users 💘

@jerry @tes The Mastodon #Bitlbee plugin, which is a pure text bridge to an IRC client. It’s extremely efficient for those who already use IRC, as Mastodon timelines just become another IRC channel right next to the real IRC channels. The keyboard is faster than the mouse. #fuckGUIs