https://github.com/aixolotls/wtx
I've been working a lot lately with parallel claude sessions in a large monorepo, creating multiple PRs at the same time.Managing worktrees manually became a headache quickly (which one has which branch?), and trying to treat them as ephemeral was slow to bootstrap each time.So I created wtx to manage worktrees for me. Now I just use "wtx checkout mybranch" and claude opens in a worktree.Under...
imwith is the selfie-GIF messaging app that makes your chats funnier. We're looking for high-schoolers to promote our app in their school.What you'll do:- Use the app and promote it among your friends. - You should be able to get your friends to keep spreading the app. - This is a chat app so most of the work will be to chat with others on the app, keep them engaged and explain the core value...
We believe that relieving users of the need for thinking of and searching for memes makes it much more accessible and fun for them and generally creates a unique experience.
One other thing we felt was lacking in other messaging platforms was a fun reaction feature, and we tried to tackle that as well - you can react to your friends messages with GIFs, which we think lets you express a wider range of laughs.
Lastly, we’re decided to opt for a button-less UX in our messaging app, so in order to send messages you basically fling from the input towards the chat. After using it for a short while we’ve found ourselves trying to fling in other messaging apps too :)
We’d love to hear any questions or feedback you have on the app.
We have built a very cool technology which can take almost any text you write and match it with several funny, relevant GIFs.We are building the funniest messaging app ever built and launching it soon. We like to laugh almost as much as we like to see our technology enable others to become more funny when chatting with their friends.We are looking to launch in US campuses on May and are looking...
1. Are there plugins for the app store and google play reviews?
2. Is it possible running your engine on arbitrary data? (it seems to cluster common themes, so I was wondering whether it can be used to show any sort of data rather than customer feedback)
> A thing that bothers me a bit is the extremely long URL...
Most platforms on which Guggys get shared either do not show the URL or shorten it. Could you say where did it bother you?
> As always there's a slight "uncanny valley" problem...
Interesting point. The thing is that if we have only the scope of the short message, such as "it's great", it's hard to predict whether you're being slightly cynical or sincere, so we try to provide with a few options to choose from.
> Let people re-caption existing Guggies
I see. It's more relevant to the website but I can think of a few ways we can do it on our apps too. We'll give it a thought.
Thanks!
We generally store necessary data for generating the GIFs within the URLs themselves. Then we use stateless servers to generate the files. These read the data and overlay the text on top of the GIF.
> Have you considered some sort of lightweight machine vision for pinning text to the scene, similar to many of the gifs in Reddit's /r/highqualitygifs / Instagram's stories?
Yes, it's in the roadmap. We used to have text effects such as the ones appearing here:
https://cdn-images-1.medium.com/max/400/1*Ws-pXgOsNkLwhVbyl9...
https://cdn-images-1.medium.com/max/600/1*YiT8QgLZ1JAr7DmjX-...
But we came to the conclusion it's too distracting. The thing is that Guggys are essentially an enriched text message, maybe even more than they are GIFs, so we want to make sure that while keeping it visually appealing, we also allow our users to send their message in a clear way, a trait we feel is absent from current GIF products.
The second part is the creatively tagged image repository. Even though tech enables now to tag objects in images, it still can't do it in a creative and funny way, so for the moment we were aiming for quality rather than quantity (I do agree that massive existing GIF repositories do not yield desired results), whereas we have plans for extending our repository significantly in the future.
The third part is also what we consider a big advantage of Guggy, and that's the image rendering engine. That allows us to personalized each request, such that different users could potentially see different results for the same texts (imagine seeing them in a font that you like, and your friend sees them in a different font, but there are also other applications for this). The images are therefore rendered on the fly per each request and are never stored.
Hope that clears up the questions you had in mind.
