Piracy

Thanks.

Did you bother to read the article or did you only decide to write this argument w/o any substantial basis?

Went to the website in the Picture. It is mentioned there if you scroll down a bit - https://cure.org/

For anyone concerned about their beverages. Following is a table of Recommended maximum daily intake of caffeine according to different age groups & categories: https://www.canada.ca/en/health-canada/services/food-nutrition/food-safety/food-additives/caffeine-foods.html

FDA’s recommendations: https://www.fda.gov/consumers/consumer-updates/spilling-beans-how-much-caffeine-too-much

For measure: 8 oz (227 g) of Coffee has 80-100 mg of caffeine or 35-45 mg of Caffeine per 100 g of Coffee. (Average, numbers may vary accordingly.)

«Tenebre Rosso Sangue» by ‹Keygen Church›

I can but I also do want to convert my keyboard.

A lot of people do use Adblockers. https://backlinko.com/ad-blockers-users

You can try other sources as well. The statistics say significant numbers on multiple places.

There are some hacky methods to make some Java software use Wayland. Iirc, https://github.com/openjdk/wakefield is the jvm version I used to test it on Minecraft and Mindustry. I did not really get that far, but it has been quite some time since I tested it so I do not remember exactly what the results were. Otherwise it is possible the subjected software itself needs extra editing to make it work on Wayland.

No, running sway with the --unsupported-gpu flag launches it without any remarks about your hardware. It’s been like this for a good while.

You clearly do not know what you are talking about so I have no interest in giving more value to your already worthless comment. It is amusing that you must introduce the term “Wayland Apologist” as if that has any meaning in this sector.

The main issue here is not that some of the issues that are mentioned there are not genuine. They indeed are genuine and have mostly already been notified to the devs working on the protocols and the compositors. The issue here is how those are presented. By creating this almost cultish “battle between the 2 display servers” thing is not productive and demoralizes developers. Making criticism is one thing and productive but “boycotting” is not. And certainly not in the bad faith way the author of that article has done. I myself have both X and WL setups and I alternate between them frequently. I am not sitting here “boycotting” one display server in a prejudiced manner. This is Linux, not Windows or MacOS. Users are free to continue using Xorg and develop it according to them if they do not like something else. And similarly, they are free to use Wayland.

Amazing text! I was just commenting how ridiculous the article is this morning and now you have written a more lenghty criticism.

As for the Zoom bit. I will add my 2 years experience of using it on Wayland on Artix as well as Void Linux - I never used Gnome and it worked fine on Sway and River on my iGPU. In between a few updates I did face a few crashes of zoom when rendering on my nvidia gpu but it was still fine. I have not used zoom in over an year so I can’t comment on how it is now.

As for “wayland does not work properly on nvidia.” Solely nvidia is blame. They have been pushing out patches to bring out more support but it’s just nvidia who can fix that in the end. While I would not want to assume what hardware the author uses. Wayland works like butter on my Intel hardware.

Great alternatives for xclip and many other X-tools are already in the market.

The VSync issue on wayland is genuine. Disabling it in-game does not affect anything because it is enforced by the compositor. VSync is an integral part of Wayland Compositioning (acc. to the wlroots dev) but a solution to automatically disable it in full screen applications, etc is down the pipeline and work is ongoing. I have not been following it but I think some fixes were already released, I could be wrong.

As for X11 Atoms: https://stackoverflow.com/questions/41005297/x-to-wayland-what-about-atoms Just boils down to the application dev’s willingness to port the app to Wayland. The author of the ‘boycott wayland’ article seems to just want wayland to implement Xorg 1:1 for it to not fail their stupid standard of what-should-be-boycotted. And at that point Wayland is not Wayland but Xorg.

Most of the arguments presented in the ‘Boycott Wayland’ article are either generic issues being worked upon by the devs or things that don’t have much relevance but put down in a manner as if to almost fear-monger that Wayland is the spawn of the devil and must not be used at all.

Judging by post & history. They are just a troll. As for this article. I don’t understand why anyone bothers sharing it. It is one of the most hot garbage ones I have seen. Most of this article gives arguments that are either old, have no relevance here or are just plainly cherrypicked (the jitsi one for example, open the link and see the last comment, that they quoted). Most things are also application side issue with no relevance for wayland devs. “Oh my app does not work in wayland? Must be wayland’s fault!” This is a rubbish logicless argument. If one wants to not use Wayland, they are welcome. But things like “Boycott Wayland” are irritating to those who do want to use Wayland because they know how Xorg is.

These Privacy Policies are likely only for their website element.io considering it mentions ‘service’.

In the app itself you can disable ‘Send analytics data’ in ‘Settings/Security & Privacy’ and it sends no data whatsoever to the Devs.

I just surveilled the network traffic of my installed Element client and observed that it makes 0 connections to ‘element.io’ or ‘matrix.org’ or any other element-affiliated websites. The only connections made were to my instance server at a different service. So there is no possible way element can log my IP address.

If you’re still skeptical of the Element Desktop App then you can alternatively:

• Use a fork like SchildiChat which I personally use.
• Fork the Element Client and modify the code to suit your needs.

Again, Element is open source, whether or not it makes requests to the element service to purposefully log your IP address even if you do not use the official service can be verified by just auditing the code. (Good Luck with that, or just find a previous audit report on the web)

If you’re still skeptical and want to continue using the Element Desktop app. Just block element.io and eliminate any possibilities of the app phoning home.

Vague question. I will assume you log into and use the official Element web-client instance (https://element.io/). It is safe to say it logs IP Addresses for whatever amount of time similar to any other website on Earth that you connect to which is fundamentally obvious.

To mitigate this, as in to not make Element log your IP address, you have several options:

• Use a non-web client (desktop, mobile). (Only your instance server can log your IP)
• Use a a self hosted instance of the Element Web-Client. (The server self hosting it can log your IP)
• Self host your own web client and use it. (Only your instance server can log your IP)
• Use a different Web Client. (That server can also log your IP)

The rest depends on how the server you connect to, handles IP address logs. Some servers may retain it forever, some may remove it in a few days or weeks. Check up on your server’s rules & regulations (incl. Privacy Policies) or contact your server administrator.

Artix Linux (w/ Runit) & Void Linux. Interestingly although I started using Linux from Jan 2022, I have used these 2 distros 95% of that time. The rest 5% being Endeavour OS on which I started my journey into Linux.

Due to older hardware and my natural curiousity to learn more about the System. I switched to Artix very early into Linux. The Runit Init system and the fact I chose a base iso (i.e. everything in the system apart from the Core was hand picked and configured by me) made my PC very fast and flexible. I found it quite inconvenient to work and learn w/ and in EndeavourOS. Artix provided me that canvas and it helped me a lot. One possible future con might be that I find it a bit more effort to troubleshoot more popular Distros, in case I need to, because I rarely use non-tui or non-cli programs and I have never worked on Systemd. Fortunately there are always the Arch Wiki or the Program Manuals.

I switched to Void Linux from Artix because Artx, being Arch-Based was a bit unstable whereas Void is a stable-rolling release, sort of like a middle ground between Debian and Arch and so it fits my dynamic. Otherwise it is as good as Artix in other cases.

People’s War until Communism.

Kenshi Bugmaster vibes

It will certainly be a Mega-bite…