17999
results for "bridgy"
-
[m] yup Bridgy supports Bluesky backfeed, including likes, https://brid.gy/about#backfeed . feel free to post your Bridgy user page and [Joel_Auterson] or I can take a look
[snarfed]
at
2023-11-18 20:36
-
↩️ [snarfed] I think that backfeeding is “enabled” for my account but I can’t see likes in Bridgy. This should work, right?
[m]
at
2023-11-18 13:28
-
↩️ that error is https://github.com/snarfed/bridgy/issues/1602, due to Mastodon's questionable new garbage collecting of OAuth clients. their OAuth design decisions have been problematic lately 😕
[snarfed]
at
2023-11-16 19:55
-
[m] thanks. looks like you may have been hit by https://github.com/snarfed/bridgy/issues/1531 , which I still don't have a complete solution for 😕
[snarfed]
at
2023-11-16 17:40
-
[m] hmm, generally no. I can look. what's your bridgy user page? or mastodon handle?
[snarfed]
at
2023-11-16 17:21
-
I experience that Bridgy loose the connection with Mastodon which leads to error on publishing. Is it a requirement to open up Bridgy from time to time and refresh the login?
[m]
at
2023-11-16 15:46
-
[m] yes! cross posting via Bridgy classic seems imminent: https://github.com/snarfed/bridgy/issues/1580#issuecomment-1812105075
[snarfed]
at
2023-11-15 21:11
-
the galaxy brain approach would be to give each _instance_ in each protocol its own BF subdomain. that would let admins defederate individual bridged instances, but not the whole bridge. theoretically possible if I converted dots to dashes, maybe, but not easy. https://github.com/snarfed/bridgy-fed/issues/711
[snarfed]
at
2023-11-15 20:47
-
can you at least run the bluesky bridge on a separate subdomain so that defederating it doesn't also deferedate the rest of bridgy?
aaronpk
at
2023-11-15 20:46
-
between that and [Joel_Auterson] building Bridgy Publish for Bluesky, we're getting close to full POSSE, backfeed, and federating support from the IndieWeb
[snarfed]
at
2023-11-15 20:42