ProletarianDictator [none/use name]

  • 0 Posts
  • 19 Comments
Joined 2 years ago
cake
Cake day: December 21st, 2022

  • It couldn’t possibly be that fucktons of people out there see this political Western-influenced kernel clownshow for what it is, or that they might disagree with Western narrative on global issues.

    Probably not even that.

    Knowing software devs, most of those opposing are probably doing so out of the same anti-moderation “muh censorship” brainworms that surface every time a project tries to give some Nazi the boot or adds a code of conduct.

    Libs being this overzealous convinced a good number of chuds to automatically come to Russia’s defence out of pure contrarianism.




  • Agreed on not shaming forking, but creating a serious fork for anything substantial takes a fuckton of effort and many times you wind up with multiple mutually-incompatible source trees. In libre, community-run software, it’s almost always advantageous to settle your differences and centralize efforts than to fork and split the efforts.

    Most forks die because its hard to get people to jump ship. Think about how much lemmitors cry about Lemmy, the devs, and lemmy.ml, yet they cannot muster the effort to keep kbin alive or get sublinks off the ground. OG Hexbear was eventually rebased back to upstream too.

    When forking, there are a few paths, all having some serious disadvantage:

    1. Soft fork and remain at the mercy of the decisions of the project you forked from unless your fork becomes the de facto default. This is usually only really beneficial if you want to rectify disagreements on a handful of small features. (e.g. Ungoogled-Chromium / Brave vs. Chromium, various Linux kernel forks)

    2. Hard fork and lose compatibility of upstream patches, making keeping feature parity difficult. This is only really beneficial if your fork gets a critical mass of users/devs and can outpace upstream at features users want. (e.g. Forgejo vs. Gitea, Lemmy vs. OG Hexbear)

    3. Rewrite from the ground up, building the same or a similar API but upon a better architecture. This is the most effort, but keeps compatibility with the ecosystem, and potentially has a massive payoff once fully implemented (e.g. like Tvix vs. Nix, OpenHarmony vs. Android)

    4. Write an alternative from scratch, focusing on implementing the most important features and not caring about feature parity. This is the best balance for small utils, but you lose the ability to be used as a drop-in replacement. (e.g. lsd / eza vs. GNU, ripgrep vs. grep)

    Getting a critical mass of devs onboard is key to success, but also difficult. Outside of some open core software making some shitty money-grabbing decision and sparking community outrage, that’s not very probable.


  • The West seems to be doing whatever it can to accelerate its decline.

    American hard power is about to be hard countered, so America’s massive amount of soft power could provide a nice floor to keep a comfortable position on the world stage after its coercion mechanisms are thwarted. But they keep trying to weaponize their best means of post-multipolar relevancy.

    Using the Linux kernel to push their short term geopolitical objectives is about as large of an unforced error as can be made.

    Having the most developed open source ecosystem gives the US & EU disproportionate influence over the direction of the technology sphere; an advantage adversaries are incentivized to avoid trying to circumvent because no one wants to waste time reinventing the wheel.

    Yeah, it’ll probably slow Russian technological development a little for awhile until non-Western ecosystems mature, but this will hurt the West far more in the long run than the relative edge they get over Russia.

    Any countries not explicitly Western-aligned will see the writing on the wall and take steps to build homegrown alternatives that can’t be used for leverage over them…and they can start just by forking the Western projects.

    Russia, China, India, Brasil, Iran, Saudi Arabia, Vietnam, Africa, Latin America, and Southeast Asia will comprise a vast majority of software developers, and their projects will inevitably outpace their Western counterparts as more countries develop, especially if this trend of wielding FOSS as a geopolitical coercion tool continues.

    What happens when China has a runaway technological edge and decides to take giant strides to build and migrate their products/systems to a homegrown kernel?..now 30%+ of global manufacturing is built without consideration for Linux compatibility and interop. Soon any software wishing to take advantage of top hardware begins to target this new kernel and Linux kernel support becomes an afterthought. Shortly after, new APIs and programming languages are built to target these platforms, with bad/no localization to Latin & Germanic languages, possibly even using hanzi or cyrillic instead of latin characters. Then you wind up a tech ecosystem where cultural factors disadvantage Westerners instead of the opposite in the current status quo.

    Throwing away global leadership to take cheap shots at Russia.

    Meanwhile, Russian devs & Russian companies will make sockpuppet personas and accounts, fork the kernel, and ignore licensing since they’re gonna be blocked from Western markets regardless.






  • I haven’t used KDE (outside VMs) since like 2010, but have followed development somewhat. Just seems like it’s easy to configure to have a Windows taskbar like experience.

    I really like GNOME, and it is nice and simple, but I think new users might find the workflow different enough from what they’re used to that it’s not intuitive. I’ve been using GNOME for like a decade though.

    I think both are probably easy enough to use with default settings, GNOME is just more of a departure from the conventions of proprietary OS shells.








  • You don’t need to use Whisper, I got some names mixed up. I was thinking of wyoming-faster-whisper which uses the FOSS speech to text system faster-whisper, but there are others that can be used.

    Edited my original comment to fix that.

    Wyoming is a protocol for voice assistants.

    It ties together:

    • speech recognition services (faster-whisper, vosk, whisper.cpp, OpenAI’s Whisper API)
    • text to speech services (piper)
    • wake word detection services (openWakeWord, snowboy, porcupine1)
    • intent handling services
    • intent recognition services

    Home Assistant can interact with that protocol. I think the addons run servers for various components used by the wyoming protocol server that the integration can use, but I run it separate from Home Assistant, so idk.

    Not sure what futo is capable of, but you can use anything that can communicate with a wyoming server. I’m willing to wager you can, but idk.

    OpenAI’s ChatGPT API and LLM models are orthogonal to this, but probably could be used as an intent or as the fallback when no other intent was recognized. So I’m pretty sure you could link up getting a response from OpenAI or any other LLM API, but I haven’t tried setting that up for myself yet. wyoming-handle-external lets you pipe the input text to the stdin of whatever program you give it and responds with the program’s stdout, so you could definitely use this to pass it to OpenAI or Ollama.