i’d avoid BIOS-based RAID… it doesn’t really offer many benefits over linux-based raid like MDADM, and MDADM offers a LOT of up-sides for portability, repairability, diagnostics, etc
i’d avoid BIOS-based RAID… it doesn’t really offer many benefits over linux-based raid like MDADM, and MDADM offers a LOT of up-sides for portability, repairability, diagnostics, etc
let’s not go too far though… the holders of h264/h265 did put a lot of money and effort into developing the codec: a new actual thing… they are not patent trolls, who by definition produce nothing new other than legal mess
add tailscale and you’re golden
as a linux professional, congrats you’re a junior and have a lot to learn about the world
yeah stupid people like most tech workers who just need their tech to work as expected rather than be “customisable”
there’s value in the “just works” when not working costs you hundreds of $ per hour that it doesn’t work
$2000 for a phone is nothing when it’s a professional device
also nothing that looks the same for the annoying time when you do have to do some analog copying
no I, l, or | and i usually avoid ‘, “, !, /, \ (which one was it again?) and a few others that i have set in my password manager
okay, so it seems as though disregarding android usage of LTS seems reasonable because whilst it shouldn’t be this way, nothing will actually change
which is kinda the point of LTS right? or does LTS for kernel mean additional things?
okay but all that “technically possible but nobody has written the software yet” is incredibly unhelpful
it’s technically possible to run every windows app perfectly in WINE but nobody has implemented a bunch of the APIs without bugs yet
HTTPS is heavy when you’re talking about the extreme low power, bandwidth, and compute devices matter is intending to support
its also not a broadcast protocol - matter intends to connect many devices to many devices
those are off the top of my head; i’m sure there are more. HTTP is great, but new/alternate network protocols aren’t inherently bad: especially when you’re operating in a very constrained/niche environment
you’re thinking of openbsd; not freebsd
sure, but a $1m over how many causes? i’d assume they don’t really even use freebsd, considering macos was based in openbsd? so i’d suggest that an employee match is pretty decent
kinda different there though… it’s trivial to add whatever data you like to images etc (and that’s without even resorting to steganography), but that data is only accessible with an application. i believe the question was intended as whether you could get a virus from downloading/playing media files… the content of that “hidden data” isn’t executable, so whilst it’s reasonable to say it’s possible to transport a virus via hidden data in media, it’s not reasonable to say that you can “get” a virus using that same method alone
the protocol that allows instances to communicate is, but AFAIK there’s an API that apps use… the protocol is kinda just for how to push raw bulk data around, whilst the instance itself does things like filter based on “top”, “hot”, etc
also, in activitypub things like the actor (user), each comment, post, etc are individual objects which must be requested individually (or in a list via a search i think?), so any app that communicates via activitypub would need to make hundreds of requests to the instance to display a single post, comments, and user information!
also as a kbin user
god damn i want a native kbin app!
you’re missing the fact that google chat and XMPP is a totally different situation… they used an open protocol; they didn’t open their backend
sure, but an open source UI isn’t going to change that… they’d just close the source!
sure you can fork it, but you can also just copy the UI to an open source clone
imagine if twitter were activitypub: kinda like having an OSS backend with a proprietary front end… i’d bet the move to mastodon would be far quicker… network effects keep people on twitter… same here with OSS backend: we can reimplement the UI and people will have the same experience
yeah… pragmatism beats purity every time: they’re doing some great work, but to do that great work they have to fund it somehow… i think that open sourcing all of the functional components (the bridges) and keeping the shiny UI closed is a pretty good way of doing that!
i guess i get not wanting to used closed source clients too, but it’s shades of grey: people shouldn’t hate on them for keeping 1 part closed source!
so i just did a quick search and apparently
Starting with Gitea 1.19, Gitea Actions are available as a built-in CI/CD solution.
*edited:
also they support being a package repo, including container registry
kinda the same reason people suggest something like linux mint over slackware, gentoo, arch, etc… mint is easy to install and is preconfigured to be an easy to use user desktop environment. you can configure any other option to be have like that, but they tend to be a bit more “DIY”, which is great if you know what you’re doing!
dedicated NAS OSes will have good software out of the box that make it easy to configure and manage various common disk-related configurations (RAID, SMB, NFS, etc). you can certainly do all this yourself, but it might not have a pretty, unified user interface, or you might have to deal with software that isn’t compatible with some version of a library that’s in your distro of choice… all resolvable things, but they take time to solve: anywhere from installing a package manually to applying a kernel patch and recompiling the kernel to get something to work