5·5 months agoYes there is, it’s called the compositor.
In Wayland, the compositor is functionally both a display server and compositor.
Yes, but not on Gnome Wayland and that’s the problem. Their decision to do CSD only on Wayland is a problem for the entire ecosystem.
Server Side Decorations merge when?
Yeah, OP should probably add “Rust-based” or specific Epoch to avoid confusion.
like 5 years or more
They’re really good & extremely dedicated devs with lots of experience working on it, so I think that’s a little bit of an underestimation, I think it’s within the possibly of getting there within 5 years, maybe not exactly 1:1 ofc. However, they’ve really put in a lot of thought into base of the project, and in my experience having a strong well designed base can propell future development forward much faster than initial estimates. Even now, they’ve been smashing mile stones much faster than expected and if they keep their current trajectory at a steady rate I believe it’s possible the meet some level of parody within a 5 year goal. Ofc, anything can happen so only time will tell. Also, considering the fact that they’re not having to deal with the X11 tech debt…
1. Monopolistic business practices to crush competition (Netscape, Java, web browsers, etc.).
- Microsoft was found guilty of maintaining an illegal monopoly and engaging in anti-competitive tactics against competitors like Netscape Navigator and Java in the 1990s antitrust case.
2. Illegal bundling of Internet Explorer with Windows to eliminate browser rivals.
- The U.S. government accused Microsoft of illegally bundling Internet Explorer with Windows to crush competition from other web browsers. Microsoft was found guilty of this tying arrangement.
3. Keeping useful Windows APIs secret from third-party developers to disadvantage competitors.
- Microsoft allegedly kept useful Windows APIs secret from third-party developers to give an advantage to their own applications, though this was not a central part of the antitrust case.
4. Embracing proprietary software and vendor lock-in tactics to prevent users from switching.
- Microsoft has been criticized for embracing proprietary software and vendor lock-in tactics that make it difficult for users to switch to alternatives, such as their failed attempts to establish OOXML as an open standard for Office documents.
5. “Embrace, Extend, Extinguish” strategy against open source software.
- Microsoft has been accused of using the “Embrace, Extend, Extinguish” strategy against open source software to undermine adoption of open standards. This is also shown in the leaked Halloween documents.
6. Privacy violations through excessive data collection, user tracking, and sharing data with third parties.
- Microsoft has faced scrutiny over privacy issues, such as the NSA surveillance scandal and their handling of user data with Windows 10.
7. Complicity in enabling government surveillance and spying on user data (PRISM scandal).
- The PRISM surveillance scandal revealed Microsoft’s complicity in enabling government spying on user data.
8. Deliberately making hardware/software incompatible with open source alternatives.
- Microsoft has been accused of deliberately making hardware and software incompatible with open source alternatives through restrictive licensing requirements.
9. Anti-competitive acquisitions to eliminate rivals or control key technologies (GitHub, LinkedIn, etc.).
- Microsoft has acquired many companies over the years, sometimes in an effort to eliminate competition or gain control over key technologies and platforms.
10. Unethical contracts providing military technology like HoloLens for warfare applications.
- Microsoft’s $480 million contract to provide HoloLens augmented reality tech for the military drew protests from employees and criticism over aiding warfare.
11. Failing to address workplace issues like sexual harassment at acquired companies.
- Microsoft’s failed acquisition of gaming company Activision Blizzard raised concerns about ignoring workplace issues like sexual harassment at the acquired company.
12. Forced automatic Windows updates that override user control and cause system issues.
- Microsoft has faced backlash for forcing automatic updates on Windows users, including major updates that have caused issues like deleted files and crashed systems. Users have little control over when updates install.
13. Maintaining monopolistic dominance in productivity software and operating systems.
- Microsoft has maintained its dominance in areas like productivity software (Office) and operating systems (Windows), making it difficult for competitors to gain market share. This monopolistic position allows them to exert control over the industry.
14. Vague and toothless AI ethics principles while pursuing lucrative military AI contracts.
- Microsoft’s AI ethics principles have been criticized as vague and toothless in light of their pursuit of lucrative military AI contracts.
15. Continued excessive privacy violations and treating users as products with Windows.
- Windows 10 has been criticized for excessive data collection and lack of user privacy controls, essentially treating users as products to be monetized.
16. Restrictive proprietary licensing that stifles open source adoption.
- Microsoft’s proprietary software licensing makes it difficult for open source alternatives to be adopted widely, as they have a history of undermining open source software and interoperability with Windows.
This isn’t even anywhere near everything.
That’s not Linux… Here’s hoping your post doesn’t get removed.
1·5 months agoIt’s just that they seem to treat pre-release like they’re stable while never actually having a stable release. It’s not really an issue persay, it’s just kinda annoying how they handle release cycles. Pre-releases are supposed to be for experimentation and for finding bugs, not to sit on for months upon years.
I’ve been using lawnchair for such a long time, but one gripe I have is that it seems to be in a perpetual state of “Pre-release” with large gaps between releases.
by “the host” you mean the server?
With the traffic decrypted it should be possible to automate the inspection process to some degree, but obviously milage may vary.
By combining with other methods for intercepting HTTPS traffic, typically involving installing certificates or modifying system configurations like configuring your browser or operating system to log secret keys.
To break down the process of the cert method :
- Device Trust: Install a trusted Root CA certificate (issued by you) on the Android device using Root permissions. This certificate tricks apps into trusting the proxy. Without Root level install the apps may reject the certificate as User Installed.
- Device Routes Traffic : Configure the rooted Android device to route its traffic to the proxy on the separate system. This can be done through proxy settings.
- Proxy Decryption : Configure the proxy to use the corresponding private key to decrypt the HTTPS traffic coming from your device, this key is generated when you created/issued the Root CA.
- Traffic Inspection : With the traffic decrypted, you can use Wireshark configured to the proxy to inspect the traffic.
- Proxy Re-encrypts and Forwards: After inspection, the proxy re-encrypts the traffic using a legitimate certificate and forwards it to the real website.
It entirely depends on how you set it up and where in the transport pipeline you’re intercepting pockets from.
123·6 months agoHell yeah!! So many needed fixes that have been bugging me for a while are finally fixed!!
Why should we have the same standard for two fundamentally different languages with distinct design philosophies and features?
Even if the C coding standard was used, it fundamentally will not make Rust more legible to C-only kernel devs. Imposing the C coding standard on Rust would be fundamentally counterproductive, as it would undermine Rust’s safety and productivity features. Rust’s coding guidelines align with its design principles, promoting idiomatic Rust code that leverages language features like ownership, borrowing, and lifetimes.
This ensures that Rust code in the kernel is safe, concurrent, and maintainable, while adhering to the language’s best practices. While the C coding standard served its purpose well for the procedural C language, it is ill-suited for a modern language like Rust, which has different priorities and language constructs. Having separate coding standards allows each language to shine in its respective domain within the kernel, leveraging their strengths while adhering to their respective design philosophies. Having separate coding standards for C and Rust within the kernel codebase is the sensible approach.
3·6 months agoIf it’s a native app then it’s fine, else if it’s just a chromium skin then that bullshit can fuck off.
In any case, it’s the temporary file directory so it should be fine to delete them manually.
Just make sure that podman isn’t running while you’re deleting them, assuming it is podman.
This error is caused by a compatibility issue between Wine’s RandR (X11 display extension) implementation and the NVIDIA proprietary drivers.
a. Install winetricks and run
winetricks orm=backbuffer glsl=disableThis will configure Wine to use a different rendering method that is compatible with the NVIDIA drivers.&/Or
b. Use a tool like Q4Wine to configure the Wine prefix and set the “UseRandR” option to “N” This will disable Wine’s use of the RandR extension and use a fallback method instead.
That should fix it.
13·6 months agoI’d like to add that the current Cosmic DE in use is an ageing fork of Gnome and is going to be replaced with a Rust-based DE called Cosmic (Epoch) soon.
<gentoo joke>