sysadmin

joined 1 year ago
 

Privacy Front-end Nitter:

https://xcancel.com/carlrichell/status/1815498238285562127

https://nitter.privacydev.net/carlrichell/status/1815498238285562127

Extracted from Twitter:

The first alpha release of Pop!_OS 24.04 with COSMIC will be released August 8th.

@jeremy_soller , Maria, and I join the System76 Transmission Log pod to chat about how COSMIC came to be and where it’s headed.

https://system76.transistor.fm/10

 

On their order page, it says "Ships within two weeks"

Cheers!

 

Ever thought, "Why should I care about online privacy? I have nothing to hide." Read this https://www.socialcooling.com/

credit: [deleted] user on Reddit.

original link: https://old.reddit.com/r/privacy/comments/savz9u/i_have_nothing_to_hide_why_should_i_care_about/

u/magicmulder

The main issue isn’t that someone would be interested in you personally but that data mining may put you in categories you don’t want to be in. 99.9% correlation of your „likes“ and follows to those of terror suspects - whoops you’re a terror suspect yourself. You follow heavy metal bands and Harley Davidson? Whoops, you have a 98% likelihood of drinking and smoking, up goes your insurance rate. And so on.

u/Mayayana

Indeed. But most people here seem to have misunderstood your post. One of my favorite examples is from Eric Schmidt, chairman of Google, whoo said in an interview (on youtube) that if you think you have something to hide then maybe you shouldn't be doing what you're doing. (Like maybe the Jews on Kristallnacht shouldn't have been living in their houses?) Schmidt was later reported to have got an apartment in NYC without a doorman, to avoid gossip about his promiscuous lifestyle. :)

u/SandboxedCapybara

I always thought the like "no bathroom door," "no curtains," or "no free speech" arguments always fell flat when talking about privacy. Sure, as people who already care about privacy they make sense, but for people who don't they are just such hollow arguments. I think a better argument is real life issues that people always face. The fact that things like their home address, social security number, face, email, phone number, passwords, their emails and texts, etc could be out there for anyone to see soon or may already be is almost always more concerning for people. People trust companies. People don't trust people.

u/Striking-Implement52

Another good read: https://thenewoil.org/why.html 'I've Got Nothing to Hide' and Other Misunderstandings of Privacy

etc

 

Even after all these years firefox keeps using mozilla hidden directory instead of XDG base directories. For how long will this continue?

Watch https://bugzilla.mozilla.org/show_bug.cgi?id=259356 for updates to this request.

~/.mozilla/firefox/ is a mish-mash of data, config, and cache. It's not simple to unravel that. Beyond that, it would be a breaking change, and that requires more caution.

credit: u/yo_99 on Reddit.

original link: https://old.reddit.com/r/firefox/comments/vkgk78/why_does_firefox_keeps_using_mozilla_directory/

 

Hi everyone, I have just recently found out there is a thing like coreboot/libreboot, and I like the concept of it: fast(er), secure, open source, easy to flash and non-brickable process.

I’ve been trying to understand the basics behind it and it’s too difficult for me. I have some basic understanding of what BIOS / EFI is. And as I understand it, the core/libreboot is an open-source replacement for it. Great!

But what I’m interested in is understanding, how it manages to be better than the OEM’s BIOS? I understand that the nature of open-source is better than closed source software, but what I don’t understand is how this project manages to be better for end-user?

As I get it, it’s similar to Custom ROMs on Android. There is an OEM’s rom — say, Samsung — it makes its version of Android, and it’s good (in terms of how it works with the hardware), but usually with tons of bloatware and OEM never updates the phone after a customer bought it. Here we have Custom ROMs, like CyanogenMod / Lineage OS / Pixel Experience / etc. etc. Those ROMs somehow manage to keep the software updated for much longer time-frame, having extra functionality and even working faster. (Frankly, I don’t understand how do they manage to do that as well, and why it’s so difficult for OEMs.)

Is this something similar? I can understand the (ineffective) processes of big corporations, but I cannot understand how the developers manage to keep those things better, lighter, etc. Say, whether the OEM’s firmwares somehow bloated? Why is so then? Why won’t a big company like Gigabyte, Asus, Acer, etc. also use this product, why do they write so-closed-source BIOSes and EFIs then, if they can use something lighter and faster, and in so many ways better? As it’s advertised on the website of coreboot.

I’m not sure I keep the question simple, for others to understand, but if talking about the real hardware. Say, I have Asus MAXIMUS IV GENE-Z motherboard. Can I install coreboot on it (seems like yes, according to the website https://coreboot.org/status/board-status.html#asus/maximus_iv_gene-z), and if I can, will it miss some functionality comparing to its original EFI? I mean not that I need it, but I’m interested whether there’s something special in original firmware or not. There are many things on the website, at ‘ROG Exclusive Features’ and ‘Special Features’ sections, but I’m not aware if it’s something special or it’s just some marketing bullshit, is it located in the firmware, or it’s something entirely different they speak of in that section?

Please pardon me if the question is too newbish and was answered somewhere. I’ve tried to do my search and found no information on my question. I would appreciate any comment on this topic. Thanks!

edit: Found Why use coreboot? (reddit post) And it’s an interesting read itself, but it’s not the question I’m trying to find answer to.

credit: u/walteweiss on Reddit.

original link: https://www.reddit.com/r/coreboot/comments/bgjzth/how_does_coreboot_manage_to_be_better_than/

[–] sysadmin@lemmy.world 1 points 1 year ago

As a side note about BIOS

Framework’s official stance on Coreboot:

“As this keeps popping up even after multiple responses, let this be the “official” response so we can put this to bed, at least for now.

It is not that Framework “does not care” about Coreboot, it is that we have a very long list of priorities for a very small team (we are less than 50 globally and have existed for less than 3 years) and while being able to support Coreboot would be fantastic, it is just not a priority for Framework right now given the sheer number of initiatives that we have to launch now and in the immediate future. We pivot from one NPI (New Product Introduction) to the next, back to back, and have since our first product launch. Our firmware/BIOS team is small and is supplemented by an outside 3rd Party partner. The consistent, “well, just hire more people then” is unfortunate as those in the know understand that’s not how it works, especially for a small, private company trying to exist in a very mature market segment. While tech in general is shrinking, layoffs are in the news constantly, and global economies are getting hit hard, we’re still here, releasing new products, and working hard to support everything we’ve already launched.

If and when we decide to add Coreboot to the docket of active projects, we’ll let the Community know, but if you want Framework to continue to exist, and you believe in our mission, we’ll have to continue to ask for your patience. If not having Coreboot is a blocker for you, personally, to join the Framework Family, we do hope that we can earn your business in the future.”

https://community.frame.work/t/responded-coreboot-on-the-framework-laptop/791/239

view more: next ›