feat(gathering): linkedin button

[omBratteng]

No description provided.

[pulumi]

🍹 The Update (preview) for dailydotdev/api/prod (at f8b22f7) was successful.

Resource Changes

    Name                                                   Type                           Operation
~   vpc-native-calculate-top-readers-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-deployment                                  kubernetes:apps/v1:Deployment  update
~   vpc-native-update-tags-str-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-update-source-tag-view-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-images-cron                    kubernetes:batch/v1:CronJob    update
~   vpc-native-post-analytics-history-day-clickhouse-cron  kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-gifted-plus-cron                      kubernetes:batch/v1:CronJob    update
+-  vpc-native-debezium-props                              kubernetes:core/v1:Secret      create-replacement
~   vpc-native-check-analytics-report-cron                 kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-users-cron                     kubernetes:batch/v1:CronJob    update
+   vpc-native-api-db-migration-ff907548                   kubernetes:batch/v1:Job        create
~   vpc-native-generate-search-invites-cron                kubernetes:batch/v1:CronJob    update
+-  vpc-native-k8s-secret                                  kubernetes:core/v1:Secret      create-replacement
~   vpc-native-update-trending-cron                        kubernetes:batch/v1:CronJob    update
~   vpc-native-generic-referral-reminder-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-bg-deployment                               kubernetes:apps/v1:Deployment  update
-   vpc-native-api-db-migration-f28828c6                   kubernetes:batch/v1:Job        delete
~   vpc-native-personalized-digest-cron                    kubernetes:batch/v1:CronJob    update
~   vpc-native-validate-active-users-cron                  kubernetes:batch/v1:CronJob    update
~   vpc-native-sync-subscription-with-cio-cron             kubernetes:batch/v1:CronJob    update
~   vpc-native-update-tag-recommendations-cron             kubernetes:batch/v1:CronJob    update
-   vpc-native-api-clickhouse-migration-f28828c6           kubernetes:batch/v1:Job        delete
~   vpc-native-temporal-deployment                         kubernetes:apps/v1:Deployment  update
~   vpc-native-update-views-cron                           kubernetes:batch/v1:CronJob    update
+   vpc-native-api-clickhouse-migration-ff907548           kubernetes:batch/v1:Job        create
~   vpc-native-post-analytics-clickhouse-cron              kubernetes:batch/v1:CronJob    update
~   vpc-native-ws-deployment                               kubernetes:apps/v1:Deployment  update
~   vpc-native-daily-digest-cron                           kubernetes:batch/v1:CronJob    update
~   vpc-native-clean-zombie-user-companies-cron            kubernetes:batch/v1:CronJob    update
~   vpc-native-update-highlighted-views-cron               kubernetes:batch/v1:CronJob    update
~   vpc-native-update-source-public-threshold-cron         kubernetes:batch/v1:CronJob    update
~   vpc-native-personalized-digest-deployment              kubernetes:apps/v1:Deployment  update
~   vpc-native-private-deployment                          kubernetes:apps/v1:Deployment  update
~   vpc-native-clean-stale-user-transactions-cron          kubernetes:batch/v1:CronJob    update
~   vpc-native-hourly-notification-cron                    kubernetes:batch/v1:CronJob    update
+-  vpc-native-debezium-deployment                         kubernetes:apps/v1:Deployment  create-replacement
~   vpc-native-update-current-streak-cron                  kubernetes:batch/v1:CronJob    update

[capJavert]

I think for me overall this is good but I would ideally expect much better validation of Cores assignment or make it manual after some time so that Cores farming is not easy with many new accounts.

For example user create account, shares linkedin, gets Cores and then moves them through awards to single account. Some ideas:

• require minimal account age, 3-6 months?
• require higher reputation, eg. 2000 reputation

[omBratteng]

It's a manual process now, cores doesn't get assigned until the referral is "accepted" (which we have not defined yet how it should be done), so until then, it's just in a pending state.

[capJavert]

Perfect