Change the algo so the Sticky job board get shuffled when caching gets flushed every hour #jobboardsearch

fix Stripe invalid Session ID error when hackers try to randomly fill ?action=stripe_checkout_success with data to force it to bump a post by checking if job exists first #remoteok

save job post feedback box to jobs.db then send only after Stripe Checkout callback and payment succesful to stop getting random spam messages #remoteok

Make a bot that shuffles non paid job boards every 30 mins #jobboardsearch

add sticker + info when airline offers stopover program with e.g. free hotel stays #yelmair

find solution for if company adds sticky (24h/7d/30d) during editing job it won’t sticky cuz sticky based on posting date not when sticky was added; solution = sticky boolean value can be a timestamp instead (0 = false, 1 = true, 1601993989 is timestamp of sticky time) and it checks that when showing stickies and resets timestamp of job to edit #remoteok (complex af)

add new code for race condition if Stripe webhooks fire twice but job already posted or bumped but use time of post or bump to check for it to ignore, so that multiple manual bumps can occur succesfully over time #remoteok

save stripe_customer_id from bundle/coupon purchase and 1) when job posted with coupon code, 2) transfer stripe_customer_id to the job posted in db, 3) so that auto_bump charges that card to bump with bump_price #remoteok

add ‘active’ stickers to active deals to not overly confuse visitors #yelmair

manage to figure out how to add sticky jobs into SQL query by doing ORDER BY max(coalesce(epoch,0),coalesce(epoch_bumped,0),(coalesce(is_sticky_day,0)+86400),(coalesce(is_sticky_week,0)+604800),(coalesce(is_sticky_month,0)+2592000))) so that we don’t need to “manually” add the sticky jobs on top with code but it just sorts it straight into db (86400 is 24h, 604800 is 7 days, 2592000 is 30 days etc.) #remoteok

add Stripe Checkout to bump job post #remoteok

raise sticky job pricing #remoteok and base it on total current sticky jobs instead of only total current sticky for month jobs

distribute jobs across queues #optimizetoolset

pre-generate bundle coupon codes for job posts when Stripe Checkout redirect happens and add stripe_checkout_session_id to each coupon code, then after payment when we get the webhook we can match it and set all those as paid (and send the email to the company with invoice) #remoteok

add 24-hour sticky upsell #remoteok

when bumping, and job has sticky set, reset the sticky epoch timestamp so it becomes sticky again #remoteok

schedule post #cardmapr

schedule post #cardmapr

schedule post #cardmapr

schedule post #cardmapr