printf VS elk

https://github.com/mpaland/printf i think this would work

Seems unlikely. My spot check of the the two vfprintf implementations shows no flow from one to the other, and shows that part of the Cosmopolitan code has an older lineage than nolibc.

The nolibc source has many reference to copyright held by "Willy Tarreau", under LGPL-2.1 OR MIT license, with a copyright date starting in 2017.

The string "Tarreau" does not exist in the Cosmopolitan library, so that's a strong negative there. Let's look closer.

The file organization is quite different. And so is the implementation. So that's another negative.

Compare the vfprintf in nolibc at https://elixir.bootlin.com/linux/v6.2-rc4/source/tools/inclu... (a 'minimal vfprintf()') with the one in cosmopolitan starting at https://github.com/jart/cosmopolitan/blob/master/libc/stdio/....

Right away we can see nolibc places many functions in the same file while Cosmopolitan uses a one-function-per-filename organization.

Cosmopolitan's fvprintf locks the file (which nolibc doesn't need to do) then calls vfprintf_unlocked which calls __fmt at https://github.com/jart/cosmopolitan/blob/master/libc/fmt/fm... , which is the actual implementation. It look very different from NOLIBC's.

Okay, so perhaps that's they way now but not at the beginning?

We can also go back to Cosmopolitan's original implementation and see how vfprintf goes through https://github.com/jart/cosmopolitan/blob/c91b3c50068224929c... to call "palandprintf", which https://github.com/jart/cosmopolitan/blob/c91b3c50068224929c... says is copyright "Marco Paland" from 2014-2019.

That's a few years older than the start of nolibc, available from https://github.com/mpaland/printf , and part of https://github.com/embeddedartistry/libc , a "libc targeted for embedded systems usage".

Thus, multiple factors seem to agree that nolibc code is not used in the Cosmopolitan library.

I wrap this C implementation in a C++ Logger class and use it to "print" into a simple buffer. Then the static buffer is periodically unrolled into a transport layer using a static Logger::transmit() function in my BSP. I'm working with very little flash, so the linked implementation is essential.

There are many good and tiny printf's fir embedded on GitHub. https://github.com/mpaland/printf eg Better than the bsd printf mostly

I'm sure sprintf itself is working in their library, so try to find other issues first, BUT, as a last resort you can try another lib: https://github.com/mpaland/printf/

looked at that account, found this one too

This has lead to a delightful variety of custom clients like https://phanpy.social/ - https://elk.zone/ is another example that I really like.

It's the complete opposite of the Twitter API situation, where they locked their API down and killed the entire ecosystem of third-party clients.

And there are tons of third party clients. I think Tusky is the best one I’ve seen for Android, and there’s an interesting web-based one called Elk that’s very nice. You load up https://elk.zone and then use it as a front-end to sign in to your server.

The answer to that is https://elk.zone atm, a fun and chef's kiss interface (built with nuxt). You can insert elk.zone/ before any Mastodon url. https://phanpy.social is also great, with multi columns even for lists.

A browser plugin (like "Mastodon – Simplified Federation") to follow, favorite, etc. directly on any server has also improved my experience a lot.

Quick! Tell Obama and Taylor Swift about https://elk.zone! They're going to be so excited!

Also try logging in through https://elk.zone/ if you want to stick with the familiar twitter interface

For me, the boost/reply-numbers using https://elk.zone have been much more reliable than the original app. (It's also the (web)app that convinced me. Mastodon is the real deal.)

Try elk.zone. You can log into the UI with an account from any instance. I use it as my main UI and it looks pretty close to twitter, at least close enough for me.