or1k

It's shit.

Pingora is designed for developing secure high-performance network services and programmable network systems in Rust. The framework is well tested and already used in the operation of high-loaded systems - a proxy built on its basis has been used in the Cloudflare content delivery network instead of nginx for more than a year and processes more than 40 million requests per second. https://blog.cloudflare.com/pingora-open-source

Jonathan Riddell, former Kubuntu project leader currently working on the KDE neon distribution, has announced the availability of a new set of Oxygen 6 icons designed to be shipped with KDE 6. Besides KDE, the proposed icons can be used in any applications and user environments that conform to XDG (FreeDesktop X Desktop Group) specifications.

The Kubuntu distribution has announced (https://kubuntu.org/news/kubuntu-graphic-design-contest/) a logo and branding contestThe contest aims to create new branding elements, including the project logo, desktop splash screen, color palette and fonts. The contest assignment notes the desire for a recognizable and modern design that reflects the specificity of Kubuntu, is positively perceived by newcomers and old users, and harmoniously blends with the style of KDE and Ubuntu. Submissions will be accepted until April 1. The top three entries will receive $50 worth of branded merchandise, and the winner will receive a Kubuntu Focus NX MiniP computer worth over $1000. (https://kubuntu.org/news/kubuntu-graphic-design-contest/)

KDE Slimbook 16 is developed with the participation of the KDE community and Spanish hardware vendor Slimbook. The software is based on the KDE Plasma 6 desktop, the Ubuntu-based KDE Neon system environment and a selection of free applications such as the Krita graphics editor, the Blender 3D design system, the FreeCAD CAD system and the Kdenlive video editor. The default graphics environment uses the Wayland protocol. All applications and updates delivered with the KDE Slimbook are thoroughly tested by KDE developers to ensure a high level of environment stability and hardware compatibility. The new notebook is characterized by the use of a 16-inch screen (2560x1600, 6:10 sRGB 100%, 165Hz), as well as the use of AMD Ryzen 7 7840HS processor (8 cores with 16 threads, 3.8-5.1GHz) and AMD Radeon 780M GPU (12 cores RDNA 3, 2700 MHz). The device features 2 USB-C 3.2 ports, three USB-A 3.2 ports, Wi-fi 6, Bluetooth 5.2 and a physically disconnected HD 720P 1.0M webcam. It comes with up to 64GB of RAM (5600 MHz DDR5) and 8TB SSD (two NVMe PCIe 4.0 M.2 SSD NVMe slots). Size: 356.6*248.5*20.3mm, weight 1.86 kg. The cost of the device is 999 euros. (https://kde.slimbook.es/) (https://discuss.kde.org/t/introducing-the-kde-slimbook-v-first-laptop-with-plasma-6/10756)

When discussing the bug about the relatively high power consumption on AMD APUs supporting hardware video decoding compared to Windows, an AMD engineer, Alex Deucher, the primary developer of the amdgpu driver, admitted that displaying video in Linux is fundamentally inefficient. Linux video output now uses the following chain: - Compressed video stream - VCN (hardware video decoding module for AMD GPUs) - Raw YUV data - Palette conversion, scaling on the GFX module (essentially a 3D gas pedal in the GPU, which forces it to increase core and VRAM frequencies) - RGB data - Display output. How it should work: - Compressed video stream - VCN - Raw YUV data - A display controller that will convert the palette, scale and display. This can be solved more efficiently in Wayland compositors, but there is no implementation yet. This problem is solved in Microsoft Windows and Google Android, for there are full-fledged single compositors that provide the appropriate capabilities and APIs - something that is not yet available in Linux, because neither X.org nor Wayland can handle YUV streams directly.

it's example of script to do backups and sending to aws s3. #!/bin/bash # AWS Settings AWS_ACCESS_KEY_ID="your_access_key" AWS_SECRET_ACCESS_KEY="your_secret_access_key" #AWS_DEFAULT_REGION="your_aws_region" # Database parameters DB_NAME="name" DB_USER="user" DB_PASSWORD="pass" DB_HOST="127.0.0.1" DB_PORT="3306" # The path to the folder to be backed up SOURCE_DIR="/your/path" # Name of the S3 bucket and path to the folder inside the bucket S3_BUCKET="name_of_yours_s3_bucket" S3_FOLDER="name_of_yours_s3_folder_in_bucket" # Create a backup folder with the current date and time BACKUP_FOLDER="$(date +'%Y-%m-%d_%H-%M-%S') (FULL)" mkdir -p "/tmp/$BACKUP_FOLDER" # Archive the backup folder cd "$(dirname "$SOURCE_DIR")" || exit tar -zcvf "/tmp/$BACKUP_FOLDER/$(basename "$SOURCE_DIR").tar.gz" "$(basename "$SOURCE_DIR")" # Dump the database mysqldump -u"$DB_USER" -p"$DB_PASSWORD" -h "$DB_HOST" -P "$DB_PORT" "$DB_NAME" > "/tmp/$BACKUP_FOLDER/$DB_NAME.sql" # Copy archive and database dump to S3 aws s3 cp "/tmp/$BACKUP_FOLDER/$(basename "$SOURCE_DIR").tar.gz" "s3://$S3_BUCKET/$S3_FOLDER/$BACKUP_FOLDER/" aws s3 cp "/tmp/$BACKUP_FOLDER/$DB_NAME.sql" "s3://$S3_BUCKET/$S3_FOLDER/$BACKUP_FOLDER/" # Clear the temporary folder rm -rf "/tmp/$BACKUP_FOLDER" you can change it. for example i need to exclude some dir in my path cd "$(dirname "$SOURCE_DIR")" || exit tar -zcvf "/tmp/$BACKUP_FOLDER/$(basename "$SOURCE_DIR").tar.gz" --exclude='wp-content/uploads' --exclude='wp-content/backups-dup-lite' "$(basename "$SOURCE_DIR")"

The developers of the Qt Lightweight Desktop Environment ( LXQt ) have described the process of migrating to the Qt6 library and the Wayland protocol. Migration of all LXQt components to Qt6 is currently seen as the primary focus of the project. Once the migration is complete, support for Qt5 will be discontinued. Most LXQt components are already ported to Wayland to some extent. Only the screen configurator, the screenshot program, and the global keyboard shortcut handler lack Wayland support. There are no plans to port the sudo wrapper to Wayland. The results of the porting to Qt6 will be presented in the LXQt 2.0.0 release scheduled for April this year. In addition to internal changes, the new branch will offer by default a new application menu "Fancy Menu", which, in addition to categorizing applications, implements a summary view of all applications and adds a list of frequently used applications. In addition, the new menu has enhanced program search capabilities. It is noted that the implementation of Wayland support will not lead to conceptual changes: the project will remain modular and will continue to adhere to the classic desktop organization. Similar to the support of various window managers, LXQt will be able to work with all composite managers based on the wlroots library, developed by the developers of the Sway user environment and providing basic functions for organizing the composite manager based on Wayland. The work of LXQt using Wayland was tested with the composite managers labwc, wayfire, kwin_wayland, sway and Hyprland. The best result was achieved with labwc. The panel, desktop, file manager (PCmanFM-qt), image viewer (LXimage-qt), permission management system (PolicyKit), volume control component (pavucontrol, PulseAudio Volume Control) and global hotkeys handler are now fully migrated to Qt6. Not yet translated to Qt6 are the session manager, notification system, power management mechanism, configurator (appearance, screen, input devices, locales, file associations), and the interface for viewing running processes (Qps), terminal emulator (QTerminal), screenshot program (Screengrab), program launcher (Runner), sudo strapping, SSH password request interface (LXQt Openssh Askpass), FreeDesktop portal system (XDG Desktop Portal), and system settings and user management interface (LXQt Admin). In terms of Wayland readiness, most of the above LXQt components have already been ported to Wayland to some degree. Only the screen configurator, the screenshot program, and the global keyboard shortcut handler lack Wayland support. There are no plans to port the sudo wrapper to Wayland.

Matthew Kosarek introduced (https://discourse.ubuntu.com/t/introducting-miracle-wm-a-wayland-compositor-built-on-mir/42583) miracle-wm, which is based on using the Wayland protocol and components for building Mir composite managers. Miracle-wm supports mosaic layout of windows in the style of the i3 window manager, Hyprland composite manager, and Sway user environment. Finished assemblies are generated in snap format. The functionality of miracle-wm in the first release: mosaic window management with the ability to leave stylish gaps between windows, use of virtual desktops, support for reserving screen areas for panel placement, the ability to expand windows to the full screen, support for multi-output, keyboard navigation and control. The ultimate goal of the project is to create a composite server using mosaic window management, but more functional and stylish than projects such as Swayfx.

Name: hier - description of the filesystem hierarchy Description: A typical Linux system has, among others, the directories: [ / ] This is the root directory. This is where the whole tree starts. [ /bin ] This directory contains executable programs which are needed in single user mode and to bring the system up or repair it. [ /boot ] Contains static files for the boot loader. This directory holds only the files which are needed during the boot process. The map installer and configuration files should go to [ /sbin ] and [ /etc ]. The operating system kernel (initrd for example) must be located in either [ / ] or [ /boot ]. [ /dev ] Special or device files, which refer to physical devices. See mknod(1). [ /etc ] Contains configuration files which are local to the machine. Some larger software packages, like X11, can have their own subdirectories below [ /etc ]. Site-wide configuration files may be placed here or in [ /usr/etc ]. Nevertheless, programs should always look for these files in [ /etc ] and you may have links for these files to [ /usr/etc ]. [ /etc/opt ] Host-specific configuration files for add-on applications installed in [ /opt ]. [ /etc/sgml ] This directory contains the configuration files for SGML (optional). [ /etc/skel ] When a new user account is created, files from this directory are usually copied into the user's home directory. [ /etc/X11 ] Configuration files for the X11 window system (optional). [ /etc/xml ] This directory contains the configuration files for XML (optional). [ /home ] On machines with home directories for users, these are usually beneath this directory, directly or not. The structure of this directory depends on local administration decisions (optional). [ /lib ] This directory should hold those shared libraries that are necessary to boot the system and to run the commands in the root filesystem. [ /lib<qual> ] These directories are variants of [ /lib ] on system which support more than one binary format requiring separate libraries (optional). [ /lib/modules ] Loadable kernel modules (optional). [ /lost+found ] This directory contains items lost in the filesystem. These items are usually chunks of files mangled as a consequence of a faulty disk or a system crash. [ /media ] This directory contains mount points for removable media such as CD and DVD disks or USB sticks. On systems where more than one device exists for mounting a certain type of media, mount directories can be created by appending a digit to the name of those available above starting with '0', but the unqualified name must also exist. [ /media/floppy[1-9] ] Floppy drive (optional). [ /media/cdrom[1-9] ] CD-ROM drive (optional). [ /media/cdrecorder[1-9] ] CD writer (optional). [ /media/zip[1-9] ] Zip drive (optional). [ /media/usb[1-9] ] USB drive (optional). [ /mnt ] This directory is a mount point for a temporarily mounted filesystem. In some distributions, [ /mnt ] contains subdirectories intended to be used as mount points for several temporary filesystems. [ /opt ] This directory should contain add-on packages that contain static files. [ /proc ] This is a mount point for the proc filesystem, which provides information about running processes and the kernel. This pseudo-filesystem is described in more detail in proc(5). [ /root ] This directory is usually the home directory for the root user (optional). [ /run ] This directory contains information which describes the system since it was booted. Once this purpose was served by [ /var/run ] and programs may continue to use it. [ /sbin ] Like [ /bin ], this directory holds commands needed to boot the system, but which are usually not executed by normal users. [ /srv ] This directory contains site-specific data that is served by this system. [ /sys ] This is a mount point for the sysfs filesystem, which provides information about the kernel like [ /proc ], but better structured, following the formalism of kobject infrastructure. [ /tmp ] This directory contains temporary files which may be deleted with no notice, such as by a regular job or at system boot up. [ /usr ] This directory is usually mounted from a separate partition. It should hold only shareable, read-only data, so that it can be mounted by various machines running Linux. [ /usr/X11R6 ] The X-Window system, version 11 release 6 (present in FHS 2.3, removed in FHS 3.0). [ /usr/X11R6/bin ] Binaries which belong to the X-Window system; often, there is a symbolic link from the more traditional [ /usr/bin/X11 ] to here. [ /usr/X11R6/lib ] Data files associated with the X-Window system. [ /usr/X11R6/lib/X11 ] These contain miscellaneous files needed to run X; Often, there is a symbolic link from [ /usr/lib/X11 ] to this directory. [ /usr/X11R6/include/X11 ] Contains include files needed for compiling programs using the X11 window system. Often, there is a symbolic link from [ /usr/include/X11 ] to this directory. [ /usr/bin ] This is the primary directory for executable programs. Most programs executed by normal users which are not needed for booting or for repairing the system and which are not installed locally should be placed in this directory. [ /usr/bin/mh ] Commands for the MH mail handling system (optional). [ /usr/bin/X11 ] This is the traditional place to look for X11 executables; on Linux, it usually is a symbolic link to [ /usr/X11R6/bin ]. [ /usr/dict ] Replaced by [ /usr/share/dict ]. [ /usr/doc ] Replaced by [ /usr/share/doc ]. [ /usr/etc ] Site-wide configuration files to be shared between several machines may be stored in this directory. However, commands should always reference those files using the [ /etc ] directory. Links from files in [ /etc ] should point to the appropriate files in [ /usr/etc ]. [ /usr/games ] Binaries for games and educational programs (optional). [ /usr/include ] Include files for the C compiler. [ /usr/include/bsd ] BSD compatibility include files (optional). [ /usr/include/X11 ] Include files for the C compiler and the X-Window system. This is usually a symbolic link to [ /usr/X11R6/include/X11 ]. [ /usr/include/asm ] Include files which declare some assembler functions. This used to be a symbolic link to [ /usr/src/linux/include/asm ]. [ /usr/include/linux ] This contains information which may change from system release to system release and used to be a symbolic link to [ /usr/src/linux/include/linux ] to get at operating-system-specific information. (Note that one should have include files there that work correctly with the current libc and in user space. However, Linux kernel source is not designed to be used with user programs and does not know anything about the libc you are using. It is very likely that things will break if you let [ /usr/include/asm ] and [ /usr/include/linux ] point at a random kernel tree. Debian systems don't do this and use headers from a known good kernel version, provided in the libc*-dev package.) [ /usr/include/g++ ] Include files to use with the GNU C++ compiler. [ /usr/lib ] Object libraries, including dynamic libraries, plus some executables which usually are not invoked directly. More complicated programs may have whole subdirectories there. [ /usr/libexec ] Directory contains binaries for internal use only and they are not meant to be executed directly by users shell or scripts. [ /usr/lib<qual> ] These directories are variants of [ /usr/lib ] on system which support more than one binary format requiring separate libraries, except that the symbolic link [ /usr/libqual/X11 ] is not required (optional). [ /usr/lib/X11 ] The usual place for data files associated with X programs, and configuration files for the X system itself. On Linux, it usually is a symbolic link to [ /usr/X11R6/lib/X11 ]. [ /usr/lib/gcc-lib ] contains executables and include files for the GNU C compiler, gcc(1). [ /usr/lib/groff ] Files for the GNU groff document formatting system. [ /usr/lib/uucp ] Files for uucp(1). [ /usr/local ] This is where programs which are local to the site typically go. [ /usr/local/bin ] Binaries for programs local to the site. [ /usr/local/doc ] Local documentation. [ /usr/local/etc ] Configuration files associated with locally installed programs. [ /usr/local/games ] Binaries for locally installed games. [ /usr/local/lib ] Files associated with locally installed programs. [ /usr/local/lib<qual> ] These directories are variants of [ /usr/local/lib ] on system which support more than one binary format requiring separate libraries (optional). [ /usr/local/include ] Header files for the local C compiler. [ /usr/local/info ] Info pages associated with locally installed programs. [ /usr/local/man ] Man pages associated with locally installed programs. [ /usr/local/sbin ] Locally installed programs for system administration. [ /usr/local/share ] Local application data that can be shared among different architectures of the same OS. [ /usr/local/src ] Source code for locally installed software. [ /usr/man ] Replaced by [ /usr/share/man ]. [ /usr/sbin ] This directory contains program binaries for system administration which are not essential for the boot process, for mounting [ /usr ], or for system repair. [ /usr/share ] This directory contains subdirectories with specific application data, that can be shared among different architectures of the same OS. Often one finds stuff here that used to live in [ /usr/doc ] or [ /usr/lib ] or [ /usr/man ]. [ /usr/share/color ] Contains color management information, like International Color Consortium (ICC) Color profiles (optional). [ /usr/share/dict ] Contains the word lists used by spell checkers (optional). [ /usr/share/dict/words ] List of English words (optional). [ /usr/share/doc ] Documentation about installed programs (optional). [ /usr/share/games ] Static data files for games in [ /usr/games ] (optional). [ /usr/share/info ] Info pages go here (optional). [ /usr/share/locale ] Locale information goes here (optional). [ /usr/share/man ] Manual pages go here in subdirectories according to the man page sections. [ /usr/share/man/locale/man[1-9] ] These directories contain manual pages for the specific locale in source code form. Systems which use a unique language and code set for all manual pages may omit the <locale> substring. [ /usr/share/misc ] Miscellaneous data that can be shared among different architectures of the same OS. [ /usr/share/nls ] The message catalogs for native language support go here (optional). [ /usr/share/ppd ] Postscript Printer Definition (PPD) files (optional). [ /usr/share/sgml ] Files for SGML (optional). [ /usr/share/sgml/docbook ] DocBook DTD (optional). [ /usr/share/sgml/tei ] TEI DTD (optional). [ /usr/share/sgml/html ] HTML DTD (optional). [ /usr/share/sgml/mathml ] MathML DTD (optional). [ /usr/share/terminfo ] The database for terminfo (optional). [ /usr/share/tmac ] Troff macros that are not distributed with groff (optional). [ /usr/share/xml ] Files for XML (optional). [ /usr/share/xml/docbook ] DocBook DTD (optional). [ /usr/share/xml/xhtml ] XHTML DTD (optional). [ /usr/share/xml/mathml ] MathML DTD (optional). [ /usr/share/zoneinfo ] Files for timezone information (optional). [ /usr/src ] Source files for different parts of the system, included with some packages for reference purposes. Don't work here with your own projects, as files below [ /usr ] should be read-only except when installing software (optional). [ /usr/src/linux ] This was the traditional place for the kernel source. Some distributions put here the source for the default kernel they ship. You should probably use another directory when building your own kernel. [ /usr/tmp ] Obsolete. This should be a link to [ /var/tmp ]. This link is present only for compatibility reasons and shouldn't be used. [ /var ] This directory contains files which may change in size, such as spool and log files. [ /var/account ] Process accounting logs (optional). [ /var/adm ] This directory is superseded by [ /var/log ] and should be a symbolic link to [ /var/log ]. [ /var/backups ] Reserved for historical reasons. [ /var/cache ] Data cached for programs. [ /var/cache/fonts ] Locally generated fonts (optional). [ /var/cache/man ] Locally formatted man pages (optional). [ /var/cache/www ] WWW proxy or cache data (optional). [ /var/cache/<package> ] Package specific cache data (optional). [ /var/catman/cat[1-9] or /var/cache/man/cat[1-9] ] These directories contain preformatted manual pages according to their man page section. (The use of preformatted manual pages is deprecated.) [ /var/crash ] System crash dumps (optional). [ /var/cron ] Reserved for historical reasons. [ /var/games ] Variable game data (optional). [ /var/lib ] Variable state information for programs. [ /var/lib/color ] Variable files containing color management information (optional). [ /var/lib/hwclock ] State directory for hwclock (optional). [ /var/lib/misc ] Miscellaneous state data. [ /var/lib/xdm ] X display manager variable data (optional). [ /var/lib/<editor> ] Editor backup files and state (optional). [ /var/lib/<name> ] These directories must be used for all distribution packaging support. [ /var/lib/<package> ] State data for packages and subsystems (optional). [ /var/lib/<pkgtool> ] Packaging support files (optional). [ /var/local ] Variable data for [ /usr/local ]. [ /var/lock ] Lock files are placed in this directory. The naming convention for device lock files is LCK..<device> where <device> is the device's name in the filesystem. The format used is that of HDU UUCP lock files, that is, lock files contain a PID as a 10-byte ASCII decimal number, followed by a newline character. [ /var/log ] Miscellaneous log files. [ /var/opt ] Variable data for [ /opt ]. [ /var/mail ] Users' mailboxes. Replaces [ /var/spool/mail ]. [ /var/msgs ] Reserved for historical reasons. [ /var/preserve ] Reserved for historical reasons. [ /var/run ] Run-time variable files, like files holding process identifiers (PIDs) and logged user information (utmp). Files in this directory are usually cleared when the system boots. [ /var/spool ] Spooled (or queued) files for various programs. [ /var/spool/at ] Spooled jobs for at(1). [ /var/spool/cron ] Spooled jobs for cron(8). [ /var/spool/lpd ] Spooled files for printing (optional). [ /var/spool/lpd/printer ] Spools for a specific printer (optional). [ /var/spool/mail ] Replaced by [ /var/mail ]. [ /var/spool/mqueue ] Queued outgoing mail (optional). [ /var/spool/news ] Spool directory for news (optional). [ /var/spool/rwho ] Spooled files for rwhod(8) (optional). [ /var/spool/smail ] Spooled files for the smail(1) mail delivery program. [ /var/spool/uucp ] Spooled files for uucp(1) (optional). [ /var/tmp ] Like [ /tmp ], this directory holds temporary files stored for an unspecified duration. [ /var/yp ] Database files for NIS, formerly known as the Sun Yellow Pages (YP).

Maxim Dunin, one of the three active core developers of Nginx, has announced (https://mailman.nginx.org/pipermail/nginx-ru/2024-February/PJ2FQXIMS534BZYJKOJYQNEZ4LEOK3LK.html) the creation of a new fork - FreeNginx. Unlike the Angie project, which also created an offshoot of Nginx, the new fork will be developed exclusively as a non-commercial, community-developed project. FreeNginx is positioned as the main descendant of Nginx - "given the details - more like a fork left over from F5". The goal of FreeNginx: to provide Nginx development free from arbitrary corporate interference. http://freenginx.org/

LineageOS 21 (https://lineageos.org/) has reached parity in functionality and stability with LineageOS 20, and is considered ready for the first release. Builds have been prepared for 109 device models. LineageOS can also be run in the Android Emulator and Android Studio environment. Additionally, the option to build in Android TV and Android Automotive mode is provided. Compared to LineageOS 20, in addition to the changes specific to Android 14, the following improvements are offered: ▪️ Implemented a migration to the android-14 branch from the AOSP repository as of February 2024. WebView browser engine synchronized with Chromium 120.0.6099.144. ▪️ Included a new Glimpse app with an interface for managing the photo gallery, which is used by default instead of the Gallery2 app from the AOSP. ▪️ Redesigned the calculator, which has been redesigned in line with the Material You concept and unified with the rest of the applications. ▪️ In the Jelly web browser, the user interface has been redesigned and stylized using the Material You design concept. Added support for the Brave search engine and search provider. Added the ability to selectively provide access to location data for individual sites. And other changes.

- Cheat - a cheat sheet on Linux commands. - Cloudup - a tool for backing up GitHub repositories to Bitbucket. - Crypt - encrypts and decrypts files. - Cryptocurrency - converts cryptocurrency based on real-time exchange rates of the top 10 cryptocurrencies. - Currency - currency converter. - Geo - Provides WAN, LAN, router, DNS, Mac, and IP information. - Gist - Gist management. - Lyrics - quickly retrieve song lyrics from the command line. - Meme - create memes from the command line. - Movies - search and display movie information. - Newton - performs numerical calculations up to symbolic math. - Qrify - turns a given string into a qr code. - Short - shortens URLs - Siteciphers - check which ciphers are enabled or disabled for a given https site. - Stocks - provides certain information about stocks. - Taste - a recommendation system that provides three similar items like the item supplied (these can be books, music, artists, movies, games, etc.). - Todo - a task manager from the command line. - Transfer - quickly transfer files from the command line. - Weather - displays weather information for your location. - Youtube-Viewer - watch YouTube from the terminal. 📌 https://github.com/alexanderepstein/Bash-Snippets

Changes: - Wine Mono engine with .NET platform implementation has been updated to release 9.0.0. - System tray support has been improved. - Improved exception handling on ARM platforms. - YEAR2038 macro for using 64-bit time_t type is involved in the build. - Improved cursor handling in winewayland.drv driver. - Closed bug reports related to Elite Dangerous, Epic Games Launcher 15.21.0, LANCommander, Kodu. - Closed bug reports related to the following applications: Quick3270 5.21, digikam, Dolphin Emulator, Windows Sysinternals Process Explorer 17.05, Microsoft Webview 2 installer. In addition, the release of the Android application Winlator 5.0 (https://github.com/brunodev85/winlator/releases/tag/v5.0.0) has been published (https://winlator.org/), which provides strapping over Wine and Box86/Box64 emulators to run Windows applications on the Android platform. The new version improves the task manager, improves performance, adds support for changing design themes and improves compatibility with XInput. https://www.winehq.org/

The Fedora Project has announced (https://fedoramagazine.org/introducing-fedora-atomic-desktops/) the unification (https://www.opennet.ru/opennews/art.shtml?num=60582) of the naming of custom builds of the Fedora Linux distribution that use the atomic update model and monolithic system layout. Such variants of the distribution are organized into a separate family of Fedora Atomic Desktops. Builds in this family will be referred to as "Fedora Atomic Desktops". At the same time, it was decided to keep the old name for already recognized and long-existing atomic builds. Fedora Atomic builds are delivered as a monolithic image that is not separated into separate packages and can be updated as a whole by replacing the entire system image. The base environment is built from official Fedora RPM packages using the rpm-ostree toolkit and mounted in read-only mode. Flatpak is used to install and update additional applications.

In response to sudo for Windows, developers decided to port Word to OpenBSD Teo de Raadt, founder of the OpenBSD project, has published a joking response to the publication of sudo for Windows, in which he mocks Microsoft's attitude towards development. A patch with a Word implementation, created by renaming the mg text editor, has been proposed for inclusion in OpenBSD. As with Microsoft's publication of sudo, the Word application also ignores the name overlap with an existing project, does not care about maintaining compatibility, does not take into account possible trademark infringement, and is published without clarifying the opinion of the original product team.

🎮 ThievingFox is a set of exploits for collecting credentials from various password managers and utilities. Each module uses a specific injection method into the target process and then plugs in internal functions to collect credentials. ▪️Github

SiCat is an advanced exploit search tool designed to efficiently identify and collect exploits from both open source and local repositories. Focused on cybersecurity, SiCat allows users to quickly search the Internet for potential vulnerabilities and relevant exploits for any project or system. ▪️Github

A powerful tool for capturing and analyzing network traffic. It provides a complete set of features to inspect HTTP requests and responses, view raw payload data, and gather information about network devices. With PacketSpy, you can gain valuable insights into network patterns and troubleshoot problems effectively. git clone https://github.com/HalilDeniz/PacketSpy.git ▪️Github

The plan (https://wiki.xfce.org/releng/wayland_roadmap) now mentions implementing initial Wayland support in the base components of the next major release of Xfce 4.20, while retaining X11 support. It has been decided that X11 support will not be discontinued for the foreseeable future. The Wayland-based session in Xfce 4.20 will cover the minimum required set of features, and the missing functionality will be added gradually in preparation for the next releases. It is also planned to continue honing the Wayland-based environment in already ported custom applications. The project does not have the resources to maintain its own composite manager for Wayland, but has rejected the possibility of using a binding to XWayland for the work.

42345.mp4

Following the successful release of Steam Deck, Valve has encountered (https://overclockers.ru/blog/History/show/134619/Valve-zabrakovala-klient-Steam-dlya-Ubuntu) technical issues on the Ubuntu platform related to the use of Snap by default. Valve developer, Timothy Bessette, has expressed concern over the increased number of bug reports caused by Canonical's unofficial repackaging of the Steam client via Snap. It is noted that users are actively sending their bug reports to Valve, instead of contacting the developers of the distribution. In an official statement, a Valve representative recommends that users install Steam on Debian and similar operating systems using the official DEB file, following the instructions provided, to avoid possible Snap-related technical issues. In addition, he suggested considering the Flatpak version if DEB is not suitable for some reason. In an official statement, a Valve representative recommends that users install Steam on Debian and similar operating systems using the official DEB file, following the provided instructions to avoid possible Snap-related technical issues. In addition to this, he suggested considering the Flatpak version if DEB is not suitable for some reason. In addition, should the situation worsen, Valve reserves the right to implement a pop-up window in all Snap versions of Steam to warn users that an unofficial version may be running. This emphasizes the importance of using official installation methods to ensure stable operation of the Steam client on various Linux distributions.

From her position as CEO, Mitchell will return (https://blog.mozilla.org/en/mozilla/a-new-chapter-for-mozilla-laura-chambers-expanded-role/) to the position of Chairman of the Board of Directors of Mozilla Corporation, a position she held for many years prior to her election as CEO. Reason for leaving: a desire to share leadership of Mozilla's business and mission. Mitchell has been on the Mozilla team for 25 years and is the author of the Mozilla Public License and a leader of the Mozilla Foundation. Laura Chambers, who serves on the audit committee and board of directors, will take over as CEO by the end of the year. Prior to joining Mozilla, Laura ran Willow Innovations, a startup promoting the world's first silent breast pump worn in a bra. Prior to running a startup, Laura held executive positions at Airbnb, eBay, PayPal and Skype.