Yes, thank you, I know it's not ideal now. It would make a much better impression.

I plan on adding it soon, after smoothing out the internals.

Hey thanks for taking a look! Diving in now. support@anytoolhq.com routes to me, happy to chat!

edit: problem found, fixed, and tested.. let me know if you have a chance to try again

I tried creating a tool, it's been stuck "generating" for a few minutes now.

Thanks for testing - i apologize for wasting your time... But I did take a deep look at things and figured out how to make generation of tools more reliable.

If you're still interested, please take another try... I've got more visibility into logs and errors, and it should be much more reliable!

I built this little tool to hack alert/confirm/prompt into promises.

I use it everywhere. Optkit.com

Thanks! It was born from a conversation with a friend who offers Fractional CFO Services.

One of his most repeated tasks is helping clients predict their cash flow...

So, this tool to simplify and automate that process, making it accessible to everyone. Next steps are going to be exploring some revenue opportunities.

3,133.7 is a great reward!

Is it? I'm not so familiar with the specifics of bug bounty programs, but it seems like this issue could cause much more than 3k in damages if it were to be exploited.

Similarly, I'm kind of shocked that Google is only offering 30k for discoveries of remote code execution vulnerabilities on their own servers. I don't mean to trivialize that amount of money, but compared to the scope of what that kind of vulnerability could be used for it seems insignificant. There's the potential for access to internal Google secrets and private data belonging to users. Would a government not pay 10-20x for something like that?

Governments achieve code execution within Google by sending special agents to become employees of Google.

I imagine that's orders of magnitude more expensive than paying these rates for an exploit.

No it’s not! That is extremely low compared to say Apple, which doles out something like 50k for low severity bugs (source: they pretty much paid my college fees)

This is not my experience with Apple at all.

Launched a bare-bones prototype, Inbox.Dog, aiming to rethink B2B email with a sprinkle of AI—think of it as email, but with an AI-powered twist for tasks we haven't fully imagined yet.

It's rough around the edges (it literally could not be a simpler prototype), but I'm curious about its potential to evolve email beyond its current state.

Keen to explore how AI could make email a more powerful tool?

I'd love to hear your thoughts or see you give it a whirl by emailing hello@inbox.dog

Cheers,

- Jordan

Reminds me of BrewPDF.com

I have some success by telling it to not speak to me unless it's in code comments. If it must explain anything, do it it in a code comment.

I’ve been telling it I don’t have any fingers and so can’t type. It’s been pretty empathetic and finishes functions

So already humans need to get down on their metaphorical knees and beg the AI for mercy, just for some chance of convincing it to do its job.

You might be on to a new prompting method there!

I love when people express frustration with this shitty stochastic system and others respond with things like "no no, you need to whisper the prompt into its ear and do so lovingly or it won't give you the output it wants"

People skills are transferrable to prompt engineering

For example, my coworkers have also been instructed to never talk to me except via code comments.

Come to think of that, HR keeps trying to contact me about something I assume is related, but if they want me to read whatever they're trying to say, it should be in a comment on a pull request.

I've heard stories about people putting this garbage in their systems with prompts that say "pretty please format your answer like valid json".

You expect perfection? I just work through the challenges to be productive. I apologize if this frustrated you.

Could you elaborate on which functionality? I've been using SK in production since early beta, I've not run into this (yet)

To be honest I'm not a front end developer, just learned that a few things on GitHub had issues outstanding about SK issues, and avoided them after the first run-in. Massive props to Svelte to allow me to finish my project while actually, somehow, enjoying the front end development portions though!

The one I ran into: https://github.com/BulatDashiev/svelte-slider

Subtle change. I enjoy the concept and execution.