stoplying1

Oh, oh dear. Um, that was sarcasm. I clearly don't think people should be looking for get rich schemes, on yt or otherwise. It was aimed at the people that think day trading, lottery tickets, or otherwise longshots are a logical response to a hostile market.

Its hard to think of any scam that isn't portrayed as "working out (for the (would be) rich)". Again, a good reason to be wary of such things.

I'm totally in favor of helping struggling folks, taking care of basic needs, etc (though I'm not sure laundered money is the culprit I'd offer). But lord maybe some reasoning skills would also do some wonders. Also, Christ, it pains me how often I think "if only I could sleep with myself stealing money from fools". Because I do know you're right, that's the psychology of why get rich schemes work...

Uhm, yeah, people made the wrong bet because they fell for another hyped up tech company.

But let's put a fine point on it -- that specifically fell in with a rent-seeking company capitalizing on a decentralizaed space with a centralized platform and then surprise-pikachu'd when they did the same thing as every one before them.

> because when it's not on an exchange you can't convert it back into USD when significant market moving events take place.

Weew, well, idk, if y'all know this, and I'll take the karma hit, but the rest of us that know better than to day trade mostly roll their eyes at this ... crap. And if you WERE "day trading" and didn't manage to pull out, well, maybe day trading isn't in your cards. Go watch YT for a few hours and I'm sure youll be on to your next get rich scheme.

I don't get it, other than the Apple-y-ness of it all? Maybe that's not important but ... ?

Every single thing I own and need to function on a daily basis (other than my immersion water boiler for otg-espresso) operates on USB. Preferably type-c, but plenty of things still need a USB-A-to-C in the mix because resistors are hard, I guess.

Also, open hardware hackers,, my trimmer and touthbrush are basically internally identical. An we please make these inter hangeable?

Using a "thin-client" laptop with cheap default -cafe alliances d chesap ones means I can live out of a bag, using redundant chargers - either a tiny 45w charger that literally fits in my bu^H^H pocket, or charge my laptop, phone and Ledger using a 100W charger that is barely more than double the physical-size of the smaller charger.

`please` in fact does exist. NixOS even has a module for it. ;)

https://github.com/edneville/please

Well, no, you don't chain-load Windows from grub either because then PCR are wrong and Bit Locker rightly complains.

Which is why you... Just use the system boot manager to pick which loader to load. Easy, problem solved.

And you can edit the system boot manager entries from Linux and Windows, set bootnext from either one. It's really strictly superior to what you're describing.

Yeah I don't get how Linux is running on the Thinkpad and openbsd was able to boot but a device trees is the blocker for Linux? Are they just on some distro that doesn't have the new kernel packaged?

Oh, it's because of "APCI" mode working with openbsd apparently...

"Password Store" ('pass' compatible) for Android also supports TOTP to tokens and Gpg encryption.

With Syncthing, 'gopass' and 'Android Password Store', I have a fully open source, very easy to reason about fully in my control, password and totp storage, accessible on all my devices. All of which can only be accessed with my Yubikey that I keep in my pocket and my GPG PIN.

I love that the CSS is basically identical. I'm very curious to see if this takes off. It feels like this has been missing for a while.

I really wanted to see something like this for Matrix but despite seeing some functional prototypes, it doesn't seem like anyone stuck with it...

I think you'd be shocked how much of my NixOS system not only natively compiles for my Vision Five but also cross compiles to it... (and Nixpkgs cross compiling support has room to improve, so..)

Obviously a monorepo of largely FOSS is easier to deal with than random Android apps but I don't think it's that dire or insurmountable.

Signs so far point to a big fat no (as someone running a custom uboot build on visionfive that works better than the bsp from manufacturer). Plenty of blobs, still device trees, etc.

Some humans, maybe.

Lol so what happens if I run 'curl' in my PS6 script? Asking for a friend with PTSD.

I just ported a bunch of scripts to nushell.

I hit some bugs, a couple of which are a bit sharp, but wow, the list of quirks I have to remember for nutshell are so much fewer than for bash.

Constantly impressed at the errors it catches at parse time, kinda crazy sometimes.

Oh my god I could cry, strings are sane to work with. I may never write a bash script again (it's okay, I use Nix so I get nushell everywhere I'm might need it, for free)

Everyone is asking about PowerShell. I never hated it, but lord it makes some awful, stupid infuriating decisions. I've lost hair and sanity to some stupid list/single-item-list beahvior. Numerous operators and bits of syntax are just different. Everything about the script syntax is just slight odd and confusing. There's basically none of this with nushell. Jonathan Turner is a gifted person with an eye for language design and it really shows.

Edit: I do think it's missing some important output redirection functionality. You can workaround by using "complete" but that feels non-ideal.

