jlsalvador 1mo ago • 100%
The first improvement (Media Foundation by FFMPEG) could be significant. Currently, VALVe generates large shaders to re-render those Media Foundation videos into other free codecs. These shaders can be several gigabytes in size for some games with lengthy videos. With FFMPEG, those videos could be played without being re-encoded as shaders.
jlsalvador 1mo ago • 90%
TLDR:
- New Media Foundation backend using FFMpeg.
- Initial support for network sessions in DirectPlay.
- New Desktop Control Panel applet.
- Various bug fixes.
jlsalvador 1mo ago • 100%
https://github.com/LadybirdBrowser/ladybird
It takes a time to compile the whole project, but a way less than Firefox and Chrome. There is an AUR package for ArchLinux.
IMHO, it is not yet daily-drive usable. Really slow for JS. The window manager is extreme limited (I can not drag tabs outside the window). It can not render steampowered neither youtube (I didn't test any more websites, just these two). The current setting page is just a window popup with a checkbox for one option. But competition is always good for the users. A web browser is a big project for today standards. Good luck to these developers 💪👍
jlsalvador 1mo ago • 100%
I tested it the last week from the main git branch, it doesn't open YouTube homepage, yet.
jlsalvador 2mo ago • 83%
Hi!
I made my own inmutable distro using buildroot (https://buildroot.org): https://simplek8s.org
This distro is just an AIO kernel image that will bootstrap everything in RAM. You can mount additional devices for data persistence (for example you can mount your storage in /var
).
jlsalvador 2mo ago • 100%
TLDR; from MIT to GPL.
jlsalvador 2mo ago • 100%
Disappointing and poorly crafted ending. There are scenes from the trailer that doesn't include in the final game.
jlsalvador 2mo ago • 100%
For example, when someone ask for a command to list files, and another one reply with a command that removes everything.
jlsalvador 3mo ago • 100%
TLDR; the reviewer is upset because the PSVR2-PC adapter doesn't come with a Display Port cable, and his Bluetooth adapter is not compatible. So he can't review the unit on time until he receive both items. 🤷
jlsalvador 3mo ago • 100%
Official Linux RSS about stable kernel releases: https://www.kernel.org/feeds/kdist.xml
jlsalvador 3mo ago • 80%
It's illegal in Europe to have an opt-out checked by default, must be an opt-in unchecked by default. This is one of the reason that Microsoft has always troubles in Europe about privacy and opt-out services.
jlsalvador 4mo ago • 100%
Yes, using xrandr in the /etc/sddm.conf
(https://man.archlinux.org/man/sddm.conf.5#DisplayCommand=) /usr/share/sddm/scripts/Xsetup
.
jlsalvador 4mo ago • 100%
Hahaha. Common problem with multiscreen with different resolutions. Your laptop screen is below and left of your main display, and X11 renders this black "virtual screen".
There are multiple solutions:
a) Set your screen resolution and position through KDE Plasma SystemSettings and push the button "apply to SDDM configuration" (I think Plasma 6.0 removed this option, try to find it in the SystemSettings KCM SDDM section).
b) The another solution is the old one. Create a file into /etc/X11/xorg.conf/display.conf
with the proper values of position and resolution. Search in a wiki about examples (archlinux wiki?).
c) There is a third one that I used few years ago. SDDM allows you run any command after the screen initialization. So you can exec your xrand command here. Search about /etc/sddm.conf
jlsalvador 5mo ago • 100%
Buddy, this message was posted 6 month ago, when this issue was a thing. Does not applied nowdays. But thank you for your help.
jlsalvador 6mo ago • 100%
When you create a filesystem, there is a parameter named as "block percent free". This parameter should be "5%", so a 5% of your partition size can only be written by the "root" user.
You can decrease this value or just free some space. You can try to create files or folders as root as well.
jlsalvador 6mo ago • 81%
I think that the reason is the same for "why is XMPP mentioned more than IRC?". IRC has more clients, it's less resources hungry and simpler than XMPP.
I think that the reason is because it is old-fashione, and it's clients feel outdated and (native) "lacking features" compared to more popular clients like Discord, WhatsApp, Messenger, Telegram or Signal. 🤷♂️
I can imagine my cousins using any of the clients I mentioned before, but not IRC, XMPP, or any protocol from my era. Life and traditions, isn't it?
jlsalvador 7mo ago • 100%
The last year 2023 was incredible (providing a lot of good games).
Fils Aime: ‘Thank you, but I want more.’ ‘Thank you, but give me more.’ I mean, it is insatiable. 2012 https://kotaku.com/the-trouble-with-the-never-satisfied-gamer-5920572
jlsalvador 7mo ago • 100%
#!/usr/bin/env bash
A folder dotfiles
as git repository and a dotfiles/install
that soft links all configurations into their places.
Two files, ~/.zshrc
(without secrets, could be shared) and another for secrets (sourced by .zshrc
if exist secrets).
jlsalvador 8mo ago • 100%
I used Tekton for the last two years, and I didn't like it. One of the reasons is the community split around Tekton Hub between versions 3 and 4. Another reason is that it's not very Kubernetes native. While you write YAML, there are a subset of instructions that limit you regarding mundane things you can do on Kubernetes but Tekton doesn't support, such as mounting different PersistentVolumeClaims or setting tasks by platforms or nodes (amd64, arm64, etc).
I was so frustrated that I created my own Kubernetes-native CI/CD solution. Currently in development phases (when it is done, I will publish it here). This one uses real native Kubernetes components (jobs). You create Webhooks that launch Workflows, and Workflows can launch other Workflows or Jobs. You can do anything in a Job with no limitations other than Kubernetes itself. Take a look if you want: https://github.com/jlsalvador/simple-cicd
Hello! Do you hate the watermark preview banner? Add the text `HideDesktopPreviewBanner=true` just after `[General]` in the file `~/.config/kdeglobals`. You will have something as the following: ``` [General] HideDesktopPreviewBanner=true ``` Better for OLEDs displays, stylish, auto-suspend all-blacks displays, etc. Src: https://invent.kde.org/plasma/plasma-workspace/-/commit/b15d9f41f7f41210b1dd5a78dc1b1894bd40c3dd#16f843a94440a858a2387e36472454ab5685e179_193_196
Hello! Do you hate the watermark preview banner? Add the text `HideDesktopPreviewBanner=true` just after `[General]` in the file `~/.config/kdeglobals`. You will have something as the following: ``` [General] HideDesktopPreviewBanner=true ``` Better for OLEDs displays, stylish, auto-suspend all-blacks displays, etc. Src: https://invent.kde.org/plasma/plasma-workspace/-/commit/b15d9f41f7f41210b1dd5a78dc1b1894bd40c3dd#16f843a94440a858a2387e36472454ab5685e179_193_196
Hello world! I want to release to internet my custom immutable rolling-release extreme-simple Linux distribution for Kubernetes deployments. I was using this distribution for about the last 6 years on production environments (currently used by a few startups and two country's public services). I really think that it could be stable enough to be public published to internet before 2024. **I'm asking for advice before the public release**, as licensing, community building, etc. # A few specs about the distribution: - **Rolling release**. Just one file (currently less than ~40Mb) that can be bootable from BIOS or UEFI (+secure boot) environments. You can replace this file by the next release or use the included toolkit to upgrade the distribution (reboot/kexec it). Mostly automated distribution releases by each third-party releases (Linux, Systemd, Containerd, KubeAdm, etc). - **HTTP setup**. The initial setup could be configured with a YAML file written anywhere in a FAT32 partition or through a local website installer. You can install the distribution or configure KubeAdm (control-plane & worker) from the terminal or the local website. - **Simple, KISS**. Everything must be simple for the user, this must be the most important aspect for the distribution. Just upstream software to run a production ready Kubernetes cluster. - **No money-driven**. This distribution must be public, and it must allow to be forked at any time by anyone. # A bit of background: I was using CoreOS before Redhat bought them. I like the immutable distro and A/B release aspect of the CoreOS distribution. After the Redhat acquisition, the CoreOS distribution was over-bloated. I switched to use my own distribution, built with Buildroot. A few years later, I setup the most basic framework to create a Kubernetes cluster without any headache. It's mostly automated (bots checking for new third-party releases as Linux, Systemd, Containerd, KubeAdm, etc; building, testing & signing each release). I already know that building a distribution is too expensive, because of that I programmed few bots that made this job for me. Now days, I only improve the toolkits, and approve the Git requests from thats bots. Thank you for your time!