It’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 :
It entirely depends on how you set it up and where in the transport pipeline you’re intercepting pockets from.
That’s a weird way of saying :
I’mma pull bullshit out of my ass with no evidence.
why would you care about a far away government collecting intelligence about you over the one that can (and will) actually hurt you?
Both of you are dangerous in truth. We don’t trust anyone. (ಠ_ಠ)>⌐■-■ Why do you think we use FOSS?
You really just compared “African leader” to “a monkey”. I can’t, I can’t believe it. The irony, the sheer irony, it’s delicious, so very delicious, keep feeding me more of this shit.
You’re completely miss understanding the entire thing. You’re dear lead is being compared to an iconic, childhood beloved, Disney, cartoon bear 🐻, and you think it’s racist? How foolish.
You’re the only one “comparing Chinese people to yellow animals” in truth. Your Irony is delicious to me.
False. “Chinese people” aren’t being compared to “yellow animals”. The only thing happening here is your dear leader looking like a cartoon Bear 🐻.
Removed by mod
Hell 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.
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.
1. Monopolistic business practices to crush competition (Netscape, Java, web browsers, etc.).
2. Illegal bundling of Internet Explorer with Windows to eliminate browser rivals.
3. Keeping useful Windows APIs secret from third-party developers to disadvantage competitors.
4. Embracing proprietary software and vendor lock-in tactics to prevent users from switching.
5. “Embrace, Extend, Extinguish” strategy against open source software.
6. Privacy violations through excessive data collection, user tracking, and sharing data with third parties.
7. Complicity in enabling government surveillance and spying on user data (PRISM scandal).
8. Deliberately making hardware/software incompatible with open source alternatives.
9. Anti-competitive acquisitions to eliminate rivals or control key technologies (GitHub, LinkedIn, etc.).
10. Unethical contracts providing military technology like HoloLens for warfare applications.
11. Failing to address workplace issues like sexual harassment at acquired companies.
12. Forced automatic Windows updates that override user control and cause system issues.
13. Maintaining monopolistic dominance in productivity software and operating systems.
14. Vague and toothless AI ethics principles while pursuing lucrative military AI contracts.
15. Continued excessive privacy violations and treating users as products with Windows.
16. Restrictive proprietary licensing that stifles open source adoption.
This isn’t even anywhere near everything.