of course he was afraid of russian nuukes. this only prompted Ukrainian engineers to bypass use of starlink entirely and current sea drones, like the one used in second Kerch bridge strike, or these used against SIG tanker and Olenegorsky Gornyak landing ship use domestic technology only
lemmy is the mastodon of the threadiverse in that it invents a standard and expects everyone to follow it and because it’s the largest of it’s type you can’t really do anything about it
i bet what’s going on is that kbin is attaching images in the mastodon/microblog way and lemmy expects inline markdown images and doesn’t try to extract the attached images.
(fun fact: lemmy custom emojis are just “macros” for markdown images and not real emojis like the rest of the fedi standardized on (which is how you get things like the hexbear problem of remote emojis being gigantic))
lemmy has a lot of questionable design decisions, and the justifications I’ve seen for them on GitHub have very frequently been disappointing
on the other hand, it’s a lot easier for me to understand and modify lemmy’s rust-based stack than it is for me to comprehend the PHP kbin is written in, which is a big part of why this instance ended up with lemmy
with that said, holy fuck am I looking forward to contributing to a lemmy fork with better development priorities one of these days
i’d love to take a peek at a “glitch-soc for lemmy” but not that many people seem keen enough to fork and take on the responsibility of maintaining the jank.
that said i know of at least 2 instance specific forks (pawb.social’s and programming.dev’s), yet neither of them seem to have produced anything worthwhile just yet.
I’m in a similar boat. ours is also a minor instance-specific fork, though trying to get our changes upstreamed is on my todo list (as are more changes — it’s kind of amazing how threadbare lemmy’s mod tools are, when a lot of them wouldn’t even be hard to implement)