@owingst I like octoprint quite a bit. It's nice having a standalone rpi managing my printer w/ a web UI to monitor the print including via the rpi camera. I also use the web-based slicer even though some people these days recommend recent cura instead.
@owingst Ya, so it's easy to add things like hostapd after the fact.
@ajmartinez Hmm then it sounds like there may not be all that much room for further optimizations there. That matters less on, say, a Librem 14, but would have more of an impact on battery life on the Librem 5 I would *think* but I suppose I could test just how much of an impact.
Since that article was written there's been additional research on using other sensors (ambient light, gyroscope, etc) for tracking, which is why we implemented lockdown mode in the Librem 5 so you have an option to turn it all off.
This guide from Grugq is a great overview for phone privacy and applies even if you have a phone with hardware kill switches for the modem, or a user-swappable modem like in the Librem 5. While those things might make certain steps easier, you still have to keep all the correlation in mind.
https://grugq.github.io/blog/2014/02/10/a-fistful-of-surveillance/
Social media's stranglehold comes from lock-in, not network effects (network effects can be reversed with #interoperability. The important thing about a walled garden is the height of the walls, not the number of people locked inside them: https://www.wired.co.uk/article/social-media-competitive-compatibility
@unl0ckd I thought it was dead too, but I looked at it again recently and it turns out development has picked up: https://github.com/evilsocket/opensnitch/releases/
In case anyone wants to try out receiving MMS messages on their #librem5 I just wrote down the steps needed for that here, still unofficial and hacky but it does work: https://source.puri.sm/Librem5/chatty/-/issues/30#note_151962 #GNU #Linux #ModemManager #libqmi #mmsd #chatty #freesoftware
@koherecoWatchdog @eliasr All your points make sense to me. For what it's worth I'm not angry, just a bit surprised, so it's more just a case of trying to fix this for the future at this point.
@koherecoWatchdog @eliasr That's fair. I didn't really have a better word at hand to use for it and "abuse" is too extreme, especially since, as you say, we didn't publish any restrictions or policies. Maybe "unexpected use" ?
To be fair I wasn't just thinking of this case when I wrote that (although I didn't make that clear in my reply) but was also referring to a lot of the gitlab spam that our administrators have had to deal with as well.
@eliasr I totally agree and that was the kind of thing we were going for originally, not expecting (perhaps naively) that it would be abused.
@koherecoWatchdog @aral @lvdd_ @purism @0 By the way I agree that having outside repos like that on source.puri.sm is confusing and I admit that until now I didn't realize we allowed it. I believe this is simply an oversight in permissions we granted people who requested accounts so they could file bugs and contribute to *our* projects.
It's something we are looking to address now because we don't intend source.puri.sm to be an open-access repository ala Github.
@koherecoWatchdog @aral @lvdd_ @purism @0 Thanks for pointing this out. To my knowledge no one who works at Purism is involved in that repo so you should treat that file as the opinions of the owner and not necessarily of Purism.
Like the latest fashion,
Like a spreading disease,
Devs will login all the way to production,
Getting root shells with the greatest of ease.
Pentests staked out your whole network locale,
And if they pop your Jenkins then it's all over pal.
If one dev exploit gets a shell in Linux,
They're gonna bash it up, slash it up, hack it up, prod's not up.
Here comes libadwaita! Read about our plans to make GNOME apps and GTK 4 even better, and about the future of libhandy: https://adrienplazas.com/blog/2021/03/31/introducing-libadwaita.html
Technical author, FOSS advocate, public speaker, Linux security & infrastructure geek, author of The Best of Hack and /: Linux Admin Crash Course, Linux Hardening in Hostile Networks and many other books, ex-Linux Journal columnist.