Create a new tab on Twitter for Gender navigation specifically

[mvidonne]

For ads with "targetingType" : "Gender", I would like for 1 "targetingValue" : "Men" 2 "targetingValue" : "women" count how many are targeting me through Gender (M/W) and percentage of all ads what were the criteria?
by keywords, interest, Follower look-alikes, Interest and conversation topics ex "targetingValue" : "Men" --> "targetingType" : "Interests" "targetingValue" : "Leadership" x time "targetingValue" : "Women" --> "targetingType" : "Interests" "targetingValue" : "Fashion" x time

are there common criteria between the 2 Gender

[mvidonne]

@Shalf any comment?

[pdehaye]

Dev resources are previous and should be allocated according to a structured process.

[Shalf]

Am a bit puzzled here. There is a momentum on Twitter with specific targeting (ads, semi-automated moderation, coordinated raids by masculinists) issues at women and non-binary people.

Shouldn't that kind of enhancement proposal be reviewed by devs, and for instance in that case, put into "backlog" at least, instead of closing and asserting (falsely imho) this is not even a topic? I get the "not urgent". And this could be important.

[pdehaye]

I didn't say it was not a topic. It is. And yes it could be important.

I commented on the process, which certainly is not that @mvidonne submits an issue and then draws you in this.

[Shalf]

So that should have been a "discussion" github-wise, and not an "issue", and should we transform it into one?

MP and I did had a short coffee-break prep-talk about this before she posted, so on my side, it was OK and felt organic regarding process.

Broader scope: Where on Hestia's github (and is github the right tool, providing webhooks and sending issues to devs is taken care of) should biz people talk about their stuff (before it becomes a company/dev topic, and above all if it never needs to become one)?

[Shalf]

Yes, transforming after "broader scope" in its own discussion 😏

[Shalf]

Back on topic, why I was asked to contribute here:

My wife and friends are considering starting a data collective re: twitter moderation/censure on women (with or without PDIO); I'd contribute, and LQDN's lawyer Alexis Fitzjean Ó Cobhthaigh could too.

Hence my involvement.

[pdehaye]

Broader scope: Where on Hestia's github (and is github the right tool, providing webhooks and sending issues to devs is taken care of) should biz people talk about their stuff (before it becomes a company/dev topic, and above all if it never needs to become one)?

On the clients github. And this might get promoted to the main board and given visibility to dev when deemed relevant by bizdev - and only then.

[mvidonne]

@pdehaye If I wrote this issue, it was to open up new perspectives, particularly in the context of partnerships with academics, and to see if the hypotheses of gender bias could be verified with twitter data. So my goal was clearly business oriented and not to overload the dev...

[Shalf]

Request to move this to "internal discussion" actually to be quietly and privately upcycled there please (since there is no "discussion" tab in "clients" if I get that right, and this is not yet a client's need translated into a feature request/issue) (do not have rights in this repo to do it myself) @pdehaye

[mvidonne]

Another perspective for all Horizon Europe grants: MANDATORY: explaining how the gender dimension relates to the content of the planned research and innovation activities