- User Since
- Feb 10 2018, 9:29 AM (79 w, 6 d)
Mon, Aug 12
Sat, Aug 10
Mon, Aug 5
How can KDE guarantee that malicious keys aren't being served?
Sun, Aug 4
This is ridiculous, you say coordination is not enough but lydia says that's what's needed and we have enough people coding? which way is it? Own up to your mistakes instead of acting like nothing happened.
Here is a tool that may be useful with all the different components: https://github.com/cncf/landscapeapp
The irony in all of this is that I didn't even add the sysadmins back it was YOU @valorie that added them back. I only reopned the issue... like @ngraham said was fine... Find another excuse to rag on me.
This is getting ridiculous. You took the time not to respond to what I said but to instead patronizingly rag on me even more. What was extremely rude was having an open issue be ignored for a year then having it patronizingly closed without discussion. @ngraham saying It's perfectly fine to reopen it, @valorie says it was extremely rude. You can't have it both ways.
Fri, Aug 2
Could colors be moved up together with the other 'theme-ish' items in preparation for T11052 (there is already a kcm module that is rough around the edges but works)?
Thu, Aug 1
Functionally it looks good to me, there are a few improvements/optimizations that can be made for example 16 and 22 have unnecessary attributes such as:
Tue, Jul 30
I noticed that only the 22px icons use the viewbox, is this intentional?
Mon, Jul 29
Besides night mode and color correction this can also help test how something looks for different types of colorblindness, it can make it easy to make sure everything looks nice in those cases.
Sun, Jul 28
@johan.boule you are talking about two things if I understand you correctly: inefficiency and inconsistency/bugs. If there isn't an issue open for the konsole issue, you should open one or join the discussion because everyone agrees that manpages should be readable. As for efficiency: where do you feel that Breeze is lacking compared to "classic" themes? Maybe there is a way of improving that too. Glad that you decided to join the discussion.
Yeah I think you are right, I've thought about it and I don't want to lead this goal. Only someone with the social capital of the big names can lead goals, everyone else can be effectively ignored with zero accountability.
@ngraham it was closed as wontfix, it's a top down decision that happened without discussion. It has nothing to do with that it wasn't visible, in fact the sysadmin made an effort to make it less visible (removing sysadmin, websites, etc.). I don't know how you don't see this as a top down decision.
Sat, Jul 27
The example of school project happened in the other task that's why I mention it. I addressed all the claims made but someone else said they made a school project about tor and the sysadmin immediately disregarded what I had to say and the ticket was removed from sysadmin grouo, that is to say it's not in the wishlist even. It means that they are done talking about it (there was no discussion at all). I don't think this represents the KDE community but what is the next step at that point?
@ngraham I see what you are saying but de facto I've been doing all the things you can expect someone coordinating a goal to do - make a coherent proposal, make the issues, track the progress, keep my eye on other projects and chime in when there are issues that intersect with the goal. The difference is I don't have the social capital of some of the 'big names' who make the decisions, so even though I might know more about a subject it might still get ignored.
At this point I think I wrote most of the actual proposal (the original one) besides the fluff, if we are talking about actionable items instead of marketing speak. When I started working on it it was just marketing speak with no way to do anything with it.
FOSS targeted due to geopolitical reasoning of Microsoft.
Jul 22 2019
It seems like these kind of malware are already being seen in the wild on linux desktops: EvilGnome
Jul 21 2019
Jul 19 2019
This is exactly kind of bad faith structural obstacles I'm talking about. Yes you removed both sysadmins and websites so it just sits there ignored. It's not even on the wishlist as is customary. But why play word games?
There was no discussion, it was made without even understanding the possibilities or how much bandwidth it would take. One of reasons given was that subdomains wouldn't work which just isn't true. It was a top down decision. I'm not too concerned with being called passive aggressive by someone I'm criticising. I'm not talking to you but to the wider KDE community. You passive aggressively removed the sysadmin task to block any further discussion and you're trying to stifle discussion again.
The KDE sysadmins recently closed the onion service task no after it stood open for 1 year with no comments. Does KDE not care about users in places such as Kazakhstan? https://bugzilla.mozilla.org/show_bug.cgi?id=1567114
I thought privacy was a goal so I put time in turning the vague privacy goal into something actionable only to see nothing happen and worse yet active pushback against improving privacy.
Yet another case of wide scale MITM facilitated by CAs but I guess KDE's sysadmins don't care about users in Kazakhstan.
Jul 16 2019
Jun 29 2019
@valorie how should this be approached from a community perspective?
This really leaves a bad taste in my mouth for contributing more, when KDE announced privacy as a goal I put a lot of time into editing the goal, creating the tasks and providing as much contribution as I could in an area where I think I have some knowledge worth sharing.
Which one of those tasks are part of our goals though? Why is this such a "top-down" decision filed with technical misconceptions @bcooksley?
Jun 26 2019
What is the argument against it?
I agree, I think it's unhelpful that an issue that was open and stood there for more than a year was closed based on misinformation. I would like to have a discussion without dismissing the concerns and insights of others, especially when one might have a misguided sense of being an authority on a subject. It gets in the way of a constructive discussion. I was trying to say that it got personal for no reason and that now the conversation isn't about how to set up onion services and the benefits that it might offer or clearing up the misconceptions about subdomains for example.
Jun 25 2019
Isn't this the same but less fleshed out as the current privacy goal?
And again I would love to hear your better ways to improve privacy and security as I've done most of the editing on the goal for the past year and haven't seen much of anything happen at all. :)
Why are you acting like this? This is the Dunning-Kruger effect in action.
Jun 24 2019
You seem to have some misconceptions about tor and onion services and the properties you get with each of them. I would be glad to clear them up.
Yes, https://github.com/alecmuffett/eotk was made to make all of this easy
Would have liked to hear some of the discussion as this has been sitting here with no discussion for more than a year. I think there must be some misconceptions because you can have subdomains on onion services (for example facebook has subdomains on their onion service) and as for referring to kde.org I think a simple regex can fix that pretty easily (the same thing that is done to http:// links). Users of tor browser can and will prevent third-party connections if that is what they are worried about, there's a very nice security slider where you can set that.
This blog post seems relevant: https://www.inkandswitch.com/end-user-programming.html
Jun 23 2019
Jun 20 2019
Why not both? Removing consistency for no reason doesn't make any sense to me.
Jun 19 2019
Jun 18 2019
I think that is very valuable and i like your response, it's well articulated and I understand what the main focus is.
Jun 17 2019
@neofytosk Can you give some explanation?
The problem is that the proposal doesn't tell us how we should prioritise differently. Because people have different experiences (broadly speaking) they will think different things should be prioritised so with setting the goals we are already trying to have a discussion on what we want to prioritise. So just saying "prioritise the things that are good" is too vague because good means different things to different people.
Jun 15 2019
Jun 14 2019
An option is to add per project watchlists so we have more of an overview of the changes on a per project basis which can be reviewed periodically.
Jun 13 2019
@crozbo I just think saying i3 support is a better way to summarize what you want to do, it's a nice clear goal to work towards that would satisfy the functionality that most people want. I'm not hung up on the implementation details.
I think there is merit in having a robust tiling experience out of the box no matter how it is implemented, whether baked into kwin or through kwin scripts. Having support in Plasma for it would also mean then exposing it to the user in a discoverable way and documenting it (some users might have never heard of tiling but would like it), I think there is something to be said about it being an accessibility feature as well.
What would this look like in a language that isn't LTR? Would it be better to maybe have it on the right side in that case?
Jun 12 2019
My suggestions for this proposal would be to focus it around Organizations which is far more general instead of Big Enterprise and change the "how would we know we succeeded" to something like "we see more distributions switch to Plasma as default" or something like that instead of naming specific ones. We have no control over whether a certain distribution picks Plasma because those choices are not just based on popularity or how good our software is - for example Red Hat is heavily involved in GNOME and I don't see them switching to Plasma even if a lot of people on a forum asked for it.
@skadinna really nice work! it's clear what needs to be done now :)
Jun 11 2019
On trackpads we already have two point touch. If we want to introduce a different/special case for touch screens we should also discuss whether it should be a special case or if for example long press should be right click on trackpads as well.
Jun 10 2019
An issue I see is that on the second view there is no indication of what ISO image you selected, so if you selected the wrong file you have no idea of knowing.
Adding VDG because we will need a design for this
The best implementation of this I've seen is fw-daemon
Should we have input methods as a goal or maybe something a bit more broad such as Accessibility?
Hey, thanks for taking the time to write this! I have to say though I think this is way too specific to be a Goal. If you search around here and the bugtracker you will find multiple discussions about this and what the current roadblocks are.
I created T11052 to discuss the idea of an Accent Color system and related components for Plasma.
Tangentially related; I created T11052 to discuss the idea of an Accent Color system which would kind of fill the void of the additional color schemes we don't ship anymore with Breeze ;)
Jun 9 2019
Radically improve the UX for switching between common panel UIs (e.g. Windows XP style task var vs Dock). This probably needs its own Phab task.
Jun 7 2019
Really good effort, here are two relevant links: https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO