That type of art you can find by using proprietary Nvidia drivers on GNU/Linux under Wayland.
Another time I wanna say thanks to Nvidia to make their software incompatible with adequate people.
Another time I wanna say thanks to Nvidia to make their software incompatible with adequate people.
💩1
In case you want to speak, there's a bunch of mine OT chats, all of them are nice and cozy
Ukrainian OT - @YachaOT
English OT - @YachaENOT
German OT - @YachaDEOT
Ukrainian OT - @YachaOT
English OT - @YachaENOT
German OT - @YachaDEOT
💩1
Today I have installed MobaXterm, one of the best programs from Windows, on my Arch setup using @usebottles. That thingy is super nice and requires as minimum configuration as is possible for that.
Go write @FrancescoMasala hello from me, he's from the Bottles team and my friend 😎
Go write @FrancescoMasala hello from me, he's from the Bottles team and my friend 😎
💩1
Forwarded from yachu
The message of OrangeFox Recovery project for miatoll (Xiaomi POCO M2 Pro / Redmi Note 9S / Redmi Note 9 Pro / Redmi Note 9 Pro Max) community
It has come to our attention that some miatoll ROM maintainers, who are using a particular developer’s miatoll trees, have started to try and block OrangeFox Recovery in their ROM zip installers. This ridiculous activity is supposedly a response to their (misguided and erroneous) belief that OrangeFox doesn’t work with their FBEv2 ROMs.
We expect that the sensible miatoll community is able to understand that this type of behavior is completely inappropriate.
The latest OrangeFox Recovery release with FBEv2 support for miatoll was fully tested on all the Android 12 FBEv2 ROMs in existence at the time of release (about eight) and was fully verified to be perfectly fine on all of them. The build notes for the FBEv2 release advises users to ascertain from their ROM’s maintainer which FBE version the ROM uses, before flashing the release. See for example the XDA release.
Miatoll users should be trusted to be intelligent beings who are able to understand and follow guidelines, and not be treated as babies who ought to be prevented from using the recovery of their choice
It has come to our attention that some miatoll ROM maintainers, who are using a particular developer’s miatoll trees, have started to try and block OrangeFox Recovery in their ROM zip installers. This ridiculous activity is supposedly a response to their (misguided and erroneous) belief that OrangeFox doesn’t work with their FBEv2 ROMs.
We expect that the sensible miatoll community is able to understand that this type of behavior is completely inappropriate.
The latest OrangeFox Recovery release with FBEv2 support for miatoll was fully tested on all the Android 12 FBEv2 ROMs in existence at the time of release (about eight) and was fully verified to be perfectly fine on all of them. The build notes for the FBEv2 release advises users to ascertain from their ROM’s maintainer which FBE version the ROM uses, before flashing the release. See for example the XDA release.
Miatoll users should be trusted to be intelligent beings who are able to understand and follow guidelines, and not be treated as babies who ought to be prevented from using the recovery of their choice
💩1
Right after the war started, I see a massive amount of Russian propaganda assertion there is "nazis" in Ukraine.
I had no doubts that the restored post-USSR propaganda machine will cope with making the most absurd and idiotic statements.
So they did.
Russia is doing genocide and cancels Ukraine's culture while saying it is de-Nazification the country. Because free Ukraine is not compatible with Russia's idea fix. So far, all people that trying to protect its country and nation are "nazi" people for Russia.
However, any adequate people can understand who is "nazi" actually.
Speaking about a few of the most popular cases:
1. Azov Regiment - Azov was a Mariupol unit of the National Guard of Ukraine created in 2014, as the answer to the started war. Its logo was created in 1991 (Right after USSR collapsed) by a party named Svoboda (directly translated as "Freedom").
People from Azov Regiment were against Russian occupation and strongly fought for city's freedom for 86 days under full blockade.
You can imagine how this heroic behavior angered Russia.
2. Orange-Black flag. This flag was used by Ukrainian Insurgent Army from 1942 - 1949 years. This organization was against the Soviets, Germany, and Poland in turn to protect the independence of Ukraine.
The army included Ukrainian, Russians, and Jews.
The Ukrainian history is another battlefront, the same as Mariupol, Kherson and Donbas, but nothing can't change it's facts that the whole Ukraine's history was against Russian aggression.
At the last, I will repeat the words I said on 25th February - the current war is Russia's nation fault, it was initially responsible in selecting the government and then inaction, which is a crime too!
I'm with enthusiasm watching for Russians who are against the war and actively protesting, battling on Ukraine's side, and speaking about the situation. Unfortunately, this incredibly small part of the nation can't neutralize the other.
Until then as Russia's nation won't stop the war, I will call them as participated in it.
I had no doubts that the restored post-USSR propaganda machine will cope with making the most absurd and idiotic statements.
So they did.
Russia is doing genocide and cancels Ukraine's culture while saying it is de-Nazification the country. Because free Ukraine is not compatible with Russia's idea fix. So far, all people that trying to protect its country and nation are "nazi" people for Russia.
However, any adequate people can understand who is "nazi" actually.
Speaking about a few of the most popular cases:
1. Azov Regiment - Azov was a Mariupol unit of the National Guard of Ukraine created in 2014, as the answer to the started war. Its logo was created in 1991 (Right after USSR collapsed) by a party named Svoboda (directly translated as "Freedom").
People from Azov Regiment were against Russian occupation and strongly fought for city's freedom for 86 days under full blockade.
You can imagine how this heroic behavior angered Russia.
2. Orange-Black flag. This flag was used by Ukrainian Insurgent Army from 1942 - 1949 years. This organization was against the Soviets, Germany, and Poland in turn to protect the independence of Ukraine.
The army included Ukrainian, Russians, and Jews.
The Ukrainian history is another battlefront, the same as Mariupol, Kherson and Donbas, but nothing can't change it's facts that the whole Ukraine's history was against Russian aggression.
At the last, I will repeat the words I said on 25th February - the current war is Russia's nation fault, it was initially responsible in selecting the government and then inaction, which is a crime too!
I'm with enthusiasm watching for Russians who are against the war and actively protesting, battling on Ukraine's side, and speaking about the situation. Unfortunately, this incredibly small part of the nation can't neutralize the other.
Until then as Russia's nation won't stop the war, I will call them as participated in it.
💩2👍1👎1🤡1
As might you already noticed, @OrangeFoxChat now has topics. I activated them as part of the experiment, let's see how it goes.
💩1
Last time I am working on a new Sophie update. The main purpose of it is to cover all of the problematic places with the current Sophie:
1. Typing system - the python's duck-typing (🦆) is pretty much okay and mostly reliable, but by default, it is not anyhow checked, with Sophie which caused constant NoneType issues.
2. Parsing of text - that's the most fundamental and the most issue-rated aspect of every Telegram bot. In Sophie's case, we are having problems parsing the argument text all the time.
3. Tests - Sophie was always tested manually before releasing, and even if every case was tested during the development, that doesn't mean it wasn't broken while developing.
4. Formatting messages - apart from it being pretty easy, this is the luckiest to break, as you aren't going to test it in every case.
5. Logic, noodle and obsolete code - Sophie exists for over 3 years, and even though there was fundamental refactoring (2.0 version), was incredibly difficult to change. The current version contains 2 libraries to work with a Telegram API, and there's no way to remove one of them.
I have already published my own libraries to resolve the second and third problems:
- https://gitlab.com/SophieBot/ass
- https://gitlab.com/SophieBot/stf
Currently, there are a bunch of unresolved issues, but we're moving fast-forward!
By the way, to this day, Sophie has been used in around 10 000 chats with more than 3 million known users. And had about 5 new chats every 24 hours.
1. Typing system - the python's duck-typing (🦆) is pretty much okay and mostly reliable, but by default, it is not anyhow checked, with Sophie which caused constant NoneType issues.
2. Parsing of text - that's the most fundamental and the most issue-rated aspect of every Telegram bot. In Sophie's case, we are having problems parsing the argument text all the time.
3. Tests - Sophie was always tested manually before releasing, and even if every case was tested during the development, that doesn't mean it wasn't broken while developing.
4. Formatting messages - apart from it being pretty easy, this is the luckiest to break, as you aren't going to test it in every case.
5. Logic, noodle and obsolete code - Sophie exists for over 3 years, and even though there was fundamental refactoring (2.0 version), was incredibly difficult to change. The current version contains 2 libraries to work with a Telegram API, and there's no way to remove one of them.
I have already published my own libraries to resolve the second and third problems:
- https://gitlab.com/SophieBot/ass
- https://gitlab.com/SophieBot/stf
Currently, there are a bunch of unresolved issues, but we're moving fast-forward!
By the way, to this day, Sophie has been used in around 10 000 chats with more than 3 million known users. And had about 5 new chats every 24 hours.
💩1🤝1
Okay, so today was a pretty news-big day.
Let's start with Ukraine - Ukraine got more than 100 rockets from russia on its energy infrastructure, and many cities and areas are having blackout. You can read it basically in every news channel. My opinion is the same.
Another thing that's happening is Twitter, Elon only after 2 weeks of owning most of the twitter's actions and being a CEO already was able to make a lot of nonsense.
He's saying that Twitter does more than 1200 requests with every timeline refresh for each device. That is nonsense as much as it sounds.
He fired an Twitter's App developer that denied it.
He said that Twitter has more than 1000 "useless microservices" and he's going to turn them off.
If it wasn't done before, what changed when Elon joined?
Contabo is experiencing downtimes for more than 2 hours now. Yesterday it had a 2 hours downtime also. That's the reason why orangefox.download and orangefox.tech is down. Although the good NEWS is that the API is downloads server is UP, and sometimes, when CloudFlare is allows to use "always online" feature, you can download a release.
Apparently, one of their "microservices" was shut down
Let's start with Ukraine - Ukraine got more than 100 rockets from russia on its energy infrastructure, and many cities and areas are having blackout. You can read it basically in every news channel. My opinion is the same.
Another thing that's happening is Twitter, Elon only after 2 weeks of owning most of the twitter's actions and being a CEO already was able to make a lot of nonsense.
He's saying that Twitter does more than 1200 requests with every timeline refresh for each device. That is nonsense as much as it sounds.
He fired an Twitter's App developer that denied it.
He said that Twitter has more than 1000 "useless microservices" and he's going to turn them off.
If it wasn't done before, what changed when Elon joined?
Contabo is experiencing downtimes for more than 2 hours now. Yesterday it had a 2 hours downtime also. That's the reason why orangefox.download and orangefox.tech is down. Although the good NEWS is that the API is downloads server is UP, and sometimes, when CloudFlare is allows to use "always online" feature, you can download a release.
Apparently, one of their "microservices" was shut down
👏1💩1
The other message would be about Telegram. Recently Telegram released an update containing Topics. The feature was implemented incredibly awful.
The topics are just service messages about its creations and every user's message replying to it, so you have a chain of messages, which you need to trace if you want to know which topic the message belongs to (if you don't have a topic enabled).
For end-users create a complete mess of messages and replies on the same unsupported message over and over. Topics also share the same permissions, chats and restrictions between all of them, so it makes it impossible to change users' permission in one of a topic.
For bot developers:
This is a special section, that is a complete nightmare.
1. Enabling topics means all of the messages would be a reply, if you're code handles replies, it will handle the service message over and over, over and over.
2. In topics-enabled chats there's no way to send a message without a reply, so yes, all of the code in your bots that just sends a message to chat is broken with topics enabled!
3. There are no methods, messages or anything to detect when the topic is deleted. The code can't know whatever topic exists or now. The same with its renaming.
The topics are just service messages about its creations and every user's message replying to it, so you have a chain of messages, which you need to trace if you want to know which topic the message belongs to (if you don't have a topic enabled).
For end-users create a complete mess of messages and replies on the same unsupported message over and over. Topics also share the same permissions, chats and restrictions between all of them, so it makes it impossible to change users' permission in one of a topic.
For bot developers:
This is a special section, that is a complete nightmare.
1. Enabling topics means all of the messages would be a reply, if you're code handles replies, it will handle the service message over and over, over and over.
2. In topics-enabled chats there's no way to send a message without a reply, so yes, all of the code in your bots that just sends a message to chat is broken with topics enabled!
3. There are no methods, messages or anything to detect when the topic is deleted. The code can't know whatever topic exists or now. The same with its renaming.
💩1
The issue with Contabo seems to be fixed.
Tomorrow I'll provide a list of what can be done to negotiate such situations in future.
Tomorrow I'll provide a list of what can be done to negotiate such situations in future.
💩1