devdiary

No thanks

The original Raspberry announcement about Raspberry Pi Connect

> All devices get remote shell out-of-the-box, and if you use a Wayland compositor, such as Wayfire, you can also share your screen. In practice, this means you can use screen sharing with Raspberry Pi 4 and later models, and remote shell with all models of Raspberry Pi, even the oldest.

Now I have another task to purge this out of my pi.

And how do you measure the api latency? Any do's and dont's you have learned related to this metrics?

> at the end of the day prompts are just a API call and it's easier to write standard code that treats LLM calls as a flaky API call

They are also dull (higher latency for same resources) APIs if you're self-hosting LLM. Special attention needed to plan the capacity.

Do not understand your comment. What are you trying to say?

thank you for sharing the archive link. Didn't know it is possible to archive a non-public/paywalled content.

How come a paywalled content gets to the top of the HN front-page?

Can you ELI5, how did you make this possible? I see the readme asking to download a binary and then also mentioning sqlite extension. I have never had exp with sqlite ext, so not quite sure how do they work. Appreciate how does this solution work under the hood.

Thank you for writing this

I use the similar kind of structure in Developer Diary. I do it completely offline, no sync.

And yes, specifically talking about plugin based architecture. Not just a code refactor. Decoupling is the first step and the plugins will be created by internal team initially, the next will be to ensure security when external users publish their own plugins. The tech stack is Node.js.