You don't necessarily need coding skills to "audit", you can get q sense of the general state of things by simply reading the docs.
The docs are a good starting point to understand if there will be any issues from weird licensing, whether the author cares enough to keep the project going, etc. Also serious, repeated or chronic issues should be noted in the docs if its something the author cares about.
And remember, even if you do have a background in the coding language, the project might not be built in a style you like or agree with.
I'm pretty proficient at bash scripting, and I found the proxmox helper scripts a spaghetti mess of interdependent scripts that were simply a nightmare to follow for any particular install.
I think the overall message is do your best within your abilities.
In BC it is dealt with swiftly and with heft: immediate 10k fine (up to $100k), you are on the hook for expenses caused by the drone interference, and you have to go defend yourself against spending a year in jail.
Have you tried koreader? I have an old Kobo on which I actually used pocket, but I'm reluctant to try koreader again because I tried it a few years back and it was not a pleasant experience.
Sorry, I meant "Plex took away free remote streaming".
You're being really, really snippy. Either have a coffee or take a breather, but calling strangers liars is way offside.
I'm not lying, I can show you my Fw config. My son called me yesterday saying he couldn't watch Plex, something about the Plex pass. I just changed the Fw rule DST nat mangle port and told him to use jellyfin. The user is local, so that's dead easy. Done in 10 minutes.
And yes, most users don't have this kind of experience, granted. But Plex comes with its own stupidities, like in 2020 when my wife had to pay $5 for the Plex app so she could access our library. Or the exercise of sharing libraries if you don't have a Plex pass, which is a real pain.
But that wasn't my point. I was trying to relay that jellyfin isn't as buggy and difficult as a lot of self hosters claim.
I don't mean to diminish your comment, but I just went through the setup process for both Plex and jellyfin (moving to new hardware) and there was no significant difference between the setups.
Maybe this wasn't the case a few years ago, but jellyfin is just a setup, point to libraries, and enable hardware accel.
That's largely correct, and this demonstration is mostly symbolic as well.
The treaties with indigenous peoples of Canada are administered by an arm of the federal government, but the treaty agreements themselves are technically between the indigenous peoples and the crown, hence the address to King Charles.
Pretty charged article, and nonsense journalism. Boooo.
Scotland and Quebec have barely any common ground regarding their independence. Different backgrounds, different goals. Even on trans issues.
Citing material locked behind a pay-per-paper source? Really?
Citing the Montreal Gazette (American owned, caught promoting American-style propaganda several times) is weak.
This is the third time I've seen articles targeting a Commonwealth country using "lessons learned from Canada". The other times have been about right-to-die issues.
This is very obviously a campaign article, not journalism.
Eleventy is my goto as well. It builds a really, really static site. Perfect for posting practice writing, photos, and notes from the steps I take doing my homelab.
That disk upgrade thing was a mountain out of a molehill. All they are doing is reserving some of their disk health features for synology branded disks because they're the only ones they can verify meet their standards for their software.
Then explain why one can successfully use and old synology to "mark" drives as "authentic synology" and move them into a newer DSM model to use them. This means the mechanism amounts simply to marking disks and not binning disks or any kind of actual hardware selection. Which in turn means that "certified" Synology disks are nothing more than disks with a Synology signature. And not even in firmware, but on the platter.
And that is the "molehill" everyone is calling Synology out on.
As explained ad nauseum on various yt channels, having a hw compatibility list makes sense for users likely to buy support, like business users. It makes little sense in a home market where users are both more likely to buy 3rd party disks and will not likely invoke official Synology support.
But add on top of it that there is no functional hardware difference between certified and non-certified, and it becomes pretty clear that Synology is to be avoided.
Full disclosure, I myself am running an old ds211j for backups. It's way out of updates, and there isn't much of a 3rd party image collection for synology hardware, but it works fine and lives in its own locked down subnet.
Portugal is a shining example of how and why decriminalization can work; they treat drug addiction as a health issue rather than a criminal one. They have also put a lot of planning and effort into shifting resources into the infrastructure required to make that approach viable; more support staff and locations, awareness training for police.
Yes, but with an explanation.
You don't necessarily need coding skills to "audit", you can get q sense of the general state of things by simply reading the docs.
The docs are a good starting point to understand if there will be any issues from weird licensing, whether the author cares enough to keep the project going, etc. Also serious, repeated or chronic issues should be noted in the docs if its something the author cares about.
And remember, even if you do have a background in the coding language, the project might not be built in a style you like or agree with.
I'm pretty proficient at bash scripting, and I found the proxmox helper scripts a spaghetti mess of interdependent scripts that were simply a nightmare to follow for any particular install.
I think the overall message is do your best within your abilities.