• 0 Posts
  • 29 Comments
Joined 6 months ago
cake
Cake day: June 5th, 2025

help-circle


  • Just the heads up, that cpu is ancient. Its performance is comparable to an Rpi 4, but that old cpu consumes 30W+ while a full rpi maxes around 6-7 W. Rpi 5 is around 4-5 times more powerful with third power.

    So it’s good if you just tinkering with old hardware for fun, but you can buy far more powerful modern hardware for only several dollars if you look at the second hand market.

    Also I remember, I dealt with Toshibas from that era, they were quite locked down, e.g. you couldn’t install upstream nvidia drivers on them only the outdated ones signed by Toshiba. So it’s not unexpected that some options like that are missing in bios settings.




  • Wtf man, developers are also people. Most of them doing this for free in their free time. You are the kind of entitled user who makes foss devs burn out. Never thought I will find one in the wild.

    I use krita frequently and never met your bug so it’s not as recreatable or important as you think.

    Noone forces you to use krita. If it doesn’t fit your workflow or if you think developers are deliberately sabotaging your work, you can switch to another free or paid alternative. If you would switch to a paid one, you could speak to a manager.

    In op’s case I’m not sure it’s a you problem. In your case I’m sure it is.









  • There is a history dashboard where you can change the date and which sensors you want to display: https://www.home-assistant.io/integrations/history/ You don’t zoom but you have to add dates, same 2 sensors look like this there:

    But it depends on the sensor if it supports this long term statistics, by default all data is saved only for 10 days, you can change these settings.

    If filtering and zooming is the most important aspect for you this may be not the best solution, as this graph displays are not the best. The most powerful feature is that you can add local data sources.





  • CoMaps has far less features, but that’s the point. Some people love the simplicity, they don’t need all the confusing and overwhelming options of osmand.

    Osmand has some performance issues on some devices, but Comaps was generally much more responsive on any device I tried it.

    CoMaps has 3d buildings. Its map is very nice, but this is subjective.

    CoMaps aims to be fully FOSS, this was not true for its predecessors, OM and Maps.me. Osmand is not fully foss.

    If you are perfectly happy with osmand you don’t really need it, but for new users who are only familiar with the very basic interfaces of other commercial map apps, it can be much more welcoming.


  • The full story is in the Open Letter, but it’s long: https://openletter.earth/open-letter-to-organic-maps-shareholders-a0bf770c

    AI summary from this comment from the osm forum:

    Concrete Issues Leading to the Open Letter

    • Misuse of Donations: Alexander Borsuk allegedly used project donations to cover personal holiday expenses, raising concerns about financial integrity.
    • Lack of Financial Transparency: Contributors were consistently denied access to financial information, including total donations received and expenditures.
    • Secret Hiring Practices: The hiring of the first full-time developer in January 2024 was kept secret from contributors, who only learned about it months later.
    • Closed Decision-Making: Key project decisions, such as agreements with external partners (e.g., Kayak.com), were made without informing or consulting contributors.
    • Shareholder Control: The governance structure allowed shareholders to make unilateral decisions, sidelining the input of long-term contributors.
    • Conflict Among Shareholders: A significant conflict between shareholders Roman Tsisyk and Alexander Borsuk has led to a breakdown in collaboration, jeopardizing project stability.
    • Lack of Accountability: The board, composed solely of shareholders, failed to rotate members or ensure accountability, leading to a stagnant governance model.
    • Potential for Profit Motives: Contributors expressed concerns that the project could be sold or monetized for shareholder profit, undermining its community-driven mission.
    • Inadequate Communication: Shareholders did not adequately communicate the role of Organic Maps OÜ as a for-profit entity, leaving contributors unaware of its implications.
    • Violation of Open Source Values: While the maps generator code is technically available, the version in production contains private changes that are not disclosed, and the server used for downloading maps operates with proprietary elements, contradicting the project’s stated commitment to Free and Open Source Software principles.