If only this were actually real…unfortunately just looks like a dead fork of Mastodon
If it were to exist I somehow doubt it would come from a Mastodon fork.
I guess Bonfire tries to be something more fitting, but it seems too early to say whether they will be successful at that.
Wonderful idea. I see no commits in the past month. Still active?
Looks like it never was - the last two commits are merges/git issues and before that are commits from mastodon itself.
Hey, this is @haui@mastodon.giftedmc.com I think.
I like the idea of an opensource job board. Conceptually, I think the biggest conceptual issue before getting this off the ground is privacy.
Sure, most information on job boards and profiles of workers are to be public, but there is some information that should stay only accessible to certain people e.g your phone number, email address, current place of employment and other stuff should only be visible if given access. Some people don’t care about that at all and would even put their home address online, but some people don’t want to be tracked everywhere or found and contacted easily e.g you make a comment somebody disagrees with and they start dogpiling you.
I think certain information should be encrypted and only exchanged/shared with somebody you really want to share it with. Otherwise you have to put all your trust into some person hosting the instance. Right now, we do put trust in fediverse instances, but the date I’m putting out here would hopefully not make it easy to identify me. It will be difficult and maybe inconvenient to have no personal information on a job board. Unless of course the job board is just for publish jobs and won’t have public, professional profiles.
Hi there and thanks for @ing me to the discussion.
Those are my main concerns as well. This is also laid out in the readme and project plan.
The idea is to decide between three states for information: public, encrypted and off site.
Currently (on LI) your personal data is exclusively stored on LI servers (and hopefully not leaked). LI *sees* this data.
On fediwork the most sensitive data is only shared with e2ee. FW stays blind. We only see ips. Same as privatebin.
To add to this: we’re currently working on two options.
- you put your sensitive data into a secure container (similar to privatebin)
- you do not put your most sensitive data on the server (which you can of course self host) but get a request from the employer and then send this data directly to them, bypassing the server, encrypted.
This of course has other implications such as ips getting out but not storing your personal data can be a greater concern than this
https://www.forbes.com/sites/daveywinder/2025/12/26/linkedin-hack-attack-alert---12-billion-users-must-watch-for-red-flags/ linkedin seems to suffer scraping, leaks, invasions on a yearly (probably more frequently) basis
