bubblesnort

You keep your p..n stash on GitHub???

How does that even work, like, can you mount a GitHub project through fuse and put eCryptfs on top?

Asking for a friend.

If it works, don't fix it.

Shit like this is why I'll always tell people to use free-as-in-freedom software. Most DRM can only live inside blobs. I use Firefox without EME and nothing's broken. Sure, there are legit streaming sites that don't work. I consider those websites "damage" and work around them.

Don't do drugs, just say no. Don't do DRM either, just say no.

Tangent: search for DRM on trains here on HN. Incredible stuffs.

Care to elaborate? I've just looked it up to see if things changed, but all I see is Ritalin / Concerta, Strattera, and Dextroamphetamine. There might be others, but they'd either be off-label or aren't reimbursed by insurance. Where in the world are other meds prescribed and covered?

The meds are basically speed. Epilepsy patients are told never to use speed, but then another doctor can diagnose AD(H)D and prescribe ritalin. I hope these new treatments work well, reduce side effects, and have less chance of interacting with other treatments.

IIRC, Python had a win32 binding over 20 years ago and MS-Office 2000 onwards was scriptable via DCOM.

So with a little bit of effort this has already been a thing for 2 decades.

Not entirely sure how you move from plain win32 to DCOM, and it's probably a bit more difficult than WSH, but it should be doable.

Terminals have supported a bell since terminals existed. The moment I hit tab on an interactive shell and it bleeps, I make sure it never does that again or my SO can't sleep.

The Nokia Lumia was a terrible trainwreck. Microsoft could've done a better job, but they didn't. In hindsight, Nokia had just launched an incredible smartphone with a Debian-based OS and 2 years later they sealed a deal with Microsoft to make MS-Windows the new OS. Pretty good timing for Microsoft to kill off what they really hate. Especially considering that Ballmer was still their CEO at the time and he's known for saying "developers" a lot and calling Linux a cancer.

The thing that made Google evil at that time for me is when they introduced Google+. Before they launched it, you could sign up with fake names and they didn't care. G+ changed that. Nowadays they're making it impossible to register without a valid cell phone number.

The explanation is right there on the page.

I don't think this is going to be an issue as Linux has a built-in rate limiter.

Any SBC with a USB peripheral for the GPS will work.

NOOOOOOooooooo......

This article doesn't explain you need to log out of all Google accounts before factory reset. If that's not possible, you'll have to find an FRP bypass and hope for the best. The e4plus is nearly 7 years old. It'll probably work, but newer devices are increasingly difficult.

And if there's no Google account, you can just skip wifi during initial setup. That way you can setup a firewall first by installing the apk over usb.

A screenful of JavaScript errors? I guess that means 13B EUR is does not compute much.

Crypto requires a good source of random entropy. I suppose if you want more traffic for obscurity, you'll also have to find more random bits. Without enough entropy, you'd sacrifice security for obscurity. Just my ¢2, ymmv, etc

Thank you for clearing that up, OP.

Thing is, can you send any random person a bunch of documents and expect that said person will read them at your whim? In their spare time? I can't afford to XKCD 386 ;)

I wish the both of you well.

There are also very few testers of stable release candidates for such a big project.

Expat

LibreSSL

Linux-PAM

OpenSSH

re2c

tzdata

zlib

Those are just the ones that came to mind.

Basic courtesy such as being honest? You think you're smart because you can copy and paste a bunch of URLs from a search engine or your bookmarks file?

I didn't even ask for a discussion. I think I've made my point clear by now but feel free to keep being a jerk on the Internet.

Kids these days can't live without their tracking device. What happens is they disable all notifications everywhere, enable do-not-disturb, mute all the sounds, etc. And whenever you need to call your teenager for dinner they'll be blissfully unaware of ever having heard their phone ring. Let the microwave fix the situation.

Even when their assignment is on a laptop, the precious handheld entertainment apparatus must be within short range.

Banning this stuff from classrooms is a good start though.

You're free to empty your wallet to the corporation you mentioned, while really it's just pissing into the ocean.

The point I'm making is that software freedom can be hurdled by so-called "security" measures. When a bootloader can reject something you built yourself or a friend on the basis it didn't come from a large corporate software vendor, the computer places more trust in its manufacturer than its owner. This is especially problematic with smartphones and tablets.

