this post was submitted on 28 Jul 2023
22 points (100.0% liked)

Quark's

27 readers
2 users here now

Come to Quark’s, Quark’s is Fun!

General off-topic chat for the crew of startrek.website. Trek-adjacent discussions, other sci-fi television, navigating the Fediverse, server meta (within reason), selling expired cases of Yamok sauce, it’s all fair game.

founded 1 year ago
MODERATORS
ValueSubtracted@startrek.website
Admin@startrek.website
williams_482@startrek.website
22
StarTrek.website has updated to Lemmy version 0.18.3 (startrek.website)
submitted 1 year ago by Admin@startrek.website to c/quarks@startrek.website
9 comments fedilink hide all child comments
 

Release notes here.

This should decrease the variance we've been seeing in the impulse manifolds, bringing it back to within acceptable parameters. I'm told if any of you notice intrusive thoughts involving Intendant Kira Nerys you should report to sick bay immediately where they should be able to help you intensify them.

you are viewing a single comment's thread
view the rest of the comments
[–] triktrek@startrek.website 2 points 1 year ago (2 children)

Not sure if it's related to this instance update, but I noticed that the "Show Context" link doesn't work for me anymore. When I see people reply on my comment from the top-right bell icon, I can see people's replies. When I click on "Show Context" it doesn't show me the full context (my originally comment), but just still only shows the single reply.

[–] ValueSubtracted@startrek.website 3 points 1 year ago (2 children)

I've noticed the same - must be a new bug.

[–] StillPaisleyCat@startrek.website 1 points 1 year ago

Actually, it has a new twist for me.

When I tried to look at the reply of a user from another instance but the thread was on our main c/startrek here, I was given a ‘log into kbin page.’

[–] StillPaisleyCat@startrek.website 1 points 1 year ago

I have been having that issue intermittently. I didn’t realize it’s new to others.

[–] Admin@startrek.website 3 points 1 year ago (1 children)

Thanks I looked into it and it looks like it's a known bug with this update.