dannekrose opened issue firefish/firefish#10527
[Bug]: Antennas continuously loop if there are more than one "page" of posts
dannekrose commented on issue firefish/firefish#10425
[Bug]: Server Performance statistics and Identicon toggles don't seem to work.The toggles appear to work now in the latest DEV, but the label for the toggles don't show for me still. I only knew what they were from looking at the code and the db values. Thank you.
dannekrose opened issue firefish/firefish#10425
[Bug]: Server Performance statistics and Identicon toggles don't seem to work.
dannekrose opened issue Kbin/kbin-core#584
[Feature] Allow certain followed user accounts to have all content routed to a magazine without having to rely on hashtags
dannekrose closed issue firefish/firefish#10387
[Bug]: Streaming doesn't work in latest dev.
dannekrose commented on issue firefish/firefish#10387
[Bug]: Streaming doesn't work in latest dev.Closing for now, but I suspect it is somewhat related to the redis changes. I rolled back, but had to still restart via pm2 restart on the older build to get the updates working again.
dannekrose commented on issue firefish/firefish#10387
[Bug]: Streaming doesn't work in latest dev.Understood. I don't see any logs that appear to be showing any issues on the server-side and the websocket connection does appear to be working. Is this related to code around the adding of…
dannekrose commented on issue firefish/firefish#10387
[Bug]: Streaming doesn't work in latest dev.To be clear, the widgets are updating and I see the websocket connection working. It's not sending new posts through websockets.
dannekrose opened issue firefish/firefish#10387
[Bug]: Streaming doesn't work in latest dev.
dannekrose commented on issue Kbin/kbin-core#528
No content in magazines followed from MastodonHere is the Mastodon PR that would add support for everything discussed here. It's been open since August 2022. https://github.com/mastodon/mastodon/pull/19059
dannekrose commented on issue Kbin/kbin-core#528
No content in magazines followed from MastodonIn my opinion, this is something for Mastodon to implement. Kbin, Lemmy, Frendica, and maybe other platforms understand this data as expected. The reason you can see posts from gup.pe groups…
dannekrose closed issue Kbin/kbin-core#34
Request to add newly finished Japanese translation
dannekrose commented on issue Kbin/kbin-core#34
Request to add newly finished Japanese translationclosing!
dannekrose commented on issue Kbin/kbin-core#528
No content in magazines followed from MastodonTo clarify: Mastodon doesn't understand kbin "Link" threads. Those are sent to Mastodon just like everthing else, but Mastodon can't process the content properly.
dannekrose commented on issue Kbin/kbin-core#528
No content in magazines followed from Mastodon> Really? I don't get anything, and looking up a magazine just shows it like this (this is one I created and have been following from the start, it doesn't have many posts but it has more than…
dannekrose commented on issue Kbin/kbin-core#528
No content in magazines followed from MastodonThey are. You can find them in your Global timeline. Try it out. Follow a magazine (probably on a smaller kbin instance so it doesn't get backed-up due to being too busy). Create a new…
dannekrose commented on issue Kbin/kbin-core#528
No content in magazines followed from MastodonThe reason it looks blank and empty in Mastodon is that content is sent by kbin to Mastodon, but Mastodon doesn't understand Group accounts. Mastodon thinks the author of the content is the user…
dannekrose closed issue firefish/firefish#10357
[Bug]: @ "at symbol" in actor value does not appear to be understood by Calckey properly
dannekrose commented on issue firefish/firefish#10357
[Bug]: @ "at symbol" in actor value does not appear to be understood by Calckey properlyI think I had some bad data in my redis perhaps. I don't know exactly what fixed it, but thank you and I'm closing this for now.
dannekrose commented on issue firefish/firefish#9583
[Feature]: External blocklist sourcesI realize that some of the points I summarized as being the feature request were a bit ambiguous and not fully explicit in what the feature(s) would involve and that I should have made more things…