reply on: Heads up: ~jobs ranking and cost has changed \ stacker news ~bitcoin

pull down to refresh

0 sats \ 6 replies \ @cointastical 4 Mar 2022 \ parent \ on: Heads up: ~jobs ranking and cost has changed bitcoin

And, a few additional questions.

1.) When the job is status STOPPED (because I stopped it), should others still be able to see it? Here's an example: Job #13386 has STOPPED, but you can still see it.

I could understand this if the status was NO SATS, ... sure -- let's say the link followed by the prospective applicant was from a Tweet, and the listing ran out of funds, then yes -- it should be still visible to them.

But for STOPPED, I'ld think the page would have a "This job is no longer listed" message or something like that.

2.) Will there be any accounting so I can see the charge to my wallet appearing in my Satistics? I know since the charge occurs every minute, there won't be a transaction for each charge, ... but maybe at the end of the day an entry is added to wallet history under Spent that tells me the sum of my payments for that 24 hour period to ~jobs for my listings.

10 sats \ 5 replies \ @k00b OP 4 Mar 2022

I can 404 STOPPED and NOSATS jobs. Oversight on my part.
Definitely. It’s just weird ux wise as you point out. The solution is likely solving a gaps and island problem with the wallet history - ie grouping per minute spends together around gaps created by other spending activity

0 sats \ 4 replies \ @cointastical 5 Mar 2022

I can 404 STOPPED and NOSATS jobs

I would think that's expected on the STOPPED. But for NOSATS, are you sure?

Let's say the link is followed by a prospective applicant who saw a link to the SN Jobs post from a Tweet. But the listing ran out of funds before that, and the job poster / employer has not yet realized that.

Wouldn't it be better for the employer if an unfilled posting results in the maximum number of qualified applicants? (and thus, they would be more likely to use the SN Jobs service again, in the future ?)

And even if the employer ignored the part about changing to STOPPED after it is filled or for whatever reason, wouldn't it be good for the employer to continue to receive applications from the listing? Again, they would be more likely to use the SN Jobs service again. And if it was still unfilled, but still receiving applications (e.g., from the link shared in a Tweet), maybe that would persuade the employer to top up and resume the ad on SN jobs!

Simply hosting that job listing page beyond when the employer's balance runs out doesn't cost SN anything additional, and provides value to the employer. It's the inventory (space for a listing appearing in the ~jobs results) that is what is of value and thus rightly requires payment by the employer to remain in that list / results.

So that's my suggestion is only stop serving that page when the employer explicitly sets it to STOPPED.

10 sats \ 3 replies \ @cointastical 5 Mar 2022

And as far as 404, ... when I see a 404 response to a link, I think someone screwed up. Either the link was bad, or the site is having issues.

Why not instead a nice, friendly message like ...
"Sorry, this job listing has been removed. We have many others -- check them out!". (with a link to ~jobs).

10 sats \ 2 replies \ @k00b OP 5 Mar 2022

I think having a specific missing message is a better UX - great catch.

For NOSATS, yeah I think it should hide the job else you could just create a job for a minute, then get half the value prop - being discoverable by google and having a link hosting your job on our site. Open to changing my mind but I think handling STOPPED and NOSATS the same is the move for now.

15 sats \ 1 reply \ @JobsX 10 Mar 2022 freebie

Just a reminder -- using the URL, the site still shows the listing , whether active, STOPPED or NOSATS.

5 sats \ 0 replies \ @k00b OP 10 Mar 2022

Thanks! I forgot about this