interesting writeup from the maintainer of the original software #birdsitelive (which #birdmakeup is a fork of) about the practical reasons they stopped running it, and at least one missing piece that a Twitter bridge would need to play nice
https://write.as/nicolas-constant/closing-the-official-bsl-instance
Aaand it's official, my #BirdsiteLIVE instance doesn't work anymore. I think Twitter has finally implemented the rate limiting they want and restricted the access on free API keys to a subset of endpoints that aren't enough to run the BirdsiteLIVE instance without paying for more access.
I suggest everyone move to https://bird.makeup/ instead of using my instance. I'll keep the URL live and update the page with recommendations to move to bird.makeup instead after taking my instance offline.
To everyone using my #BirdsiteLIVE instance at https://birdsite.thorlaksson.com to follow Twitter accounts you may need to refollow those accounts again. There was a DB issue causing everything to lock up on the instance and I just destroyed and recreated everything in a final attempt to fix the issue.
If that doesn't fix the problem I'll take down the instance and instead recommend y'all use https://bird.makeup/ instead, since that doesn't rely on the Twitter API.
@BirdsiteLIVE Is there any hope of fixing the protocol incompatibility problem between #birdsitelive and #mastodon ? :xueyi_sad:
@board 该迁移会通知关注者将镜像账户迁移到你的正式fediverse账户,之后就会被禁用。
步骤:
先要准备一个fedi号,比如 @ 2023 @ may. 23th
在bird site live复制灰色框内的信息,粘贴至Twitter并公开发送。
在bird site live白色框输入新fedi号+在上一步已发表的推文链接。
最后点击migrate
#birdsitelive #联邦宇宙漫游指南
@board 该迁移会通知关注者将镜像账户迁移到你的正式fediverse账户,之后就会被禁用。
步骤:
先要准备一个fedi号。
在bird site live复制灰色框内的信息,粘贴至Twitter并公开发送。
在bird site live白色框输入新fedi号+在上一步已发表的推文链接。
最后点击migrate
#birdsitelive #联邦宇宙漫游指南
I accidentally stumbled across another #BirdSiteLIVE robot site myself, today: https://t.l3r.me/
It came up in a MastodonApp.UK search result. @Artifex and @oliphant both already have it on their lists. I just checked.
Just found out about bird.makeup.
How long will this one stay afloat? #BirdsiteLIVE instances don't tend to last very long.
#BirdsiteLIVE 0.23.0 is out!
It brings two major aspects:
- IP whitelisting, you're now able to hide your instance for a completely private node
- Posts auto-clean up; keeping a permanent mirror of content isn't great, BSL will now delete synchronized content after 20 days (value can be customized). 🙂
@hack13 @joolischka thank you for your detailed steps! <3 [i'm curious if the person owning the account can see at any step which users of the fediverse are following? i'd say that would be vital for my decision on step 4] #BirdsiteLIVE
@joolischka@home.social das ist, weil irgendjemand vom fediverse aus mittels #BirdsiteLIVE Deinem twitter-account folgt [und sich möglicherweise freuen wird, Dich im fediverse selbst zu finden <3]. schau mal bei @joolischka@tweets.icu: „take control of this account” https://tweets.icu/migration/move/joolischka
Taka ciekawostka o bird.makeup, forku #BirdSiteLIVE
Autor właśnie zaimplementował RT, ale zupełnie inaczej niż znamy z różnych bramek TT -> #Mastodon
Jeśli obserwowany bot profilu TT robi RT, wygląda to obecnie jak natywne podbicie (boost/repost) Mastodona.
Jak na obrazku.
Źródło pokazuje też implementację statusów profili tworzonych on-demand -> https://birb.stream/users/bobik314/statuses/1625537822701518848
Uwaga! To nam może sprowadzić tutaj niejawnie całe #birdsite w trybie read-only, bo profilu AKwiatkowski nie śledzę 😉
#BirdsiteLIVE #mastodon #birdsite
Jutro, 13.02, czyli już za kilka godzin #Twitter zablokuje dostęp do bezpłatnego API dla aplikacji.
Oprócz wielu mniejszych systemów, bramek jak #BirdsiteLIVE, staną również duże serwisy pokroju IFTTT.
#Nitter powinien "przeżyć".
Czy to spowoduje dostrzeżenie otwartego charakteru #Fediverse? Jak dalece biznesy będą nadal "ufać" TT?
Czy i jakie przyszły tydzień przyniesie zmiany i reakcje?
Elon już raz odłożył wstrzymanie dostępu do API.
Tym razem takich informacji nie widziałem.
Ciekawe :)
#twitter #BirdsiteLIVE #nitter #fediverse
Just realised that Tweetbridge no longer works, along with any Birdsite LIVE accounts. Guess I can’t “follow” Twitter accounts that aren’t over here anymore. :(
#tweetbridge #BirdsiteLIVE #screwelon
Oha, da haben sie aber bei #Twitter mit dem neuen #Tweetdeck aber so einiges kaputt gemacht.
Habe darüber ja noch so ein paar Sachen verfolgt, aber jetzt ist es wohl wirklich Zeit dieses Kapitel abzuschließen.
Mit #BirdsiteLIVE verfolge ich ja noch ein paar Twitter Poster auch im #Fediverse.
#fediverse #BirdsiteLIVE #tweetdeck #twitter
Perhaps I spoke too soon. The developer of #BirdsiteLive chimed in and said he would be adding the ability to either 1) use Twitter API keys if you have them or 2) use the "undocumented API" like Nitter. 🐦 ➡️ 🐘 🎉
https://github.com/NicolasConstant/BirdsiteLive/issues/189#issuecomment-1419996503
@witewulf had to spin up my own instance of #BirdsiteLIVE on @wild1145 hosting and use it for myself only to read a dozen of Twitter people. Whatever is interesting I have to repost via my Twitter account over there, to have it synced back to Mastodon via #Moa.
Will have to figure out a new way once this idiot kills read APIs. I wonder if IFTTT will be working, but also there is #Nitter.
All in all - lot of unnecessary work to keep few interesting people together in a single feed.
It looks like #Nitter might survive Twitter's API tightening:
https://github.com/zedeus/nitter/issues/783
#BirdsiteLive is probably dead in the water though, since it relies on having valid developer API keys.
I only have 17 Twitter accounts left that I'm still following. I would love it if those accounts would just come to Mastodon, but there's no sign of that happening (yet).
I guess for now I will take down my BirdsiteLive bridge and go back to using Nitter + RSS.
Twitter is closing its free API access? Bye, bye #BirdsiteLive Twitter-Mastodon bridge, I guess. It was a short pleasure. *sigh*
I assume this means the effective death of #BirdsiteLIVE? I only use it to follow a handful of accounts, but it would be a shame for that to stop. I suppose I can always try to use some kind of RSS-based solution instead...