3 ms·

Great idea! A few things that bothered me though: 1. Once someone has replied to your message you can't delete the conversation. If you could perhaps implement

by hucker 16y ago

Great idea! A few things that bothered me though: 1. Once someone has replied to your message you can't delete the conversation. If you could perhaps implement a "request delete" or something, so that if everyone agrees you can delete a conversation tree? Right now my "feed" is cluttered with lots of test convos. Another solution might be having a separate .json file for every user? 2. It wasn't obvious to me how you shared files. The "Set hotkey" option in the preferences should maybe be renamed to "Set file share hotkey" or something, at least explain a bit better without having to go the FAQ. Other than that, looks good for a beta! I got a really strong "why didn't I think of that" feeling when I first tried it :)

johnw 16y ago
Frenzy author here. If you were the last person to reply in a conversation you can delete your own reply by holding down the option key. The reply button will then change to a delete button. There is still currently no way to delete an entire conversation though. I was possibly thinking of adding the ability to archive items you've seen already so they don't show again. Regarding point 2 - thanks, good thinking. I will definitely need to make this clearer as many are still confused as to how to actually share things. Most try and drag files into the message text field or onto the menu item which is not yet supported. I'm glad you like it :)
- mitjak 16y ago
  To add to the bug report thread, there is no way to get out of the very first dialogue the app presents (choose shared folder to use). If I don't select anything, I can't close the app in any way except for using Activity Monitor.
  - johnw 16y ago
    Thanks. You're the second person to report this. I will fix it next version.
- hucker 16y ago
  > I was possibly thinking of adding the ability to archive items you've seen already so they don't show again. That would obviously be the best solution. Check for duplicates in the archive.json and the normal .json and hide them or something. This would be great! > Regarding point 2 - thanks, good thinking. I will definitely need to make this clearer as many are still confused as to how to actually share things. Most try and drag files into the message text field or onto the menu item which is not yet supported. That was what I tried first as well, so it seems like it would be a smart thing to implement UX-wise :)

by hucker 16y ago

johnw 16y ago

Frenzy author here. If you were the last person to reply in a conversation you can delete your own reply by holding down the option key. The reply button will then change to a delete button. There is still currently no way to delete an entire conversation though. I was possibly thinking of adding the ability to archive items you've seen already so they don't show again. Regarding point 2 - thanks, good thinking. I will definitely need to make this clearer as many are still confused as to how to actually share things. Most try and drag files into the message text field or onto the menu item which is not yet supported. I'm glad you like it :)

mitjak 16y ago
To add to the bug report thread, there is no way to get out of the very first dialogue the app presents (choose shared folder to use). If I don't select anything, I can't close the app in any way except for using Activity Monitor.
- johnw 16y ago
  Thanks. You're the second person to report this. I will fix it next version.
hucker 16y ago
> I was possibly thinking of adding the ability to archive items you've seen already so they don't show again. That would obviously be the best solution. Check for duplicates in the archive.json and the normal .json and hide them or something. This would be great! > Regarding point 2 - thanks, good thinking. I will definitely need to make this clearer as many are still confused as to how to actually share things. Most try and drag files into the message text field or onto the menu item which is not yet supported. That was what I tried first as well, so it seems like it would be a smart thing to implement UX-wise :)