the fact that we can work from anywhere is just a big bonus, and makes it possible! π¨π»βπ»π₯³
@thsofficial.bsky.social @homeexchangecom.bsky.social
the fact that we can work from anywhere is just a big bonus, and makes it possible! π¨π»βπ»π₯³
@thsofficial.bsky.social @homeexchangecom.bsky.social
trustedhousesitters is what we use for housesits, and homeexchange for swapping places..
weβre real ambassadors for both platforms and can recommend it to anyone with a heart for animals and a desire to travel!
been doing that for the past 10 years on and off & 5 years with my gf now.. > was a great hack during covid!
in belgium everything was in lockdown, but people were still travelling and needed people to look after their pets..
we spent quite some time in portugal like that! π΅πΉ
anyone else doing housesits or home exchanges every now and then?
itβs a great way to travel slow and really get to know a place! besides, you can do it all over the world! π
EOY detox is finally over.. β οΈπ
itβs high time to revive momentum in ongoing projects!π₯ I started pSEO for mytravelagent.. anyways I had to wait for some user generated content first πππ»ββοΈ
all while doing a housesit in the netherlands with my gf.. I really like my life! π¨π»βπ»π₯³
if you like to see the tool I'm talking about, you can find it here: mytravelagent.io
if youβre using @ClerkDev
βs authentication services, make sure to account for iframe scenarios! proactively handle userAgents to prevent similar issues.
learn from my experience, and save yourself the headache! π
but the damage was already done. I likely caused a lot of bad ux and lost sign-ups during that time because of the error. itβs a painful lesson I hope no one else has to learn the hard way.
to fix it, I quickly wrote a function to detect the userAgent and hide the standard clerk sign-in/sign-up components if the app is accessed within an iframe.
once I implemented the fix, the issue was resolvedβ12 hours after posting.
I contacted @ClerkDevβs support team and found out that their sign-in/sign-up components arenβt supported in iframe browsers... this wasnβt something I anticipated during development or testing.
and hereβs the problem: users trying to sign up saw a 403 disallowed_useragent error when accessing my app in the iframe.
worse, I didnβt know this was happening for hours until someone reached out to let me know. π¬
the linkedIn post got some tractionβespecially from people using the linkedIn mobile app. but hereβs where things went south: links from the mobile linkedIn app open in an iframe browser.
after testing my app, MyTravelAgent, in production for 2 weeks with friends and family, I thought it was finally ready for public release. excited, I shared my journey on linkedIn 2 days ago.
β οΈ Heads-up for anyone using @ClerkDev
for authenticationβdonβt make the costly mistake I did! I ran into a serious issue that took me 12 hours to realize was happening. Hereβs the full story and what you can learn from it: π
i pushed back the sign in request, now you access the dashboard w/o credentials, can fill in trip details, and get a better feel on how the tool works.
thanks for the feedback! ππΌ
there are curated trips you can view to see what sort of information you get on mytravelagent.io/inspiration
and the demo on the landing page shows the dashboard youβd use when signed up..
thanks for the feedback! appreciated! ππΌ
try it here: mytravelagent.io
curious for feedback π€
Release day! I'm launching MyTravelAgent β a new trip-planning companion! π test and see how effortless it is.. are you ready to explore? π
#buildinpublic
no-nonsense travel planning is our mantra! π
most tools out there have one thing in common: theyβre overloaded with features, and make it hard to keep track of what youβre doing... π€·π»ββοΈ
simplicity and good ux is everything! π―
release countdown has begun; early next week! β³π
itβs been a couple of tough days, as we had to say goodbye to our 13 yo french bulldog, Mila πΆπ’
slowly regaining momentum - wrapping up feedback loops and implementing improvements..
still on track for a mid december launch
#buildinpublic
demo video locked and loaded! π½οΈ
quite happy with the result! it took me around 6 hours π»
will drop it here next week.. still got some low volume user testing to do before i set the place on fire π₯π₯
#buildinpublic
making a demo video today, to demonstrate the tool, and trip generation flow on the landing page.. π
recording with quicktime, post-editing with @capcutapp π½οΈ
#buildinpublic
can consider generating & printing some QR codes to leave behind wherever i go for offline marketing..
but yeah, VA - havenβt thought of that yet..
random people in a bar / coffee shop so far, but airport lobbies sound like a good idea!
will book a nice trip somewhere to do more field research, and put it as a business expense ππΌπ
icp isnβt super defined yet.. i throw it out there and see what works, and what doesnβt, not excluding anyone at this point..
i gather valuable information understanding why - or why not - ppl would be using my app by asking them after their try out
best way to gather feedback for your app, is really asking random people to test it, then observe them going through the flows..
actively tweaking things based on that information this weekend.. π¨π»βπ»π
#buildinpublic
retesting all flows in production.. so far it seems like i can send out the first platform invites over the weekend! LFG! π₯π
#buildinpublic
ICYMI β Tailwind CSS v4.0 is now in beta β¨
tailwindcss.com/blog/tailwin...
β‘ Up to 5x faster builds, 100x faster rebuilds
π§° Built-in imports, prefixing, and more
πͺ Simplified, CSS-first configuration
π¦Ύ Modern CSS features like @βstarting-style and container queries
π¨ New wide-gamut color palette
would be great to see some post analytics and data insights though.. is that on the roadmap? πΊ
first impression: bluesky seems to be less bot-infected than x.. anyone else has that feeling? off to a good start! π€β οΈ