There was a time when computers weren't pre-programmed to judge what the user is doing. You could load up any program and it would execute it. You could say this is insecure, but that depends on how you look at the problem. SecureBoot has been proven to be ineffective at securing the boot process, but effective at thwarting attempts to replace MS-Windows with Linux. Apple and Google are even more hostile, with the former openly admitting they isolate their users by calling attempts to bypass their scheme "jailbreaking". It doesn't matter which multi-trillion dollar company is doing it, they're all hostile towards software freedom in my opinion.

Your argument on Intel is just red herring to me. 2 wrongs don't make a right. It's like saying corporate greed is okay because there's always bigger corporate greed out there. Whereas I'm de facto against all moves that hurdle software freedom.

I haven't taken the time to read the documents you linked, but it appears you're making a strong case against supply-chain attacks. For now, I think there's still plenty of room for disagreement much like how computers in military zones can be made deliberately insecure by our petty citizen standards, simply because their threat model is something else entirely.

I don't want blobs because as you allured to, there's a real need to be able to inspect hardware and software for correctness. Any blob that gets in the way of that, I want it gone forever.

Even if you don't do bootloader programming, I think its good practise to build as much as you can yourself. Gentoo happens to be a good fit for this on the GNU/Linux side as you can build everything but also intervene only for those few packages you really want to have fixed a particular way.

On a personal anecdote, the spaghetti code problem has been thorougly fixed. It's been replaced with much worse spaghetti microservices.

You have it backwards. One company holding the keys hurts personal choice for everyone.

And again you conflate software freedom with personal freedom. The needs of any particular piece of software are outlined in its license. My personal choice is to prefer hardware that works fine without non-free software, because I need a different level of trust than you.

Bacon.js already did FRP about 10 years ago.

You're missing the point entirely and brought a plate of red herring to the table.

I could roll keys for my own computer, but freedom 3 falls flat on its face when everyone elses private key is kept secret by one company. People unknowingly trust one company for their "security", while in fact the "security" in this entire scheme boils down to securing stock gain. You can hardly blame the consumers for buying computers that come pre-compromised with vendor-specific keys as the change was touted as "more secure". Secure, again, in the sense that it secures even more money in already deep pockets. Those who can't change their OS or can't easily tick a box on a security checklist will stay on the prerolled platform.

Not being dependant on any one party is an effect of having freedom. Not a prerequisite.

And you conflate software freedom with personal freedom. The four freedoms you call narrow and fundamentalistic, apply to software. You argue no privilege is taken away from me, which is correct, but that also applies to the four software freedoms. I choose not to buy games that don't work on the OS I run. That's personal freedom. The software I write is free on its own to end up on anything from a roll of toilet paper to critical mission control systems. I don't care because it's free as in freedom on its own.

Jitsi is actually one of the better options. My only beef is that it got bloated with features I don't need.

If you enter C:\PROGRA~1 during setup, you end up with Program Files being the only folder in the C: drive.

The downside is that one company holds the keys to the castle for this particular security scheme.

Also, saying freedom requires technical knowledge and fiddling is a non sequitur. Technical knowledge and fiddling is possible with freedoms 1 and 3. Without technical knowledge and fiddling you still benefit from freedoms 0 and 2. Thus, software freedom applies to everyone irrespective of skill level.

I have no idea why having freedom would not include running Gentoo.

Gentoo, as a matter of fact, offers lots of freedom. Its package manager has built-in capability to distinguish licenses. You can choose between systemd or openrc. Musl or glibc. You can disable all sorts of configure options you don't want or need. You can use it stand-alone or inside another distro. You can specify cpu flags for the compiler globally and per package. You can drop in your own patches for any package (and yes, I use that too). You can more easily modify just about anything in the entire system than most distros.

Using Gentoo lets you build a useful system for whatever you do, from sources or binaries, tailored to your needs, without the burden of having to learn all of the different build systems, their dependencies, and weird quirks you'll come across as a package maintainer of any distro. Ever looked at the rpmspec of things you use? Or the patches in a Debian source package? Those details are all taken care of, but with portage still customizable on a high level.

A crumb of weed from a used Dutch grinder is still enough for a spliff in the US.

This is of course a slippery slope argument, but not neccesarily wrong: I think systemd is moving a FLOSS operating system towards one that has source but comes in binaries. You get an initrd that's not built by you, tucked in a kernel also not built by you, runs the userspace from an immutable image also not built by you, which can be updated with binary deltas also not built by you, etc...

This makes sense from the perspective of making a kitchen appliance for the home consumer market. It makes no sense at all from the perspective of making a Unix-like operating system with four freedoms from scratch and ensure it stays that way.