• 0 Posts
  • 25 Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle
  • So for the PineTime the most popular firmware is https://infinitime.io/ and by default you get

    • Watchfaces for telling the time
    • Steps (displays the number of steps of the day and the daily goal)
    • Heart rate (controls the heart rate sensor and display current heartbeat)
    • Music (control the playback of the music on your phone)

    and the PineTime is relatively slick, large bezel but frequently people told me, surprised if they knew me, they though I had an Apple watch, which was a brilliant moment to open up the discussion about open source, free software, open hardware.

    Meanwhile Watchy has e-ink and the 3D printed frame is very bulky. It’s definitely a lot more noticeable and I received few compliments for it. By default its firmware is https://github.com/sqfmi/Watchy and…

    • time (+ weather if connected to network, not mobile phone, via WiFi not BT)
    • Steps

    … and that’s about it. Honestly the Watchy ecosystem is a lot less lively than InfiniTime. Sure you get some different watchfaces but that’s about it in terms of popular customization AFAICT. Basically I’d only recommend it if you only want a watch for time and if you are adamant about e-ink.


  • Linux on desktop, self-hosting and GrapheneOS too.

    I have a few smart watches, namely PineTime and Watchy by SQFMI but… honestly I don’t wear them anymore simply because I try to be as minimalist as possible. In fact just yesterday afternoon I was wondering if I could do without GrapheneOS because I might actually NOT need a phone.

    So… what do you want out of watch?

    I can recommend both but honestly it depends on your need.




  • you shouldn’t run software that accesses such intricate personal information if you don’t trust it, if it can be updated to change to grab all that data.

    Yes, and you should also brush and floss your teeth, do physical activities, buy local produces, recycle everything, do your due diligence on all political candidates, etc, etc. In practice we ALL have to make pragmatic choices. There are not a lot of browsers and basically for fully featured engines there are (arguably) only 2, Chromium by Google and Firefox by Mozilla. One is an advertising for profit company, the other is not. If you genuinely care a lot about privacy though you might not have to use either, you might be perfectly fine with much simpler browsers like Links or even lynx and I can tell you with a lot greater confidence that there no data will leak. You can also containerize your browser using e.g. https://docs.linuxserver.io/images/docker-webtop/ and then run within there whatever you want.

    since Mozilla seems to potentially give itself a license to all your data, apparently.

    That’s not correct, you mean some data from your browser usage. I think it’s important to be precise here otherwise through shortcuts you try to convince yourself, and others, about a problematic situation that just does not exist.

    So which browser do YOU trust and why?


    • Install anyway
    • daily drive
    • do a SeedVault backup on a USB stick

    then optionally, after a short while if you are convinced

    • buy a 2nd hand Pixel 8 (cheapest with longest support) or whatever match your preferences, maybe by then even a Motorola with official support
    • bring your SeedVault backup back to the new device including, contacts, apps and data

    No matter what you do you will be “left behind” but at least you have time to learn something useful in the meantime then reassess.




  • I haven’t but I did built relatively large projects before (e.g. browsers) and basically it depends mostly on 2 things :

    • are you in rush? If not just let it run over night, if you are then delegate it (if you can afford it and matches your threat model) to a cloud provider (rent a couple of instances for however long you need, that’s where the hourly pricing matters)
    • is the build system properly setup for reproducibility, e.g runs in a single container on AMD64? if so just start it and move on, otherwise be prepared for an indefinite amount of tinkering

    I think it’s interesting to do but honestly as someone else mentioned, builds are signed. In fact at the end of https://grapheneos.org/install/web#verified-boot-key-hash you get the verified boot hash. The goal is precisely to check that you actually get what you are supposed to have running. Basically the big picture of reproducible builds is that you do NOT have to do it and can STILL verify that you have exactly, up to a single bit, what should have.


  • Be mindful that such a program would have to be safer than the situation without. A program on a public repository that isn’t used by any distribution, isn’t audited, hasn’t a lot of comments (and thus eyes on its code) might be a disproportionate risk compared to the default settings of a popular open source distribution IMHO.



  • It doesn’t have to be though. It could be BOTH convenient AND private. It’s only because we, as a society, didn’t fully understand the “cost” of “free”. We thought it was just so nice to get a good search engine without having to pay. We didn’t grasp that it was the beginning of surveillance capitalism. We didn’t understand that this business model would be so successful every company, from news ones like Meta, to “old” ones like Microsoft or Amazon, would try to be hybrids, both selling stuff and but also re-selling data to advertisers.

    So no it’s not a false choice, it’s a corner we strategically got pushed into.

    I believe, maybe naively, that initiatives like https://uattest.net/ or even https://www.taler.net/ are trying to show that it can be both convenient and private, but NOT while relying on surveillance capitalism which is precisely investing a lot of money to bring the maximum convenience, including free (hard to beat) but at the cost of privacy.

    Edit: seems GrapheneOS isn’t into UAttest initiative https://grapheneos.social/@GrapheneOS/116200110686604617 but I’m not sure what alternative they propose.





  • I think that’s precisely what this is questioning : is this helping fund critical FOSS?

    What if a fraction of that money instead went to Signal infrastructure? Wikimedia? FSF which initially made GNU PG? FSFE? NLNet which supports Delta Chat? Sovereign Tech Fund? etc rather than individuals?

    I don’t think anybody is criticizing that hard working people contributing to a good project are well paid. I believe the question is rather what’s the cost to OTHER projects when there is 1 project, not an umbrella projects which funds others (again like NLNet or the Sovereign Tech Fund).

    What model are we reproducing and what’s the risk?

    FWIW the question isn’t new. It happens also with Mozilla with the compensation of its C-suite staff, not the “random” software engineer.