PupBiru

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

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

i’m sure they learned plenty of things about the old game engine they built

and now they have a new one… which was the whole point

re peertube discovery, i saw this the other day:

https://sepiasearch.org/

framasoft developed both peertube, and this… i assume to address that exact concern

i’d suggest using the CI built into whatever git host you choose: commit a change and CI runs automatically and updates posts

less bot per se, but definitely easier than webhooks or scraping to sync

yes and no… we don’t have revenue goals, but we have goals for the fediverse and we have the social media critical mass problem: you have to hit a critical mass before you become indispensable… if people try the fediverse and there’s not enough content, they tend to just leave rather than stick with it

mastodon can do default instances because they have the account migration process… i totally agree this is a great solution: get people in with sane defaults, and then let people move once they know how it works

there will be plenty of people that don’t move (or maybe that’s solvable too: analyse your toots and suggest a more niche instance after 2mo?) but i’m not sure that’s a huge problem if your “default instance” is more of a random choice from a list of sane defaults

it’s kinda vaguely similar though… a fediverse instance is moderated by the instance admins, just like a discord server (though discord has a level of admin above server mod/admin i’m not sure that distinction matters for the general user)

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

not all the data afaik, but all the data for subs that it’s users are subscribed to

i mean… to deny the similarities in the platform is kinda ridiculous… i’d go so far as to say that lemmy/kbin probably wouldn’t have the format it does without reddit being like it is. there’s a direct relationship, whether we like it or not

“even”… i think reddit’s follow ups were least likely to succeed because they were the least organic!

place was special (at first) because it was a bunch of people with no time to plan and prepare… it was humans doing human things with all the limitations and creativity that came with that

other iterations of place were bots and pre-planned “stake our claim” rather than making something interesting and different… it was kinda all just the same as the last one but with subtle “meme of the moment” tweaks

of course nobody is going to commit to supporting a stable API for 10 to 20 years… that’s expensive as heck and not even remotely worth it!

there’s nothing “wrong” with software development, it’s just that consumers demand new features rather than stagnation… i sure don’t want to be using a 20 year old app because we’ve come a long way in 20 years in so many regards

in 2003, windows xp was still microsoft’s dominant OS with vista still being several years off, half life 2 was about to be released, gmail was allllmost ready to release, msn messenger was still in its prime

yeah no, ill stick with rapidly changing technologies rather than sticking to that for some misplaced sense of “stability”

the server requirements of fediverse instances isn’t that high… plenty of people just run hobby servers! as long as we keep that process pretty interesting that could just continue to be the case: people hosting the instances just as a hobby and not expecting a return!

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