Diseased Open Source Software Community - it's about ethics in Code of Conducts

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
It's because she's a cute anime girl written with the problems of a depressed insane male in his twenties or thirties but also the power to change things by controlling tech and reality itself with her mind. For them, it's both validation of them being a woman and a power fantasy as a coder. They want to be that young girl being revered and outright worshipped as a computer god. In reality they're more like that creep who wanted to control her:

View attachment 5148528

Except not thin and with patchier hair. Similar smirk though. Very similar.
True, however it was always just a mid early 2000s anime. Back in the day it wasn't something that stood out and honestly when I first watched it I just moved on from it cause everything just was average. I mean I get it, smaller budget and shit but still it would never be something I'd even bat an eye to. I'd say its kinda like noir....It was a watch but I don't think i'd ever re-watch it. To see people create entire imageboards dedicated to a 15 episode series (lainchan) is really wierd.
 
  • Disagree
Reactions: 306h4Ge5eJUJ
Windows is pretty notorious for having every other major release be complete ass, followed by a return to relative normalcy the next time.
People keep saying this but that hasn't been true since 8*. Windows 10 is an ad-riddled mess with buggy inconsistent GUI and random features removed and I'm anticipating the fried dogshit that Windows 12 will be and everyone will brand a "good version".

*Sidenote: I remember people being HYPED for that fucking pile. Thanks for ruining computers forever.
 
Microsoft's C++ evangelist and professional they/them is shocked to learn something about himself: https://mastodon.social/@TartanLlama/110932656678058254, https://archive.is/NiOEs

View attachment 5295047

Next time come here, we'll give you your puzzle pieces for free. Also...

View attachment 5295050

Hmm... It's almost as if...
Isn’t it funny how all these people are diagnosed with is always some form of autism or ADHD, always something that means the rest of the world has to cater to them instead of them being responsible for working on themselves?
 
"Because X11 fucking sucks and was due for a replacement years ago."

X sucks in many ways, but that is not super important. What is important is that X WORKS. It does what it needs to do and it does it quite well, eventhough the internal details are quite ugly.

X needs to evolve and add additional protocols to remove a few warts, but it works.

All the fucking wayland faggots have no clue. They want to turn linux into a desktop only piece of shit because they do not understand why X11 is good and what problems it solves.

Wayland faggots are like if you let WoW players decide on the future of a protocol for your windowing system. "It has to solve my use-case of playing WoW locally. All other use-cases are irrelevant."
Fuck them and fuck fuckland.

I want to ssh -X into a remote machine, run a command and have its window show up, seamlessly, on my local desktop.
If your solution is "use vnc or rdesktop" then I will come to your house and dillate you with a plumbers showel until you see the errors of your ways.
 
Last edited:
X sucks in many ways, but that is not super important. What is important is that X WORKS. It does what it needs to do and it does it quite well, eventhough the internal details are quite ugly.

X needs to evolve and add additional protocols to remove a few warts, but it works.
It is important. X is an architecturally flawed part of desktop Linux that harms security, privacy, and performance. It is both over complicated and feature incomplete for what is necessary for the part it plays in a modern graphics + input stack. For aspects like improving security you could technically address this by adding additional extensions and then migrating apps to use them. While you could just keep adding extensions to X and then migrate applications to onto the new secure way to do things. There is value in existing technology that works, but there is also value in simplifying the current architecture based off how modern hardware works and improving security in a world where users run code from untrusted sources. While the Wayland ecosystem is being developed, since X will still work, the lack of resources being invested into X is not going to be a large problem.

It is important that as operating switch out X for Wayland that they try not to break as much as possible which is why the Xwayland backwards compatibility layer is important. The goal is for everything to keep working, but for users to gain extra performance, security, and privacy.
I want to ssh -X into a remote machine, run a command and have its window show up, seamlessly, on my local desktop.
If your solution is "use vnc or rdesktop" then I will come to your house and dillate you with a plumbers showel until you see the errors of your ways.
Since computers are exponentially more powerful and have exponentially more memory retained mode is no longer a benefit for drawing the contents of your applications. Modern applications will render straight to a texture which eventually will get composited into the final image shown on screen. Similarly remote rendering is evolving to just a raw video encoding of the frames being rendered. Simplicity wins in the end.
By default GLX, the OpenGL extension for X, can not be used with X11 forwarding. Indirect GLX is what enabled streaming OpenGL commands, but it was not supported well, is stuck on an old version of OpenGL, and was a security nightmare so it was disabled. Especially with the rise of laptops and mobile, there is not a big interest in continuing to invest in servers telling the client to render things locally on its behalf. There are big energy and complexity savings by just having the client use a hardware video decoder.

