yoavz

Excellent product, congrats on the launch guys!

Correct, it's the inverse that requires disclosure by Youtube.

Still, I find it interesting. If you can't synthetically alter someone's performance to be "worse", is it OK that the NFL synthetically altered Alicia Key's performance to be "better"?

For a more consequential example, imagine Biden's marketing team "cleaning up" his speech after he has mumbled or trailed off a word, misleading the US public during an election year. Should that be disclosed?

I am not envious of the policy folks at Youtube who will have to parse out all the edge cases over the next few years. They are up against a nearly impossible task.

https://novehiclesinthepark.com/

Most interesting example to me: "Digitally altering audio to make it sound as if a popular singer missed a note in their live performance".

This seems oddly specific to the inverse of what happened recently with Alicia Keys from the recent Superbowl. As Robert Komaniecki pointed out on X [1], Alicia Keys hit a "sour note" which was silently edited by the NFL to fix it.

[1] https://twitter.com/Komaniecki_R/status/1757074365102084464

This looks excellent.

In my opinion, these kinds of apps are the future of data science / data analyst work. Forget no-code, just enable these professionals to work in a single programming language that they're familar with and give them visualization superpowers. The Python ecosystem has https://www.streamlit.io/ and https://gradio.app/ now. R has https://shiny.rstudio.com/. I think we'll see more.

I love that fuzzy date search use-case, will try testing that out.

Pretty cool. The embedding similarity approach makes a lot of sense. I actually this project by experimenting with computing cosine similarities of sentence embeddings [1]. But I wasn't very impressed with out-of-the-box results, and I found it difficult to set a similarity threshold for a match. QA was the second try, and the pretrained models worked better out of the box. I'm wondering if I should revisit the embedding approach now...

[1] https://github.com/UKPLab/sentence-transformers

Yep -- no calls to any API backend.

The extension feeds it context data in chunks (e.g. only one <p> element at a time). I could see TensorFlowJS BERT struggling with a single sequence of 87 KB -- have you tried breaking them up?

Thanks, really nice to hear :)

I just got access to GPT3! Have only played around with it for a few hours so far, but haven't gotten it to reliably summarize.

Nope, I've developed and hosted my own summarization API here. It does heavily rely on open-source machine learning libraries and research / datasets released by Facebook AI [1]

[1] https://ai.facebook.com/research/publications/bart-denoising...

https://readable.com/ is an interesting tool I came across in my research you might be interested in. It relies on the Flesch–Kincaid readability tests [1] and has found sustained usage.

Actually, now that I think about it... this might be a good source for bootstrapping further training data.

[1] https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readabi...

Interesting take because there is a school of thought that comes to the opposite conclusion: emails should be more like text messages: http://five.sentenc.es/.

I think the most interesting part of this problem is the ambiguity in desired result. Emails are inherently unstructured text data, which results in conflict about how people want them to look like.

Yes, you are correct -- I linked to this research on the frontpage as a citation.

The original inspiration and example featured on the website was from a blog post on cold "welcome" email copy: https://www.gkogan.co/blog/increase-reply-rates/.

I'd love to test it on more marketing emails, or content marketing -- these seem to be the two applications with the most direct ROI.

Good looking out! Will fix that.

When I was researching this product area, I found a bunch of similar tools that summarized on the inbound side. I thought it would be more interesting to experiment on the outbound side as the main initial focus, which I haven't seen.

I do have a generic popup that you can to summarize any passage, so you could copy-paste some long passage (email, article) to piggy back on the functionality. But it isn't tightly integrated into the Gmail UI as of now.

Interesting. I have a different experience than you -- I often find myself writing an email that's way too long and trimming it down later.

For the design of this tool, it was important for me to "not get in the way" if you're already writing a short email. That's why I designed the widget so that it will only appear in your gmail window if you go over 100 words. It can serve solely as a "reminder" for the rare cases you might go over... almost like a training to help you form short email habits over time.

Author here.

If you're talking about https://www.gkogan.co/blog/increase-reply-rates/, this was a primary inspiration for this project -- I even stole the name ;)

Woops! Yep, Model Zoo is somewhat of an overloaded name.

Hey Dmitry!

Good to meet you -- I'm a big fan of DVC. In our implementation, we've taken the approach of conforming to the standards (typically open-source) set by the frameworks for serialization (for example https://www.tensorflow.org/guide/saved_model). In our API design, it was important to integrate at the framework level (e.g. a tf.keras.models.Model object) for our client libraries. If you're using one of the widely available frameworks that we support, this results in a simple API where the serialization / deserialization is more of an implementation detail. If you're using a custom or rarer ML framework with an unstandardized serialization format, an open-source approach might work better.

Hope that was helpful!