good point
except that is considerably better than “throw shit at a wall until it sticks” approach that some HWW manufacturers take
though they also do not know how an SE should be properly used
Yes.
Integration is not possible due to economic reasons.
You can’t.
It is objectively not in X’s best interests. Being a SPOF is fine for them as long as they retain control and can lock people in
reminder to not update a rolling distro only halfway
If you’d like to illuminate the twitter devs add your commentary here
https://github.com/twitter/twitter-server/issues/81 nostr:note194wdd5hgcca6ykkgvgrycp7dvng8fa8erlrflcmw9jrf09amhxhqptjxnp
What the fuck.
In a bad way.
uhh I mean a signing device
Kotlin supports types. And it has proper null checks unlike Java
I used it for a web app a few years ago.
Was not good as frameworks like Svelte. But also was somewhat better than writing raw JS
yes
also, unlike most HWW vendors, proper industry standard software development practices will be employed
We have an imeta tag already.
We could add a field to force inline display.
I was proposing more of an idea for future implementation.
Images that should be grouped should be listed in succession