(doesn't list or use the package manager most likely to already be reproducibile)

So, even though it's a convention, and a supported action, it's taboo for them to yank.

Meanwhile, it's apparently such a sin because of people... That don't bother to lock their deps with a Cargo.lock? And that's not breaking an important convention?

"I'm good at DevOps and everyone else should be too", feels tangential, and isn't going to help you when your banking session gets compromised because your bank wasn't prepared to roll this out through any expedited process versus their regulatory compliant, slow process.

(As an example/thought experiment. I make no claims about the vulnerability at hand.)

The discussion was a way of replicating or distributing a filesystem structures, there's absolutely no requirement anywhere that individual files in that FS are directly addressable via IPNS. And yes, it's simple because there are countless implementations of chunking deduping CID systems. Basically none of which have that artificially created requirement. MANY of which ARE ALREADY BUILT ON IPFS AND IPNS and work exactly the way I describe.

Also, again, its like I mentioned it for a reason, see Git, where in fact, there isn't a nameable identity per-file, per-commit, and yet, there's a revisioned filesystem abstraction built on top! That works perfectly fine with pointers to CID content that points to other CID content.

It's almost exactly what is being discussed at hand.

Shame away buddy. Btw I've contributed code to more than one Content Addressable chunking deduping filesystem projects, because they're the future of file sync, and frankly now that Iroh is here, we're likely to start realizing these things in a "final" ish from.

Oh and the other commenter saying the exact same thing as me ;).

Am I the only one completely bewildered by this comment? Putin seems like Not A Great Guy TM, but did I miss some expose?

Note to self, host more stuff on duckdns.

I can't stand the amount that folks bend over backwards to accommodate lazy, inconsiderate middle men.

Read my think piece on my ad/pop-up riddled Medium/Substack blog!

Not a BSD guy but given what I understand this struck me as a weird comment.

https://github.com/systemd/systemd/issues/18733 you sure it's not supported?

And? Not sure what I'm supposed to take from this. Domains can be had for so cheap, the fact that it's even a consideration in the spam profile is kinda... :/.

Wow, thanks for a reminder as to why I'd literally never use Facebook Messenger.

Somethings are actually indeed worth the friction-full conversations of "no, sorry please use (anything else) to chat with me".

Er, it's not that hard. Think about git repos, they have refs that point to a tip that you traverse. This would work the same way.

And in fact CID and chunking is what makes this possible...

Ipfs is in fact ripe and perfect for some of these sorts of things and I highly suspect we're going to see more innovation in this space, in applications that are actually pushing the envelope, now that there's a sold rust impl

Holy thank god. These things deserve to be written in Rust (see also, matrix-rust-sdk and the entire ecosystem rebasing on it). And ipfs-go and the existing ipfs ecosystem, I'm just so disappointed. They've had so much money floating around, so many filecoin adjacent projects with ipfs-adjacent insiders and yet so much low hanging fruit that seems unrealized or locked up in poc nodejs projects.

This is probably the single best thing to happen for ipfs in 3+ years. Bravo, I actually have hope in ipfs again.

The messaging on the site makes me think I'm not alone in feeling this, and that excites me even more.

Smart guy though, he walked it back just in time. I'm sure he'll point to that tweet, and it's timing, whenever his legal counsel eventually tells him that, yes, very much so they need to ban certain folks. And like most of the time when playing to (that particular crowd), it won't matter when his hypocrisy (or pandering) is exposed.

I've worked with people who are that old in the industry and they don't use those terms.

Elon is projecting here. Big time. I feel like I can just see the impotent self-victimization and glorification between the lines. And walking in with a sink and Tesla engineers to "review Twitters code". Better watch my tongue, but l-o-l.

Well that one got a physical cringe from me! Whew, what to even say to that.

Great, thats cool. I'm concerned about accessibility to general computing too. But this article is about an optional feature in an FOSS software that is only as good or bad as the distro using it.

Please, you must understand, you devalue your point by demonstrating that you either don't understand the layering at play here, and where the real risks are, or you don't care to advocate in any sort of meaningful or compelling way. Instead, you just repeated FUD and waved your arms more. Again, about something we probably agree about, but is simply not at hand here.

I mean the issue that you're worried about? How about the millions of capable smartphones being tossed because of closed bootloaders? Android manufacturers, Google's Nest and Chromecast products, and Apple's iOS devices here are far greater offenders. And just more insidious. My 3 year old phone that works damn fine is considered literal garbage by Google (no security updates, means I use Lineage, means I can't bank, watch Netflix, use credit card apps, and more). Microsoft has never used security features to invalidate my old hardware. Ever.

Again, totally tangential from whether or not SystemD has first-rate support for this (mostly because at this point it's about UX and distro mechanics such that users and distros can freely secure their computers. The functionality to just lock-er-down has been here. For a decade). This issue is about capitalism, economic incentives, social politics, etc. But, I don't expect that conversation to play out on this site much.

Finally, Pixel and Chromebook prove that secure computing AND user freedom CAN be respected and can be user-empowering. Please, if you care, advocate for their models. (Which, again, I can also do on all x86 Microsoft devices and Microsoft Surface ARM, at least, today).

Smh, the FUD is suffocating in here. And really, a round of applause for everyone butting into say they don't need this. Do you have a habit of doing this for all features?

Sorry, but I expect my Linux install to be at least as secure as my Windows (Pro) installation. And without this, it's not. It's that simple. In years, most of you will be benefiting from this, it will become table stakes and the FUD will subside.

It's hard to really read this thread. If you care about user freedom, this sure ain't got nothing to do with it. Other than giving me the freedom to have a more secure computer.

Just sad to see the FUD cause people to just get so activated without even understanding the stakes at hand. (Think. It's not like MS is watching this feature to decide whether or not to allow user-key-enrollment on the ARM Surface).

Except that would've been too easy to understand, and instead seems like they're using wasmedge anyway. Needlessly confusing, why do companies do this?