You may recall a document on the creation of a new shared event between GNOME and KDE and today we have the people who proposed the event on the show #Linux #Podcast #OpenSource @pietrodc0 @ilvipero

Video: https://www.youtube.com/watch?v=G5iMWsRSUc4

Audio: https://creators.spotify.com/pod/profile/tech-over-tea/episodes/Bridging-The-Gap-Between-KDE--GNOME--Pietro--Mauro-e39jsm8

@BrodieOnLinux thank you for inviting us!

@ilvipero

@BrodieOnLinux are all of them still actually open? I expect that in the long run some bug has been fixed without managing the bug report, maybe without even knowing there was a bug report for a specific thing.

@jonquass appreciate your support 🙏

@tyil because I'm the software engineer behind it and I manage my software as I'm confident with to provide the best result.

Sorry but I'm done with this idiot, nonsense, attack thread with no foundations for a reason to exist if not your poor comprehension skills.

@tyil you are defending it from a software that is going to be public and open source AHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHAHAHHAHAHAHA

@tyil @mirkobrombin look, Mastodon is made for freedom of speech, not for Free and Open Source Software community only.

1st: I'm not saying I made a private/proprietary software and trying to sell it.
2nd: this is not a platform reserved to FOSS, anyway

@tyil learn the difference between developer private preview and released project.
And first of all learn to read twice, or even three times, before attacking.

If this is a free place to be: I use it as I prefer, even like X if I'd like to.

_edit: if you don't like to read me you can use the block function, I'm not going to be offended

@tyil well, that's why I kindly invite you, again, to read the post again.

I didn't say what you tried to quote. At all.

I said that I'm creating something - as a fucking software engineer - and I shared the idea with my network for hints advising that this thing IS GOING TO BE PUBLIC AND OPEN.

You are free to share your thoughts, I'm just saying that you are trying to say I'm against the idea of freedom and inclusivity while you want to deny me my freedom of sharing my stuff as I want to do.

@tyil so I can't have freedom of speech and action in a free community that leverages DEI?

ok

For those who constantly comment my "privacy choices", maybe is better if you look online for me... I have NOTHING set to private, not even my Instagram profile 😅

I have a public profile. I do give speeches and interviews. I work with content creators and influencers. Privacy is not a concern for my person, I'm already a public reference (of some kind).

@tyil please, read the responses already provided.
I use Chrome, so I start with Chrome.

about the "don't share with mega corpo", read again the post:

«Once this initial testing is done we'll make it public and publish the extension in the store.»

it's not private to "not share blah blah", it's just during this testing where I do a lot of random changes and tests on my own and the extension is not being packed for the store.

Before "attacking", read.

@nima once the Chrome version (as it is my primary browser) works: why not!

(help may be needed)

@dirk tested it, not working at all.
The git history is really AI written.
No options to personalize config like discussed in this thread

@nawanp @gabboman well, you are likely going to visit a few and for these that are not in the known list you are asked for confirmation the first time and then the base url is added to your local list (no more question added)

@wafrntest @gabboman well, already working!

@gabboman do you have a link for me?

@mitsunee a "never redirect" list.. why not!

@gabboman the fediverses I checked have the word "mastodon" in the "og:site_name" meta tag and that's my primary check at the moment.

Client developers may agree in a different meta tag and we can add it to the extension

@mitsunee we can maybe have a three-way-toggle:
- off
- silent redirect
- ask