Kaito / Katie Sinclaire @KS@is.a.qute.dog

Anyway here, have a pair of qutes https://is.a.qute.dog/media/7Kep5bI5Git80tH0eyI

Can't get away from the feeling that the "mastodon is dead" article is overblown and exaggerated to a ridiculous degree. A public timeline is never going to stay a close-knit circle of friends as soon as any popularity is gained; expecting it to is complete nonsense. That's what local timelines are for.

And by the way, if your reaction to an instance for conservatives would be "nuke on sight", you're part of the problem.

I wish I felt confident about myself when I write anything...

@Raspberryfloof check the web console and see what you're getting in response to the periodic api/v1/streaming calls?

The joys of open source: I pulled in a PR (instance colors on mentions) from @mykola because I wanted the feature on my own instance even though it seems Mastodon doesn't!

Time for bed... zwz

Sylv...~

woof...

I feel kinda stupid and silly now

All of that wild goose chase and it turns out my cron jobs weren't running right because the tasks were running in the wrong directory.

Um, oops.

@andlabs <3

@andlabs for what it's worth, if I pull up the search bar, paste the url to your post in it, and "search" for it, that post instantly shows up on my timeline and I can interact with it, but none of your others

@KitRedgrave @andlabs yep, I can see it fine

@andlabs woof?

More specifically, this seems to have started about 21 hours ago, so...

I don't seem to be getting timeline updates from a lot of instances now that I've updated to 1.2.2...

I can still search for statuses from those instances that aren't on my timeline and it pulls them up fine, but my timeline is quite silent otherwise

https://is.a.qute.dog/media/3ptNLkw0L94sjZtjcsU Saving for posterity

> Home to NaN users
> Who authored ∞ statuses

You know, I think it's better like this =w='

https://github.com/tootsuite/mastodon/pull/2192

help oh god why am I feeling all scared or worried for submitting a pull request for monologuing

I guess it was just an issue with my dev environment. Works fine live in production. Weird.