How would you handle user switching? Would users have to go through a password screen to use anything?
324 karma · joined January 20, 2015
* Focus on the policy stuff since that's your differentiator. Put it front and center, currently it's below the "trending news". Nobody needs another trending news feed. I'd cut it entirely.
* Make your differentiator hyper-obvious at a glance on the front page. Right now your above-the-fold is dominated by a wall of AI generated text. It should include a tagline for your site and visuals that people won't get elsewhere.
* Your UI screams "vibe coded" which does not build confidence. Look to other authoritative sites for visual cues - consider a serif for headlines, make your spacing more thoughtful and consistent, reduce or remove your border radius.
1. Do you see any downsides to storing your graph as markdown files on filesystem, rather than, say, a graph DB? I have little experience with either but I imagine there would be perf advatages to certain operations on a graph DB at least?
2. If you're using Obsidian-like .md files, why not use the Obsidian format? I bet some folks would love to have an AI coworker helping build and maintain their Obsidian vault.
Isn't there something better to aspire to?
> Initially, when the destinations were divided into separate services, all of the code lived in one repo. A huge point of frustration was that a single broken test caused tests to fail across all destinations.
You kept breaking tests in main so you thought the solution was to revamp your entire codebase structure? Seems a bit backward.
The fact that they don't allow you to use their service to scrape their own domain, tells you something about their ethics...
That, or just use Airtable as a backend, if you can get away with it.
Mostly I agree with you though, I got swept up with lots of "recent tools & frameworks" projects and I really miss the Django admin. Django+HTMX has always seemed like a tempting option.
I do get your point though, it would be nice if this was not an NC license
I see why you're doing it, but it also opens up a whole avenue of new types of bugs. Now the dataset itself could have consistency issues if, say, the unpacker produces different data based on the order it's called, and there will be a concept of bugfixes to the unpackers - how will we roll those out?
Fascinating.
Clever.
[1](https://chesspathways.com/chess-openings/kings-pawn-opening/)
Side note: supposedly this is the first cohort of this course, so how do you already have testimonials?
Bad actors will now be working to scam users' LLMs rather than the users themselves. You can use more LLMs to monitor the LLMs and try and protect them, but it's turtles all the way down.
The difference: when someone loses their $$$, they're not a fool for falling for some Nigerian Prince wire scam themselves, they're just a fool for using your browser.
Or am I missing something?
From there it's the important part: discussing, documenting, and making sure you're on the same page about what to actually build. Ideally, get input from your actual customers on the mockup (or multiple mockups) so you know what resonates and what doesn't.
It was generated as part of this PR to consolidate the metadata.json files: https://github.com/BlueFalconHD/apple_generative_model_safet...
The example photo on Wikipedia includes the rhyming words but that's not how it would be used IRL.
I often have projects where the enrichments feature alone would be super useful: I would provide, say, a list of company names, and then use enrichments to qualify them based on location, age, founder experience etc etc.
So all an attacker has to do to avoid the tarpit is reduce their retries to 2? And they can detect all your fake devices by seeing who responds on the 3rd try?
I get that this is just one step in the cat-and-mouse game, but the brittleness of this approach makes the grandiose closing statements a little grating:
> Lightweight yet powerful, it empowers you to take control of your network security with minimal effort.
Coincidence?
All you’d need is a camera to read QR codes, a display, a few kB of storage and some pretty basic processing.
But then I guess that storage would need to be encrypted with some sort of authentication. Hmm.