The project you are looking for is called waypipe. It runs both on the server and the client. The waypipe server pretends to be a Wayland compositor and it proxies messages and the graphics to the waypipe client which handles passing that to the local Wayland compositor on your machine.
 
There is value in existing technology that works, but there is also value in simplifying the current architecture based off how modern hardware works and improving security in a world where users run code from untrusted sources.
What security does Wayland provide against a user who is executing untrusted code? The display server doesn't stop a user from injecting malware into their own processes (LD_PRELOAD, ptrace + dlopen, etc.), and almost all of the user's software that you want to extract data from is going to be running under their uid.

Modern applications will render straight to a texture which eventually will get composited into the final image shown on screen. Similarly remote rendering is evolving to just a raw video encoding of the frames being rendered. Simplicity wins in the end.
Do you operate in the US? How do you intend to handle accessibility features?

That major issue aside, I work with some clients who enjoy multiple layers of remote rendering with different compression schemes, and the final result leaves something to be desired. Some of my older colleagues frequently can't read it.
 
What security does Wayland provide against a user who is executing untrusted code? The display server doesn't stop a user from injecting malware into their own processes (LD_PRELOAD, ptrace + dlopen, etc.), and almost all of the user's software that you want to extract data from is going to be running under their uid.
You are extrapolating from what I am saying. Desktop Linux's security is still a joke even with the improvements from Wayland, but I will give credit that ensuring that inputs are only going to the focused window, and that unfocused applications are no longer being able to sniff and manipulate clipboard contents are steps in the right direction.
If you can LD_PRELOAD, you can also just run whatever malicious compositor you want.
In a sensible Linux distribution you are not able to pthread attach to another program running with the same uid as processes are not dumpable by default.
Securing the Wayland process is up to the operating system to properly do and Linux does already have the tools to let this be done.
Do you operate in the US? How do you intend to handle accessibility features?
The application would integrate with the accessibility service of the operating system it is running on. The way the application actually gets the pixels it intends to show to the screen is not really related to accessibility. Typically applications are given the freedom to render whatever they want to the screen. There is no way to enforce they actually increase a font size based off some setting in the operating system.
That major issue aside, I work with some clients who enjoy multiple layers of remote rendering with different compression schemes, and the final result leaves something to be desired. Some of my older colleagues frequently can't read it.
If the internet connection does not have enough bandwidth, has high latency and jitter, or regular packet loss it is unfortunate that people are not getting a good experience. Developers are betting on the user's internet connection and video codecs both getting better over time. Full remote rendering is definitely not the right design for everything.
 
The point I'm trying to make is that, while people support removing cruft from X11, they don't support simplifying it to such an extreme degree. If you argue with the Wayland developers about these missing features, they will insist that either it should be implemented in the compositor directly by virtue of being able to be implemented in the compositor, or that the proposed feature is somehow a vulnerability despite being standard practice in most every other desktop environment.

You are extrapolating from what I am saying. Desktop Linux's security is still a joke even with the improvements from Wayland, but I will give credit that ensuring that inputs are only going to the focused window, and that unfocused applications are no longer being able to sniff and manipulate clipboard contents are steps in the right direction.
Users in my industry will complain endlessly if they're not allowed to run macro recorders which require sniffing to be allowed. The macros are frequently used to relay data between two black-box applications by rapidly pasting fields from one application to the other. While I would greatly prefer that the users don't do this, it's frequently necessary due to the costs of involving developers and the additional internal regulations they attach.

