2,836 karma · joined December 19, 2008
Email: nick@nicksergeant.com Website: https://nicksergeant.com
The app performs its functions entirely client-side except for the job search to JSearch, which only requires the company name.
> What you choose to upload to JobsByReferral.com is entirely up to you - you don't need to upload the entire ZIP. You can upload the Connections.csv-formatted file after you review it. You could also obfuscate person names if you'd like, before uploading.
> We also do nothing with your data. You can verify the app does not send your data to any backend endpoints _except_ for company name (so that we can find jobs at that company).
Edit: we've added some privacy details here: https://jobsbyreferral.com/privacy
Edit: seems like this is only the "Classic Search", and presumably may disappear once "AI search" is no longer optional?
> Download my data > Your LinkedIn data belongs to you, and you can download an archive any time or view the rich media you have uploaded.
What you choose to upload to JobsByReferral.com is entirely up to you - you don't need to upload the entire ZIP. You can upload the Connections.csv-formatted file after you review it. You could also obfuscate person names if you'd like, before uploading.
We also do nothing with your data. You can verify the app does not send your data to any backend endpoints _except_ for company name (so that we can find jobs at that company).
The approach we've taken here is that you upload data that you're comfortable uploading. You don't have to upload your entire LinkedIn ZIP archive -- you can just upload the Connections.csv file (which you can review before you upload).
It's powered by https://rapidapi.com/letscrape-6bRBa3QguO5/api/jsearch, which is a little pricey, so I'm trying to decide whether to put more effort into the project (I'd have to charge _something_ to offset the costs).
> By training AIs to fight and defeat other AIs we can perhaps preserve a healthy balance in the new ecosystem. If I had time to do it and if I knew more about how AIs work, I’d be putting my energies into building AIs whose sole purpose was to predate upon existing AI models by using every conceivable strategy to feed bogus data into them, interrupt their power supplies, discourage investors, and otherwise interfere with their operations. Not out of malicious intent per se but just from a general belief that everything should have to compete, and that competition within a diverse ecosystem produces a healthier result in the long run than raising a potential superpredator in a hermetically sealed petri dish where its every need is catered to.
It's honestly been a nightmare, and I wish I had just built in Django instead. The Tailwind 3 -> 4 migration was probably among the most painful, which I was not expecting.
I really like the idea of contributing those photos back to OpenStreetMap actually... right now I have Google Maps on profile pages but only because we absolutely need the Google Places API for accurate hours (that's really the only spot businesses update current hours at the moment). But I could see swapping for OSM at least for maps in the near future.
We launched our first location last week and have had a great response so far from business owners and residents alike: https://canandaigua.com With the current tech climate of AI and big tech, things have gotten so impersonal for the majority of actual people. I'm betting on communities and the small businesses that serve those communities in the medium and long term.
Did this over a few weeks in my free time and now it has all of the features of accessibility monitoring SaaS that I was previously paying $600/mo for.
:sobbing:
I hope someone builds / sells this! Instant buy for me, if so.
I too am quite fearful of the fact that I know zero kids under the age of 15 who have any interest in learning how computers work, despite being completely surrounded by them since age 8 or 9 (via school-issued Chromebooks).
I had a working and complete version of Apple MapKit JS rendering a map for an address (along with the server side token generation), and last night I told it I wanted to switch to Google Maps for "reasons".
It nailed it on the first try, and even gave me quick steps for creating the API keys in Google Dev Console (which is always _super_ fun to navigate).
As Simon has said elsewhere in these comments, it's all about the context you give it (a working example in a slightly different paradigm really couldn't be any better).
``` {% with field|contact_label as label %} <div class="relative mt-5 my-3 md:my-5"> <label class="{% if placeholders %}hidden{% endif %} bg-white absolute -top-[9px] block ml-2 px-2 text-black text-sm rounded" for="{{ form_name }}_{{ field }}" id="{{ form_name }}_{{ field }}_label"> {{ label }} </label> ```
(the "with" templatetag)
Over time these templates just became very difficult to work with. Part of that is likely also because I've been a full-time React dev for the better part of a decade, and I'm just faster with it.
About a year and a half ago I began moving everything to Next.js, and have migrated 30 sites from the Django platform and have built 20+ on the Next.js platform since building that out.
Next has allowed us to create reusable but heavily-themeable functional components that we couldn't do with Django's templating language (without a lot of boilerplate and pain), and I'm extremely happy with the move (even though I might not reach for Next on my next side project).
I do however wish I had given more attention to Astro when I was evaluating frameworks, because in hindsight it looks like a perfect fit for what we're doing. Not worth migrating now, though. Haha.