Comments URL: https://news.ycombinator.com/item?id=47922620

Points: 1

# Comments: 1

The newer model, C3, C6, C5 all have RSIC-V cores which make it a dream to run Rust (basically: rustup target add riscv32imac-unknown-none-elf).

Here is a good introduction: https://kerkour.com/introduction-to-embedded-development-wit...

Comments URL: https://news.ycombinator.com/item?id=46313549

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=44825449

Points: 4

# Comments: 0

But:

- More and more people see ChaCha20 as wasteful (too many rounds)

- Poly1305 is "hard" to implement

- ChaCha12 + BLAKE3 can fulfill all the symmetric cryptography needs (MAC, AEAD, Hash, RNG...), which is untrue of ChaCha20 + Poly1305, therefore simplifying the deployment of secure cryptography

- ChaCha12 + BLAKE3 both scales with the width of SIMD vectors, opening the door to really really fast cryptography on general-purpose hardware, especially with ARM SVE & SVE2

- SIV construction requires to decrypt the entire payload before being able to verify the authentication tag, which can be costly and may lead to DoS attacks due to the asymmetry of the cost of attack / cost of defense

Comments URL: https://news.ycombinator.com/item?id=44594068

Points: 1

# Comments: 0

I've just Open Sourced Markdown Ninja (https://markdown.ninja), a Markdown-first CMS to publish blogs, documentation websites and newsletters. Our motto is simple: focus on what matters, we take care of all the technical details. Websites, Newsletters, privacy-first analytics, SEO optimizations, headless CMS. Everything is built into a single, unified platform.

I've launched a few projects over the years and the first thing I always need to do is to setup a website for the documentation, a blog and a newsletter to keep people updated.

I've *never* been satisfied with the result. Either I needed to setup a complex system from scratch every time with a static site generator, try to find a good-looking and not-so-broken theme, build a CI/CD pipeline and choose a hosting platform that will not bankrupt me if I make a small mistake. And this is before talking about auxiliary services such as analytics, sending emails and SEO optimizations.

Or, we could choose a closed platform, but their web editors are always a nightmare to use, they charge a lot for basic features and always follow the enshitification playbook like Medium with its paywall, Mailchimp that was bought by the evil Intuit or Wordpress' recent meltdown. And anyway they are not a good fit for my offline-first worflow.

That's why I built Markdown Ninja: online publishing has been simplified to its maximum. You can write in your favorite editor and publish with a simple keyboard shortcut, or, commit to git and publish after a review by another team member.

  $ markdown-ninja publish

Why focus on Markdown? Markdown is the most interoperable format ever. You can start writing your draft in your notes app on your phone, continue on your computer in another app and publish from your iPad while sitting in a park. Also, Markdown in simple. In 15 years from now, publishing on Markdown Ninja will be as easy as it is today while all the "rich text editors" used by the cool kids will have collapsed under their own complexity. Also, Markdown is offline-first: you can cut internet during your deep work sessions and turn it back to publish.

Fun fact: while I've been writing Rust almost full-time since around 2019, the codebase is older than that and the project, started as an experiment in Go, have been my "digital garden" since then and grew in the shadows until today. Thus, I've spent a fair amount of time (maybe too much) optimizing the browsing experience of websites. Loading a page is literally faster than the blink of an eye (around 50ms in Europe)! You can try it here: https://kerkour.com

Online publishing always have been a in a weird state of affairs due to the difference of cultures, sensibilities, and lawmakers all around the world, that's why Markdown Ninja is Open Source (https://github.com/bloom42/markdown-ninja): even if we don't like the content that you want to publish, or can't legally host it in our jurisdiction, your are free to use our code and publish it yourself on your own terms, no strings attached. Silencing via deplatforming is real and Open Source is the only solution.

I'd love to get your feedback, insights or questions, here or in the issues on GitHub https://github.com/bloom42/markdown-ninja

Comments URL: https://news.ycombinator.com/item?id=44042144

Points: 16

# Comments: 4

It lets you create a blog and a newsletter with Markdown and publish directly from the command line (or the web editor). You get the offline-first workflow of Markdown, but with beautiful themes like substack.

It's like a mix between Wordpress, netlify and substack.

A Markdown-first CMS and website builder for blogs, newsletters and documentation websites.

I've been blogging since more than 10 years, and the only thing that made it possible is Markdown. That's why I've decided to build a complete publishing platform to replace the complex and fragile setups of bloggers and startups. Do you really need a CI/CD pipeline, static site builder, hosting, CDN and analytics just for a website? :/

The platform is currently 100% operational and I'm now working to Open Source it.

The best thing? You can publish directly from the CLI:

$ mdninja publish

You don't have to do the Big Rewrite™, you can simply migrate components one by one instead.

Comments URL: https://news.ycombinator.com/item?id=43413600

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42805687

Points: 1

# Comments: 0