The application would integrate with the accessibility service of the operating system it is running on. The way the application actually gets the pixels it intends to show to the screen is not really related to accessibility. Typically applications are given the freedom to render whatever they want to the screen. There is no way to enforce they actually increase a font size based off some setting in the operating system.
Accessibility also includes features such as screen readers which require the ability to obtain the text that was rendered. The data can still be obtained locally via AT-SPI2, but obtaining them remotely requires you to tunnel the data to the client somehow.
 
If you argue with the Wayland developers about these missing features, they will insist that either it should be implemented in the compositor directly by virtue of being able to be implemented in the compositor, or that the proposed feature is somehow a vulnerability despite being standard practice in most every other desktop environment.
This mostly has to do with an X shape hole that exists when X is removed from the system. For example, why does a Wayland compositor have to deal with implementing clipboard support? Someone could implement a clipboard service which can be communicated with over D-Bus. Just because it may need to know the currently focused window that doesn't mean that it must be in the same process as the window manager or have to use the Wayland protocol. The reason why clipboard uses Wayland seems to just be because clipboard code lived in X. Unlike D-Bus, since Wayland has clients talk to UNIX socket created by the compositor it means that only the compositor can send or receive data with a client. This means that everything needs to be built into the compositor or at least will have to pass through the compositor. While this is better than X, I don't find this to be good design when you know that people are going to want to these components to be modular so they can switch them out. There isn't a good reason for a window manager service to be bundled with a clipboard service.
Users in my industry will complain endlessly if they're not allowed to run macro recorders which require sniffing to be allowed.
Macro recorders can be useful, but allowing every application on the system to be able to sniff and inject input without the user knowing is not the best that can be done. Recording background input could be a permission that the user must grant to a program ahead of time. A recording indicator somewhere on the screen to let the user know that their input is currently being recorded could be useful so that users can avoid typing anything sensitive.
Accessibility also includes features such as screen readers which require the ability to obtain the text that was rendered. The data can still be obtained locally via AT-SPI2, but obtaining them remotely requires you to tunnel the data to the client somehow.
Despite the advancements in computer vision, screen recorders do not actually look at what is rendered nor do they inject themselves into the rendering process to detect what text is going to be rendered. With X11 forwarding the same issue exists.
For getting AT-SPI2 working remotely the solution is to have D-Bus create a socket bound to localhost, port forward this to the remote server using SSH, then use xdg-dbus-proxy that has a filter that only allows it to be used for accessibility. This proxy comes from the Flatpack project as they wanted things like accessibility to work while not exposing the full bus to applications.
 
Last edited:
Lol I think your guys argument got this thread the Infected tag.
If so, that is bizarre. The discussion is on topic, and I for one find it interesting. I've been aware of the X11 vs. Wayland controversy for a long time without understanding the issues in any depth, so these details have been informative. And it's only a handful of posts.
 
If so, that is bizarre. The discussion is on topic, and I for one find it interesting. I've been aware of the X11 vs. Wayland controversy for a long time without understanding the issues in any depth, so these details have been informative. And it's only a handful of posts.
This thread is 10% open source community watch and 90% autistic sperging that dries up every pussy in a 500 miles radius and belongs in a different subforum.
I want to laugh at tranny CoCs, not read your essay on the newest version of ShitNobodyCaresAboutOS, Autismo Prime.
 
Back to mocking idiots, I don't believe this has been mentioned yet: Drew DeVault wrote Alpine Linux does not make the news (archive) and so of course Alpine Linux shortly thereafter made the news (archive).
To be clear, this is hilarious because Drew's point is that not making the news means it's low drama and stable to use. Then suddenly an alleged woman, Alice / psykose, decides to stop maintaining packages for Alpine, for some reason, and it gets in the news.

I know of at least one troon who works on Alpine (not the alleged woman named in the article), honestly surprised it isn't in the news more often given how much drama troons cause.
 
a.png
That didn't last long. A quick look at GitHub (A) shows that Psykose is already back on the package maintainer grind.
This time for Chimera Linux (A).
b.png
 
I know of at least one troon who works on Alpine (not the alleged woman named in the article), honestly surprised it isn't in the news more often given how much drama troons cause.
They do cause drama, just not usually connected to Alpine. Ariadne Conill (Powerword: William Pitcock; often goes under the name Kaniini) for instance is a grade A dramawhore and was featured multiple times in this thread and others.
 
Back