That would always by definition block all third parties.
Think of the reddit example from the person you replied to: there was a huge outcry when reddit announced shutting down their lower API tiers.
Either information is free to flow or not at all, there is no middle ground.
With that in mind: I’m sure they thought about it and decided to prioritize transparency she flexibility over security. Personally I support that decision.
One thing that was only mentioned briefly by someone else is the physical button turning on the computer.
Similar to the paperclip test figure out where the power button goes into the mainboardw and bridge that with a short cable. Is possible that by moving the case the old button lost a cable.
This is just one more thing to test though, it’s really trial and error as you know :)
From what I understand: CasaOS is simply an abstraction layer and takes away a lot of the manual work.
I agree with you that this shows down learning quite a bit.
I see three ways forward for you:
a) switch to a Linux base system, Debian, arch, nixos, whatever resonates and set up everything from scratch. High learning curve but no more hidden things.
b) same as a but as a separate setup. This is what I would recommend if you have the time and cash. Replicate what’s already working and compare.
c) figure out how to do things manually within the CasaOS framework. Can’t help you there though :)
Not Op here, from what I’ve read is that the answer to that question is unknown but he showed a significant tolerance for some. Does that make it himself fine? In my book: yes.
For me personally it was enoughto leave the project behind as it’s so closely tied to the person.
That’s a call everyone needs to do for themselves though if course
I don’t hate that much but I don’t watch him because of the shady selling business hr often does and apparent sponsored content which is not always disclosed (been a while but his channel misrepresented graphics cards benchmarks for example).
It’s like the British yellow press for me: his face alone is enough to discredit the quality of the source. Could it be good? Sure! Will I ever find out? Not anymore.
Wow thanks a lot for that!
At least in Germany it’s the same. It gets ignored in the discussions concerning nuclear exit but it’s actually the main reason why I’m not aggressively against it: we have save areas for nuclear storage but those fight bitterly to not have it. The areas which are currently used are… Not good. Paying someone else (such as Finland) is out of budget for both state and energy companies. The latter anyway want to do the running but not the maintenance and the building, state should pay for that.
It’s really white sad for me. The (true) statement that the dangerous waste needs to be stored carefully got corrupted to “it can’t be stored”.
Oh sorry, nvidia RTX :) Thanks!
Lowest price on Ebay for me is 290 Euro :/ The p100 are 200 each though.
Do you happen to know if I could mix a 3700 with a p100?
And thanks for the tips!
And still there are other people than you who want to do that full-time - and in doing so provide, at least for me, more value than the 6ooth marvel billion dollar movie.
There are educators and entertainers out there who chose this as a job and are good at it. If they could live off of it by going the patreon route instead of the shitty YouTube ad spam one I’d be all for it.
If that’s your intend than it might be better to pick individual arch wiki pages or improve the entry documentation. Many people refer to there from all distro because of its volume.
A “how to read tech documentation” could add value for this target group.
User perspective:
If you want something big I’d pitch nixos. As in the core distribution. It’s a documentation nightmare and as a user I had to go over options search and then trying to figure out what they mean more often than I found a comprehensive documentation.
That would be half writing and half coordinating writers though I suspect.
Another great project with mixed quality documentation is openhab. It fits the bill of more backend heavy side and the devs are very open in my experience. I see it actually as superior in its core concepts to the way more popular home assistant in every aspect except documentation!
That said: thanks for putting the effort in! ♥
Which of those questions from the article would you describe as loaded enough to imply the quite interesting responses?
I expected to read something like “why are Chinese people stupid?” and then some racist shit - but the answers to those questions are… Interesting.
The bankruptcy scenario is correct but the first part isn’t: you don’t have X shares as collateral that you can liquidate. Instead, you have collateral to cover sum Y.
As long as the collateral contract covers enough stock positions the bank won’t lose.
That said all of this is assuming standard contracts. If y bank wrote “0% interest and instead 50% of the revenue growth of Twitter” then this would be an easy way to lose money.
Haven’t heard of a stupid banker yet, though, so what would the chances be?
Ah that would make sense, thanks!
I haven’t found (while cross reading ) details about why the “highly improved” didn’t make it to upstream openwrt?
Because it’s basically axiomatic: ssh uses all keys it knows about. The system can’t tell you why it’s not using something it doesn’t know it should be able to use. You can give a -i for the certificate to check if it doesn’t know it because the content is broken or the location.
That said: this doesn’t make -v more useful for cases like this, just because there’s a reason!
Both langchain as well as ollama run locally and are open source.
To be very frank: your post sounds like fear mongering without having even clicked on the link.
Edit: I missed some complexity as suspected! I’m not sure how this process would handle hard and symlinks. Would add an experiment for that before going with the nix and root folders (it shouldn’t harm log at all).
Original text: Perhaps I’m missing some complexity in your setup but from my understanding it’s really straight forward:
The main caveat is that you need twice the space of your largest future sub volume. A garbage collect - d and any manual cleanup can help you there. I’d gets that approach with /var/log and when that works move over to the more critical systems.
If everything is working as expected, write a run book for every step and repeat with /home (i.e. have every step written up). Home is the second least critical folder for this.
Once you have your runbook repeat the process and when you run out of space resize as needed. (e.g. https://btrfs.readthedocs.io/en/latest/btrfs-filesystem.html#man-filesystem-resize)
That said: as you aim for the fully ephemeral root I personally would actually go the reibstwllwtion/reinstall route and write up everything I needed to do by hand. But that needs even more spare space (I’d prefer even a second disk for stuff like that to have a fallback).
Good luck!
Seems like a historic artefact to me as well. And one of their mentioned points was “no sync via http” which even for 2006 makes me… hesitant.
And their history section ends in 2007, couldn’t find a feature comparison in their quick start guide.