aard

A major difference is how they interact with feedback - the main reason I never did my own mastodon instance is the developers attitude. “We’re not interested in helping you because you didn’t set it up exactly as in the guide” was (and maybe still is) all over the mastodon bug tracker.

That was the first thing I looked for when lemmy became popular - and found they were taking deployment issues to even the most absurd system seriously.

Additionally they treat suggestions seriously - even if they personally think it is stupid - and even implement some of that. Pretty much no chance of anything of that happening with mastodon.

My m13 is from 1994, and I have non-trackpoint Model Ms going back to the late 80s, all working perfectly fine.

IBM Model M clone

Want to try with an original?

Also, surprising you kept the wife, not the keyboard.

I switched from an IBM M13 to a Tex Shinobi with box navy a few months ago. It is not as good as buckling spring, but good enough - and the more compact keyboard, full programmability and the better trackpoint make up for it.

I initially tried Cherry MX Blues, but they’re horrible. Never understood the Cherry hype in the 90s, and still don’t understand it now.

Are you spamming this everywhere now?

On this issue the developers from the very beginning were open to have it added as setting - which is the correct way for this kind of accessibility breaking change. Apart from the last comment the issue just has normal bugtracker discussion.

The code review also has nothing special, and what the author of the pull request calls nitpicking is just a request to adhere to the coding style of the rest of the project - something pretty much any project will ask from you.

You now throwing mud for an issue and pull request very reasonably handled by the maintainers just looks like trying to stir up drama for drams sake.

emacs lisp already lets you use the full range of unicode.