• 2 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle
  • I have been using Gadgetbridge for several years. The developers are very active, with the nightly branch being released daily. I’ve collaborated with some of them to debug issues and add support for new devices.

    I’ve used it with multiple watches and a scale. While it doesn’t provide insights or interpretations of your data like proprietary apps do, it offers complete control over your data. I’ve been planning to set up a SQLite to InfluxDB/Grafana translation layer to obtain more detailed statistics.




  • Edit: just tried this and it didn’t work. Proton bridge only listens on 127.0.0.1 and doesn’t accept incoming connections due to security concerns.

    If I were in your position, which I am and will probably end up doing this, is vpn into your home network and just connect to the local IP of your bridge server.

    WG tunnel on F droid allows for you to auto connect to your wireguard server when you leave your home net, and auto disconnects when you get back on your home net.

    Personally, I’m unsure if proton bridge listens for external request or if it only accepts requests from localhost? If that’s the case it may be an issue.







  • I also dont like videos for this stuff. Summarized using kagi’s universal summarizer, sharing here:

    • The integration of Rust into the Linux kernel has been a contentious topic, with some long-term maintainers resisting the changes required for memory-safe Rust code.
    • The debate over Rust vs. C in the Linux kernel has taken on “almost religious overtones” in certain areas, reflecting the differing design philosophies and expectations.
    • Linus Torvalds sees the Rust discussion as a positive thing, as it has “livened up some of the discussions” and shows how much people care about the kernel.
    • Not everyone in the kernel community understands everything about the kernel, and specialization is common - some focus on drivers, others on architectures, filesystems, etc. The same is true for Rust and C.
    • Linus does not think the Rust integration is a failure, as it’s still early, and even if it were, that’s how the community learns and improves.
    • The challenge is that Rust’s memory-safe architecture requires changes to the existing infrastructure, which some long-time maintainers, like the DRM subsystem people, are resistant to.
    • The Linux kernel has developed a lot of its own memory safety infrastructure over time for C, which has allowed incremental changes, whereas the Rust changes are more “in your face.”
    • Despite the struggles with Rust integration, Linus believes Linux is so widely used and entrenched that alternative “bottom-up grown-up from the start Rust kernels” are unlikely to displace it.
    • Linus sees the embedded/IoT space as an area where alternative kernels built around different languages like Rust may emerge, but does not see Linux losing its dominance as a general-purpose OS.
    • Overall, Linus views the Rust debate as a positive sign of the community’s passion and an opportunity to learn, even if the integration process is challenging.