(#5ravvda) @axodys Very nice! 👌 We're very glad to have you join our growing ecosystem 🙇‍♂️ Welcome! 🤗

(#o3zzt4q) @axodys Photo or it didn't happen 😆

🥳 NEW FEED: @axodys

(#ov4ki2q) @axodys Glad you like it 🤗

(#ciaj6sa) @axodys Hmmm? Like this? 😆

(#c5wd4la) @axodys What's it about? 🤔

(#x43iebq) @axodys they actually both do under the scenes but we've been trying to transition the user interface away from explicitly showing what happens and I think we're only half did it 😆

(#owkdycq) @axodys yeah, I think it is a bug, or more accurately. I think we only half completed the user and to device change there. 🤦‍♂️

(#owkdycq) @axodys Well there is nothing to work-around per se, just ignore it for now. But yeah in general we're trying to remove the (#xxxxxxx) hash from the text area when replying and forking because we also shove it into a hidden field anyway, so we know what we're doing generally from the UI/UX and Backend. If you happen to have any Go experience we'd love some help here to finish this work 👌

(#5vaid6q) @axodys What's image mockup tech? A preview of how you will wear some frames? 😮