Professional C# .NET developer, React and TypeScript hobbyist, proud Linux user, Godot enthusiast!

https://blog.fabioiotti.com/\ https://github.com/bruce965

  • 2 Posts
  • 137 Comments
Joined 5 years ago
cake
Cake day: March 9th, 2022

help-circle
  • It depends on your goal. Considering that you seem to be on a web development path, perhaps the next step could be a frameworks such as React or Angular (my preference: React).

    You might also want to look into TypeScript. It should be relatively easy to learn if you already know JavaScript, considering that TypeScript is a superset of JavaScript.

    Obviously you also need to at least understand CSS, but that will come with time. I would say there is no hurry.












  • (Personal opinion not based on scientific evidence.)

    I would say that’s not possible for a hobbyist. The main issues with this kind of DIY phones are performance, compatibility with existing software, and most importantly battery life.

    The Raspberry Pi was never designed to be used with a small battery while still staying connected to the internet to receive notifications all the time, like a smartphone. If you want to build a usable smartphone you will need an efficient co-processor to do these tasks. This could get complicated fast unless you use a CPU designed for this job.

    There has been some interesting progress with desktop environments and small touch screens. Still nothing as good as Android, but nice UI is no longer the main issue imho.

    As for compatibility, good luck running Signal, Matrix and Thunderbird in the background without draining the battery.

    That being said, if you are just doing it as an excercise without expecting to build a device that will replace your main phone, you can definitely give it a try. Have fun and learn much!



  • Sorry, not an answer to your exact question… Dockge might be the answer if you need a web UI to manage Docker containers.

    If you need something more specific, like a button dashboard to run custom commands, perhaps you could build your own with Vite (Node.js). You will need to understand basic HTML, CSS and JavaScript. (EDIT: OliveTin makes more sense.)

    As for authentication, you could configure a basic authentication on your favourite reverse proxy (such as Nginx), or look for something more advanced such as OIDC/OAuth2 through Keycloak.



  • As far as I understand, audio cards hold a buffer of the audio that should be played at any time. If the CPU can’t keep up producing new audio, it will loop to the beginning of the buffer. My guess is that when you suspend, the CPU stops producing new data before the audio card stops consuming it. And that’s why you hear the last part for a short instant.

    It also happens on my devices, and it’s always happened on all my previous devices as far as I can remember.

    Disclaimer: this is based on my understanding + a lot of suppositions. It might not be accurate.



  • I do have an opinion about Ecosia, but it’s just based on feelings, so it doesn’t even make sense to share it. Apologies for not answering your question.

    Instead I would like to focus on this point:

    Ecosia isn’t very private, since it sends data to Bing

    Also DuckDuckGo does this, but they aggregate and anonymize that data before forwarding it to Bing. That’s probably the best they can do without building their own first-party infrastructure. I would imagine Ecosia does the same.