<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Gullivr Blog</title>
    <link>https://gullivr.xyz/blog</link>
    <description>Travel guides, Gullivr how-tos and product news.</description>
    <language>en</language>
    <atom:link href="https://gullivr.xyz/blog/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Sat, 05 Sep 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>Plan a trip with other people without losing the thread</title>
      <link>https://gullivr.xyz/blog/plan-a-trip-with-other-people</link>
      <guid isPermaLink="true">https://gullivr.xyz/blog/plan-a-trip-with-other-people</guid>
      <pubDate>Sat, 05 Sep 2026 12:00:00 GMT</pubDate>
      <category>How to use Gullivr</category>
      <description>Invites, editor and viewer roles, real-time edits and read-only share links — how collaboration works in Gullivr, and when to use which.</description>
      <content:encoded><![CDATA[<p>Group trips break in a predictable way. One person builds the itinerary, everyone else sends
suggestions in a chat, and by day three nobody is sure which version is the real one.</p>
<p>Gullivr has three separate answers to that, and picking the wrong one is the usual reason
people find it confusing. Here they are, shortest first.</p>
<h2 id="a-share-link-for-people-who-only-need-to-look">A share link, for people who only need to look</h2>
<p>Turn on sharing for a trip and you get a public read-only link. Anyone with the URL sees the
itinerary as it stands — days, places, times — without an account and without being able to
change anything.</p>
<p>Use it for the people who are coming but not planning: parents who want to know where you&#39;ll
be, a friend joining for two days, the group chat that just wants the address of the hotel.
Turn sharing off and the link stops working.</p>
<h2 id="an-invite-for-people-who-are-actually-planning">An invite, for people who are actually planning</h2>
<p>Inviting a collaborator by email adds them to the trip properly. They get one of two roles:</p>
<ul>
<li><strong>Editor</strong> — can add and move places, edit days, add flights and accommodation, change
anything you can change.</li>
<li><strong>Viewer</strong> — sees everything inside the app, including the parts the public link does not
show, but cannot edit.</li>
</ul>
<p>Roles are not permanent. Promote a viewer to editor when they start pulling their weight, or
demote an editor who keeps reordering day 4. You can also cancel an invitation before it is
accepted, and remove a collaborator afterwards.</p>
<p>The rule of thumb: <strong>editor for the two or three people building the plan, viewer for everyone
else.</strong> A trip with six editors is a trip where nobody knows who moved the museum.</p>
<h2 id="edits-show-up-as-they-happen">Edits show up as they happen</h2>
<p>When two people have the same trip open, changes appear on both screens without a refresh.
This matters more than it sounds like it should: the reason collaborative planning usually
happens in a chat window is that people do not trust a shared document to be current. Watching
a place land on day 2 while someone else adds it removes that doubt.</p>
<h2 id="where-the-ai-agent-fits">Where the AI agent fits</h2>
<p>If you have connected an AI agent, it acts with your permissions on your trips. So &quot;ask Claude
to find three restaurants near the hotel and add them to day 3&quot; produces edits your
collaborators see immediately, the same as if you had added them by hand.</p>
<p>Which is the actual point: the agent is another editor on the trip, not a separate app you
have to copy results out of.</p>
<h2 id="the-short-version">The short version</h2>
<table>
<thead>
<tr>
<th>You want</th>
<th>Use</th>
</tr>
</thead>
<tbody><tr>
<td>Someone to see the plan</td>
<td>Share link</td>
</tr>
<tr>
<td>Someone to see everything, in the app</td>
<td>Invite as viewer</td>
</tr>
<tr>
<td>Someone to help build it</td>
<td>Invite as editor</td>
</tr>
<tr>
<td>An AI to help build it</td>
<td>Connect an agent</td>
</tr>
</tbody></table>
]]></content:encoded>
    </item>
    <item>
      <title>The Gullivr blog is open</title>
      <link>https://gullivr.xyz/blog/the-gullivr-blog-is-open</link>
      <guid isPermaLink="true">https://gullivr.xyz/blog/the-gullivr-blog-is-open</guid>
      <pubDate>Sat, 05 Sep 2026 12:00:00 GMT</pubDate>
      <category>What&apos;s new</category>
      <description>A place for travel guides, how-tos for the features you already have, and short notes on what changed in the app.</description>
      <content:encoded><![CDATA[<p>Gullivr has had a landing page, a privacy policy and a page explaining how to hook up an AI
agent. What it has not had is anywhere to write things down.</p>
<p>So: a blog. Three kinds of post will live here.</p>
<h2 id="travel-guides">Travel guides</h2>
<p>Itineraries and destination write-ups. Not the SEO-shaped kind that lists twelve cities and
tells you nothing about any of them — the kind you would actually copy into a planner and
follow. Where the good coffee is. Which museum is worth the queue and which one is not.</p>
<h2 id="how-to-use-gullivr">How to use Gullivr</h2>
<p>The app has more in it than the landing page admits: shared trips with editor and viewer
roles, flights and transfers, a packing list, expenses that settle up between travellers,
public share links. Most of it is discoverable, but &quot;discoverable&quot; is not the same as
&quot;discovered&quot;. These posts walk through one feature at a time.</p>
<h2 id="what-s-new">What&#39;s new</h2>
<p>Short notes when something ships, and the occasional longer one about how it was built. This
post is the first of them.</p>
<h2 id="how-this-works">How this works</h2>
<p>Posts are Markdown files in the repository. Publishing one is a pull request, which means the
blog is versioned, reviewable and diffable like the rest of the app. It also means there is no
comment section — if you want to argue with something here, the issue tracker is right there.</p>
<p>Everything is published in English and Italian. Use the language switch at the top of any post.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Three days in Lisbon, arranged so you are not always climbing</title>
      <link>https://gullivr.xyz/blog/three-days-in-lisbon</link>
      <guid isPermaLink="true">https://gullivr.xyz/blog/three-days-in-lisbon</guid>
      <pubDate>Sat, 05 Sep 2026 12:00:00 GMT</pubDate>
      <category>Travel guides</category>
      <description>A Lisbon itinerary built around the city&apos;s hills rather than against them — three days, one neighbourhood at a time, with the walking that actually works.</description>
      <content:encoded><![CDATA[<p>Most Lisbon itineraries are a list of sights in the order someone found them. Then you get
there and discover that two of the things scheduled for the same afternoon are separated by a
hundred metres of vertical.</p>
<p>Lisbon is built on hills. An itinerary that ignores them is a day of pointless climbing. This
one is arranged by neighbourhood and by altitude: each day stays roughly on one level, and you
descend rather than ascend wherever there is a choice.</p>
<h2 id="day-1-baixa-chiado-bairro-alto">Day 1 — Baixa, Chiado, Bairro Alto</h2>
<p>Start low and end high, once.</p>
<p>Begin in <strong>Praça do Comércio</strong>, at the river. It is flat, it is enormous, and it is the only
part of central Lisbon laid out on a grid — the result of the 1755 earthquake, which flattened
everything and gave the Marquês de Pombal a blank sheet.</p>
<p>Walk north through <strong>Baixa</strong> to Rossio, then take the <strong>Elevador de Santa Justa</strong> up to Chiado
if the queue is short and the stairs beside it if it is not. The lift is a nice piece of iron
and a bad use of forty minutes.</p>
<p><strong>Chiado</strong> is for the afternoon: bookshops, the Bertrand (the oldest still trading anywhere),
coffee standing up at a counter. Then walk uphill into <strong>Bairro Alto</strong> as it gets dark. The
neighbourhood is dead until about nine and unrecognisable by eleven.</p>
<p><strong>Evening:</strong> dinner in Bairro Alto, then down to Cais do Sodré if you want the night to
continue.</p>
<h2 id="day-2-belem-and-only-belem">Day 2 — Belém, and only Belém</h2>
<p>Belém is six kilometres west and people try to fit it into a morning. It does not fit.</p>
<p>Take the tram or the train along the river. The three things worth your time are the
<strong>Mosteiro dos Jerónimos</strong> (go at opening or after three; the middle of the day is a queue),
the <strong>Torre de Belém</strong> from the outside — the interior is a stairwell with a view you can get
elsewhere — and the <strong>Padrão dos Descobrimentos</strong>.</p>
<p>Eat a pastel de nata at <strong>Pastéis de Belém</strong> because you have to, then eat a better one
somewhere else later in the trip. The original is good. The queue is not proportional to how
much better it is.</p>
<p><strong>Afternoon:</strong> the <strong>MAAT</strong> if you like modern architecture, the <strong>Coach Museum</strong> if you want
the strangest collection in the city. Then back east along the river as the light goes.</p>
<h2 id="day-3-alfama-downhill">Day 3 — Alfama, downhill</h2>
<p>The mistake with Alfama is entering from the bottom. Do the opposite.</p>
<p>Start at <strong>Castelo de São Jorge</strong>, at the top. Get there for opening; the castle itself is
mostly walls and peacocks, but the view is the point and it belongs to whoever arrives first.</p>
<p>Then walk <strong>down</strong> through Alfama, with no route. This is the one part of the city the
earthquake spared, which is why the streets make no sense — they are medieval, and they were
never redrawn. Getting lost is the intended experience. You will come out somewhere near the
river eventually; the hill only goes one way.</p>
<p>On the way down: <strong>Miradouro de Santa Luzia</strong> for the tiles, the <strong>Sé</strong> cathedral if it is
open, and any of the small places serving grilled sardines that do not have a menu in four
languages.</p>
<p><strong>Late afternoon:</strong> the <strong>Feira da Ladra</strong> flea market if it is Tuesday or Saturday.</p>
<h2 id="what-to-skip">What to skip</h2>
<ul>
<li><strong>Tram 28 as a sightseeing trip.</strong> It is a commuter tram full of tourists and pickpockets.
Ride one stop if you want the photograph, then walk.</li>
<li><strong>Fado dinners with a set menu.</strong> The food subsidises the music and neither is good. Find a
small place in Alfama that starts at ten.</li>
<li><strong>Sintra as a day trip inside three days.</strong> It deserves its own day and you do not have one.</li>
</ul>
<h2 id="copying-this-into-gullivr">Copying this into Gullivr</h2>
<p>Three days, three neighbourhoods, one day per day. If you are planning this trip in Gullivr,
the shape that works is one day per section above, with the sights added as places in walking
order — then let the route distances tell you where you have been optimistic. Lisbon walking
times are always longer than the map says, because the map is flat and the city is not.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
