kbinDevlog

Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.

sz, w RTR#22 Further improvements interspersed with code refactoring

Good job
Looking forward to seeing Mercure here

thisismissem, w /kbin RTR#19 Summary of current work and plans for the near and somewhat distant future
@thisismissem@hachyderm.io avatar

@ernest Will the spoiler system also be compatible with Mastodon? This would be very good to have.

(or, alternatively, can we get a FEP for a proper spoiler system other than using the summary field?)

ernest,
@ernest@kbin.social avatar

Definitely, I plan to integrate spoilers with ActivityPub. For now, it's just a Markdown change compatible with Lemmy - there were many requests for it, and it was quite cumbersome. I will start working on federation after finish the refactoring. I want to do this on the new codebase - I'm getting closer, but initially, I'm fully focused on instance moderation, which will enable the operation of a global moderation team. Later, things with lower priority will be gradually implemented.

Teppic, w RTR#21 Sub channel filters, spoiler tag
@Teppic@kbin.social avatar

I need to update this now, but it is still relevant:
https://kbin.social/m/fediverse/t/275724/Browsing-the-wider-fediverse-from-kbin

jupiter_rowland, w /kbin RTR#19 Summary of current work and plans for the near and somewhat distant future

That sounds good, for /kbin seems to generally have troubles with federating to the outside Fediverse. For example, formatted posts or posts with embedded links go out as raw Markdown code, implying that everything else can and will parse it, rather than standard Rich Text.

Also, I sometimes see posts from /kbin with a summary (the same as a content warning on Mastodon; I don't know what /kbin uses that field for), but the post in the summary is the same as the summary, only without hashtags which only appear in the summary.

lusterko, w /kbin RTR#19 Summary of current work and plans for the near and somewhat distant future

Resolution of several bugs causing the failure to display certain content (error 500).

It seems that Lemmy instances are unable do display new content that was posted on kbin.social. is this the big you're talking about?

e0qdk,
@e0qdk@kbin.social avatar

I'm not sure what ernest is referring to with that, but something definitely does seem to be up with federation of content from kbin over to lemmy.

e.g. in /m/anime_irl the last three threads posted have not federated out. I commented here with a list of 5 lemmy servers I checked on a 24 hour old post that hasn't shown up elsewhere (after noticing my own post wasn't showing up).

There's also something going on with comments added by lemmy users on threads that have federated not going out to other lemmy instances. e.g. on this thread from 5 days ago only my first comment has federated widely; the other comment chain (starting with the user from lemmy.world) are only visible on kbin.social and lemmy.world, as far as I can tell. Not sure if that's exactly the same issue or not, but seems plausible for it to be related if something isn't working correctly with federation right now.

Comments that I've made on lemmy threads have gone through today though.

ernest,
@ernest@kbin.social avatar

I will look into this. I will also gradually address federation issues. However, I'm not sure if the problem is on the kbin side. Currently, there are no performance issues; all queues are being cleared in real-time. Communication on my test instances with kbin.social takes a matter of seconds.

lusterko,

Idk what's the problem, but if I'm using Lemmy I'm only able to see the posts from almost two days ago, and nothing from what I've posted today. There was a problem a few months back, when my posts would appear on lemmy one to three hours after posting on kbin.

ernest,
@ernest@kbin.social avatar

I'll look into what's going on, and I'll move it up higher on my priority list. Anyway, it's not a federation issue in general.

https://mastodon.social/@lusterko@kbin.social

ernest,
@ernest@kbin.social avatar
lusterko,

Is it possible that it's because of something on Lemmy's end?
Edit: forgot to switch to the "new", but the newest visible posts are also 2days old

GeekFTW,
@GeekFTW@kbin.social avatar

Also having the same thing happen over on /m/SquaredCircle for what it's worth. Just noticed last night after a particularly slow day. Logged into my lemmy.zip alt and noticed nothing for near 48h had come across from kbin. Checked another alt on another lemmy instance and it was more or less the same there too.

ernest,
@ernest@kbin.social avatar

Fixed, thank you for pointing it out. During the night or in the morning, when there is less traffic, I will try to resend all unsuccessful requests.

This week, I will be setting up test environments for other platforms, so I will try to catch such issues more quickly.

https://lemmy.zip/c/music@kbin.social

@sab @e0qdk

lusterko,

Works well now, thanks!

Teppic, w /kbin RTR#15 Cleanup Continues, Nodeinfo 2.1 Support, KES 3.0.0
@Teppic@kbin.social avatar

For those (like me) who are wondering... Nodeinfo is a standard seeking to improve interoperability between fediverse platforms.

https://github.com/jhass/nodeinfo

  • Wszystkie
  • Subskrybowane
  • Moderowane
  • Ulubione
  • test1
  • Spoleczenstwo
  • lieratura
  • muzyka
  • rowery
  • sport
  • Blogi
  • Technologia
  • Pozytywnie
  • nauka
  • FromSilesiaToPolesia
  • fediversum
  • motoryzacja
  • niusy
  • slask
  • informasi
  • Gaming
  • esport
  • Psychologia
  • tech
  • giereczkowo
  • ERP
  • krakow
  • antywykop
  • Cyfryzacja
  • zebynieucieklo
  • kino
  • kbinDevlog@kbin.social
  • warnersteve
  • Wszystkie magazyny