RFC salary ranges / filtering for data in general

[BMaxV]

Hey everyone, I found your website and this is something I would want if I were to use the site seriously, as well as other data filters.

Cool project!

Summary

Add "soft syntax" for salary ranges for posters and a filter for job searchers. For transparency and data analysis of posting.

Basic example

I am looking for a job and want to not view jobs that are below X money.

I am posting a job and can afford to pay X money and want to attract talent with higher pay.

#range 50-60k[currency symbol]

Motivation

It is something I would want when looking for a job and I would imagine it's something transparent employers would want to be transparent about as well.

Also I think it's required information in some countries?

Detailed design

Define

\#[key] [value & format]

that you look for and parse. Also, possibly an interactive box to paste things into, that will parse the input and give a traceback of the data that is parsed or isn't parsed and what the problem is.

E.g. "#range 10,000" using a comma instead of a point.

Please reference Domain
Model (TODO write)

That link doesn't work (yet?)

Drawbacks

Why should we not do this? Please consider:

• feature bloat, possibly. If people only use this to link to job postings on other sites, it's not that useful.
• requires acceptance by people
• coding the parser for the permutations of how to write numbers could be annoying.
• no idea about costs on your end, but it would probably require some additional space and infrastructure.
• Offering this will eventually lead to spam for the one who posts this, I think? So, some sort of delisting is required as well.

Alternatives

What other designs have been considered? What is the impact of not doing this?

Possibly no impact. If the employer wants to release that information, they can do so whereever they "properly" post it and that info could probably be crawled and found.

Adoption strategy

If we implement this proposal, how will server admins adopt it? Is
this a breaking change? Does it require coordination with third party
clients? Does it require coordination with other Fediverse projects?

The idea would be for people to be able to just add #range [number or range] as a text into their posts and you looking for that when you search through posts. There is no special data or interactions, just reading the text as before.

How we teach this

What names and terminology work best for these concepts and why?

Advertise that people can do it on your website somewhere. Possibly create a form that people can use to enter data, with output being a string that includes the data in a format you can parse.

[berkes]

Thanks for the very well detailed and thought out RFC.

It came at a bad time, though. Just when we were taking some distance. Hence the late reply. Sorry for that.

We've taken that distance and time to reflect and decided to stop the project alltogether: https://fosstodon.org/@flockingbird/110622645831178530