Este feed foi encerrado. Estou sujeito a leis locais que a plataforma está aplicando incorretamente. Não desejo cumprir esta nova barreira à entrada.

Obrigado a todos que utilizaram e contribuíram para o feed.

Este feed ha sido cerrado. Estoy sujeto a leyes locales que la plataforma está aplicando incorrectamente. No deseo cumplir con esta nueva barrera de entrada.

Gracias a todos los que utilizaron y contribuyeron al feed.

이 피드가 종료되었습니다. 저는 플랫폼이 잘못 시행하고 있는 현지 법률의 적용을 받게 되었습니다. 저는 이 새로운 진입 장벽을 준수하고 싶지 않습니다.

이 플랫폼의 한국 커뮤니티에 특별한 감사를 전하고 싶습니다. 커뮤니티가 아직 작은 상황에서 이 피드의 성장을 촉진한 것은 여러분의 노력 덕분입니다. 영원히 감사드립니다. 🙏

このフィードは終了しました。プラットフォームが誤って適用している現地法の対象となってしまいました。この新たな参入障壁には従いたくありません。

プラットフォームの初期からこのフィードを利用し、貢献してくださった多くのユーザーとアーティストの皆様に感謝申し上げます。

Last night the feed was turned off permanently. This decision was made due to Bluesky voluntarily complying to a new anti-human law from which they are already exempt.

I would like to thank everyone who has used, spread the word of, contributed to and appreciated the labor of the feed.

*6 hours behind

The Yuri feed is up and running again. At the time of this post, it is running about 6 hours. It should catch up to real time by the end of the night.

It will not be back up tonight or tomorrow morning.

The feed died on Yuri day. There was too much Yuri. Hopefully we'll have it back up tonight or tomorrow morning.

Cloudflare's repair script is going to take at least another week before it is done running, in the best case scenario. Apologies, we got what we paid for.

Options for the future of the feed are being weighed.

(There is also no guarantees any of this will actually resolve our issues.)

Apologies but we are relying on a hack provided to us by Cloudflare and the script is still only about 85% through its initialization stage after almost 24 hours. We have no idea how long the script will take to do its job after this step.

The feed has been shut down for an indeterminate amount of time. Will update with details later.

Server Maintenance 👷‍♀️👷‍♀️ 🚧

The #Yuri feed is back up! It went down last night when Jetstream disconnected (still working on fail-safe solutions to this). I took the opportunity to write some new settings that would let me catch the feed up much quicker than before. 11 hours was caught up in 20 minutes, instead of a few hours.

A billing issue caused our VPS service to be interrupted. IT has been restarted and the feed will begin catching up from yesterday. Apologies.

The Jetstream instances we source our posts from was knocked out last night, about 12 hours ago. The feed is in the process of catching back up to real time. Expect some possible weirdness for the next few hours as everything gets back into sync.

During the past hour there was an outage of Bluesky's jetstream, which is the live feed of posts that BlueNotify uses to send notifications

That's resolved now!

The average time from post to push notification in BlueNotify is less than a second, so if you continue to see delays something is weird!

Bluesky's jetstream is back online. BlueNotify notifications will continue going out (and the system is processing the backlog so no notification should be missed!)

The problem has been isolated. The last 9 hours of the feed will be rebuilt to include all languages, this may result in some odd chronological behavior. Sorry for this oversight.

I think non-English languages have somehow been broken for the feed. I will look into it later today.

Feed is in maintenance mode. Expect weirdness!

The feed is back up and running. Unfortunately there is about a 14 hour gap of posts that were not picked up and recovering that time is not practical option at the moment. We may be stretching the limits of free resources. Apologies.

이 계정에는 최우선 순위가 부여될 예정이었지만 실수로 금지되었습니다. 오늘에서야 알게 되었습니다. 죄송합니다. 앞으로 피드에 게시물이 포함될 예정입니다. @dailyuribot.bsky.social