🧵 👆🏼
@Bro666
>> Why not start there? All you need is an account on bugs.kde.org and you will also revive bugs that may have flown under the radar and contribute to getting them sorted once and for all.
As mentioned before, I have already done that. it is all public information and you can go and check.
🧵 👆🏼
@Bro666
>> developer accounts are approved all the time.
Not mine! So "all the time" is as false as it gets. No one communicated to me that I need to provide certain information or details!! pure radio silence. So let's be factual.
>> when it comes to bugs, which seems to be your main concern, there is a lot you can do without a developer account.
Bugs **and** feature requests are my main concern.
🧵 👇🏼
@Bro666
I sense some hostility here which I don't appreciate.
>> A developer account, the kind of account that gives contributors full access to GitLab, gives the power to do a lot of damage too.
That sounds very wrong. All PRs (in case of Gitlab MRs) should be ultimately approved, so I cannot see why your Gitlab is vulnerable where as all other instances of Gitlab, the Github and all instances of Forgejo are nor susceptible these "damages"!
🧵 👇🏼
@Bro666
Thanks for your invitation, then I cordially and officially invite you accept the KDE Invent (Gitlab) access which I requested months and months ago.
It is not right to randomly throw such messages and accuse people of not contributing when the contribution is locked behind a login screen that needs approval and the access is never given. I mean you can, but it is, unethical and unfriendly.
For now all I could contribute is by donating money (check the records, it's public).
@Bro666
Those are bugs reports and feature requests for all KDE applications including plasma and also including Kate, Yakuake, Konsole, Kmail, rkward ...
Not complaining here, but none of the bugs I ever reported or I'm following were addressed. To me this sounds like a good place to focus on, because these are issues that the community have faced or the suggestions they have come up with.
@kde@floss.social
I know ✋I know ✋ there is already a lengthy list:
@Pantherina
I agree, although there are three things worth mentioning:
-
The conventional Android is not that opensource. It is bundled with tons of proprietary Google stuff. That's why de-googled Android does not provide as smooth experience.
-
Android does not restrict you to "only OpenSource" components. WhatsApp for example is widely used and is not FLOSS.
🧵 👇🏼
@Pantherina
I'm sorry that this bug have happened.
But did you, or whoever faced this bug, "eat" it with your "teeth" though? No they didn't. Why? Because like any proprietary software, OpenSource tools also come with certain terms and conditions that user is expected to read, digest, understand, accept, and then utilize the tool:
https://fosstodon.org/@Mehrad/112128648273530651
User had all the possible chance in the world to read the code and make sure it doesn't do what it's not supposed to do.
🧵👇
One obvious fact that I though would never need to be reiterated (but here we are):
Almost all OpenSource licenses approved by OSI and/or FSF have "Disclaimer of Warranty" clause in one way or another. This is from MIT:
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
https://opensource.org/license/mit
More examples:
https://opensource.org/license/gpl-3-0#section15
@Pantherina
Yeah, by the same logic lets also call hotdogs dangerous because people have also choked on them!
https://nypost.com/2023/07/11/4-year-old-girl-dies-after-choking-on-costco-hot-dog-report/
At some point we should understand and agree that PEBKAC is a real thing. Logic dictates not to blame Linux and hotdog, and instead understand the consequence of using unverified/unvetted software.
Tbh, I'm still super impressed with smoothness of :kdenew: KDE Plasma5 on :postmarketos: PostMarketOS on such an old phone (Samsung Galaxy A300FU). Truly an achievement. Of course it is far from optimal (e.g notifications can clutter the screen and their close button are out of bound of the display).
Well done @kde@floss.social , @kde@lemmy.kde.social and @postmarketOS 👏🏼
@Lenni
You can, and also @flameshot provides more tools and colors, but it is a "still frame" because Flameshot captures the screenshot first, and then let the user to annotate it. Therefore it is not useful if a video is playing in the background or slides are changing or moving through the code.
Side note:: I'm one of the maintainers of Flameshot ;) and I'm glad you have found it handy :ablobcatattention:
@Pantherina I don't know what you mean by Autoremove, but here are some tips:
Undo the last line by Meta+Shift+F12
Clean everything by Meta+Shift+F11
In the latest version (at least the one that is in KDE's git repo, users can change all those keybindings. Checkout mousemark.kcfg and mousemark\_config.ui files in this link:
https://invent.kde.org/plasma/kwin/-/commit/46807b1a72f1d760b52b92a574face4a7a509a39
I don't yet have #Plasma6, so I'm not sure if it is already shipped there or not. But the code is done and it is just the matter of time :)
@Larvitz
It seems the Github mirror is way out of date. I checked the https://invent.kde.org (the KDE's Gitlab instance) and found out that during the past 6 months MouseMark has received some updates, especially about the logic of arrow drawing:
https://invent.kde.org/plasma/kwin/-/commit/46807b1a72f1d760b52b92a574face4a7a509a39
But as far as I can tell, even if you have the latest build from the latest source code, the general process of drawing is the same:
https://invent.kde.org/plasma/kwin/-/blob/master/src/plugins/mousemark/mousemark.cpp#L178-192
@Larvitz
Basically this is the chuck of code responsible which is how I figured out how to draw an arrow:
I also don't see any part in the code that can throw the error. Considering that this is such a simple code and have not changed for about a decade, I don't think the issue is wayland/x11 either.
I suggest filing a bug report with the screenshot of the error and etc.:
https://bugs.kde.org/buglist.cgi?quicksearch=mousemark&list_id=2631036
@Larvitz
😅 😂 Yeah, That's why I explicitly explained the arrow-drawing process in my toot 😉 I also had this problem and figured out how to do it today. The keybinding and behavior for arrows is poorly designed imho and I hope KDE folks improve it.
But for now, this is how you should draw an arrow:
- move your mouse where you want the arrow head to be
- press **and release** Meta+Ctrl+Shift
- move your mouse to where the tail should be
- repeat step 2
One of the KDE Plasma features I use almost in daily basis is the MouseMark.
Go to your settings, in Desktop Effects, Enable the MouseMark (you can change the settings of it in the button in front of it). Then press Meta+Shift and move your mouse to doodle, or press and release Meta+Shift+Ctrl to define beginning and end of an arrow (it will draw the rest.
Interestingly enough, it have been in Plasma for the past 16 years:
https://github.com/KDE/kde-workspace/tree/master/kwin/effects/mousemark
@kde@floss.social
The bottom right is great. Modern, warm, enough contrast, ... . Imho going with plain blue or green backgrounds are becoming a cliche in KDE and tbh a little bit old-fashioned.
Mehrad :kde: :emacs: :rstats: @fosstodon.org Bioinformatician🧬 during the day, Data Scientist📈 in the afternoon, and Linux🐧 hobbyist at night. Federation and E2EE advocate. Interested in Data Analysis, Machine Learning, and FOSS/FLOSS.
Languages: 🗣 |\_ 🇮🇷: Native |\_ [🇺🇸🇬🇧]: Almost native |\_ 🇫🇮: In Progress 😅
🤖 |\_ :rstats: : Primary |\_ :python: : Know my way around |\_ 🐪: Oldie but Goodie (esp. regex) |\_ :rust: : n00b
Some of my interests in machine-readable format: \#Rstats #Bioinformatics #MachineLearning #OpenScience