u/clarafiedthoughts

Is it possible to do a day trip (Yehliu > Shifen > Jiufen)?

For example:

2 Hour at Yehliu: Queen's Head, Sea Candels, Mushroom Rocks

Head to Shifen for: Sky Lantern, Old Street, Shifen Waterfall

And then head to Jiufen for Old Street, Lantern Alley

And then back to Taipei.

If you tried: Would you recommend doing it DIY or should we book a tour on Klook?

As the title post: Is it possible to do a day trip (Yehliu > Shifen > Jiufen)? Would you recommend doing it DIY or should we book a tour on Klook?

We've helped a lot of remote teams set up screenshot monitoring through Jibble, and honestly, the ones that struggle almost always make the same mistake. They treat it like surveillance instead of a work accountability tool. Employees notice that difference immediately, and adoption tanks.

A few things we've learned and seen work:

Being upfront about everything. Tell people when screenshots are taken, who sees them, and how long they are kept. Uncertainty kills trust faster than the monitoring itself.

Tie to work time only. Teams have way less pushback when screenshots start at clock-in and stop at clock-out or break. The moment it bleeds into personal time, you've got a problem.

Start with blurred screenshots. A surprising number of teams prefer this, at least initially. You still get the accountability layer without it feeling invasive. Some never move past it, and that's fine.

Don't let it replace actual management. This is where things go sideways. Screenshots give you context, but if managers start using them instead of check-ins, project tracking, or real conversations, it creates a weird surveillance culture that kills morale.

Be selective about who it applies to. Not everyone needs it. Hourly contractors or client-billable work makes sense, but salaried employees being managed on outcomes are probably overkill.

One team we worked with actually turned it off after 6 weeks because their managers were spending more time reviewing screenshots than talking to their people. The app wasn't the problem, how they used it was.

What's your experience been? What's worked (or completely backfired) for you?

Do's and Don'ts in Screenshot Monitoring

I’m not here to sell anything. I honestly just wanted to share something I recently discovered that completely caught me off guard.

I’m still pretty new to the SaaS/startup world. A developer friend recently started asking me for ideas and feedback on a product he’s building because he sees me as a potential end user for it. So while giving feedback and discussing features with him, I’ve slowly been learning how this whole industry works behind the scenes.

This might not be new to a lot of people here, but as someone who’s still basically a newbie in SaaS, I only came across the term “patent troll” for the first time this week.

I had to look it up and I’m amazed this kind of thing even exists.

Now it’s also sitting in the back of my mind because I keep thinking… what if some random feature idea we talk about already exists somewhere in a patent?

From what I understand, patent trolls are basically entities that acquire patents mainly to pursue licensing demands or lawsuits against companies that allegedly infringe on them. They usually don’t build products themselves. The whole thing seems to revolve around legal pressure and settlement economics.

What really made it click for me was reading a post on LinkedIn from a CEO of a time tracking SaaS.

He said Jibble got sued last December in Texas by a company called UpChat LLC over patent infringement. Apparently UpChat had only been created one week before acquiring the patent involved in the lawsuit.

One week.

That alone already sounded insane to me. But the part that honestly messed with my head was the economics behind it.

According to him, UpChat immediately demanded around $95k to settle, while their projected legal costs to fight the case could potentially go beyond $500k.

And suddenly the whole thing made sense.

The goal doesn’t even seem to be winning the case. It’s making the legal process so expensive that paying the settlement becomes the rational business decision.

Apparently most of the other companies being sued by UpChat settled pretty quickly, which honestly I can understand. If you’re a startup staring at those numbers, settling probably feels unavoidable even if you think the claims are ridiculous.

What surprised me most was him saying that hiring a massive law firm would’ve actually made things worse, because the higher your legal bills climb, the more attractive settlement starts to look. Which is apparently exactly what these entities are counting on.

So instead, they hired a solo patent attorney who worked lean and basically made it clear they were willing to fight the whole thing without burning millions on legal fees.

Apparently shortly after that, UpChat dismissed the case.

I honestly sat there for a while after reading all this because I always assumed lawsuits were mostly about who was right or wrong. I didn’t realize there’s an entire corner of the startup world where the process itself is kind of the weapon.

Now I’m wondering how common this actually is.

If you’ve been in SaaS/startups for a while, have you ever run into something this absurd?

Doesn’t even have to be patent trolls specifically. Could be anything that made you stop and think. Because honestly this completely changed how I look at startups.

When we started working on this, the goal wasn’t to change how people use Jibble.

It was to remove a small but consistent friction: having to stop what you’re doing just to log time.

Most people don’t struggle with what to log.

They struggle with:

• remembering to log it
• switching context just to update it
• reconstructing it later from memory

So we connected Jibble to tools people are already using throughout the day, like ChatGPT, Claude, and Cursor.

Now instead of opening another tab, you can just type things like:

• “Clock me in” / “Clock me out”
• "Log 30 minutes to the design review meeting"
• “Show my timesheet this week”
• "Give me a time tracking report for the Engineering team this month"
• "Show me which projects took the most hours last week"
• "Show me the team's attendance for today"
• "What did I work on last Thursday?"

And it updates Jibble directly in the background.

What is MCP and How Does Jibble Use MCP?

For anyone wondering what MCP actually is:

MCP (Model Context Protocol) is what lets AI engines like ChatGPT or Claude connect directly to apps like Jibble.

So instead of just asking how to log time, you can actually log time from inside the chat.

In practice, that means you’re no longer switching tools just to update something. You’re doing it in the same place you’re already working.

What surprised us wasn’t the feature itself.

It was how people started using it.

They didn’t stop using Jibble.

They just stopped opening it as often.

Jibble is still:

• where time entries live
• where timesheets and reports are generated
• where approvals and permissions are handled

But the interaction layer changed.

Instead of:

open app → log time → go back

It became:

type → done → keep working

And that small shift changed behavior more than we expected.

People started logging things while the context was still fresh, instead of filling everything in at the end of the day.

The result:

• more accurate time logs
• better task descriptions
• fewer gaps between what was done and what was recorded

It’s not really a new feature, we are just introducing a different way of interacting with tracking time and attendance without ruining your workflow.

Jibble MCP Integration

My friends and I booked a flight to Hanoi last November. Now I’m planning to invite my partner as well, but I was a bit surprised by the fare difference.

I understand that recent fuel surcharges may have affected prices, but I’m wondering if it’s better to book now or wait for a possible seat sale in May or June.

Thanks in advance!

https://preview.redd.it/ee9kd650zoxg1.png?width=2200&format=png&auto=webp&s=1ef89567d9e497c6aa0c2c2acb78eb180bb98002