[0;34m➜ fast rung: yapsnap on audio1403151924.m4a[0m
2026-09-11-TripContext-transcript-kroko.txt
[0;32m✓ 75 lines in ./2026-09-11-TripContext-transcript-kroko.txt[0m
[0;34m➜ quality rung: faster-whisper large-v3 on cpu[0m
Detected language 'English' with probability 1.000000
[00:01.970 --> 00:12.970]  I intend to show how a complete wiki can be graded from a video specification, and for that I'm going to show my screen.
[00:12.970 --> 00:20.970]  Here is velorail.bitplan.com. It's an application which allows you to see maps of readings.
[00:20.970 --> 00:26.970]  Now I'm going to start with Bari. That's a city in southern Italy.
[00:26.970 --> 00:35.970]  When I click here, I get the different map options, and we can now see how we can travel from Bari, depending on what we want to do.
[00:35.970 --> 00:44.970]  Let's start with bike routes, so an open cycle map, and you can see this is where you can go from Bari.
[00:44.970 --> 00:55.970]  You can go to Brindisi, you can go inbound to Rome, or you can go north to Slovenia, for instance.
[00:55.970 --> 00:56.970]  This is actually a map.
[00:56.970 --> 00:57.970]  This is the plan.
[00:57.970 --> 01:05.380]  We are going to be in Bari in October, and we then want to go to Ljubljana.
[01:05.380 --> 01:13.380]  Another option we have here is to go by train, so you can see which train routes are available.
[01:13.380 --> 01:22.380]  So I think it's some 1,200 kilometers from Bari to Ljubljana, and most of it could be done by train also.
[01:22.380 --> 01:27.380]  And you could even take the ferry to the other side.
[01:27.380 --> 01:28.380]  So that's it.
[01:28.380 --> 01:36.380]  So the idea is that I want a wiki in which we can do these things, similar to the wiki we already have.
[01:36.380 --> 01:39.380]  Like, we've got the eBike39 one.
[01:39.380 --> 01:41.380]  That one we need to log in.
[01:41.380 --> 01:45.380]  Let's see whether eBike.plitdown.com is available or not.
[01:45.380 --> 01:57.660]  It says we need to log in, so let's log in.
[01:57.660 --> 02:00.660]  That's a bit frustrating now.
[02:00.660 --> 02:03.660]  Same thing with you.
[02:03.660 --> 02:04.660]  .
[02:04.660 --> 02:12.330]  My username and password.
[02:12.330 --> 02:17.570]  And I log in.
[02:17.570 --> 02:25.570]  So this is the wiki we used to have in the past where we could track places we've been.
[02:25.570 --> 02:30.570]  For instance, the Isle of Wight or Czechoslovakia.
[02:30.570 --> 02:37.570]  And then in that wiki, we used to keep track of places we've been, and then we had these fields.
[02:37.570 --> 02:41.570]  Tour date, target track, coordinate stay, shop distance common.
[02:41.570 --> 02:55.060]  And basically, I'm not too sure what this is the thing we want to have in the future.
[02:55.060 --> 02:57.060]  This is organized around trips.
[02:57.060 --> 02:59.060]  So here's a trip.
[02:59.060 --> 03:03.060]  The trip has legs, I would say.
[03:03.060 --> 03:05.060]  This one doesn't have legs.
[03:05.060 --> 03:08.060]  I think the eBike39 worked with legs.
[03:08.060 --> 03:10.060]  So let's go for the eBike39 one.
[03:10.060 --> 03:21.160]  And there is, I think, the same password.
[03:21.160 --> 03:32.150]  So this is a new version.
[03:32.150 --> 03:37.150]  And we do the same thing here.
[03:37.150 --> 03:41.150]  I think we can use Spain.
[03:41.150 --> 03:43.150]  So let's go for Spain.
[03:43.150 --> 03:50.110]  Spain 2025.
[03:50.110 --> 03:53.110]  This is where we started doing things a bit differently.
[03:53.110 --> 03:56.110]  So we had pages.
[03:56.110 --> 03:58.110]  Let's take here Miranda del Ebro.
[03:58.110 --> 04:03.110]  And the idea was we'd link these pages to places.
[04:03.110 --> 04:05.110]  So this is an adaf link that we had.
[04:05.110 --> 04:10.110]  So the whole thing here was not very structured.
[04:10.110 --> 04:16.110]  It only had a page and coordinates, which was a thing.
[04:16.110 --> 04:27.500]  And then we had different tracks we were interested in, like the Traslavina sign here.
[04:27.500 --> 04:31.500]  So this was a tour where we had, like, a day to target with a location coordinate.
[04:31.500 --> 04:34.500]  And here we have trip and track, which was available there.
[04:34.500 --> 04:37.500]  And then we already got a map of that.
[04:37.500 --> 04:41.500]  So if I go to track, you can see the track here.
[04:41.500 --> 04:45.500]  Cycle.travel was the link that we got.
[04:45.500 --> 04:57.220]  And if you go on the track property at the time, this was like an external identifier, which showed to Cycle.travel.
[04:57.220 --> 05:02.220]  And I think we already do also, this might be a good example, like going through the adventures of a fat man.
[05:02.220 --> 05:08.220]  Because this is something where you have YouTube links.
[05:08.220 --> 05:10.220]  Like this is episode 13.
[05:10.220 --> 05:14.220]  And then we try to find out where they stayed.
[05:14.220 --> 05:19.220]  So here's a TripAdvisor link.
[05:19.220 --> 05:25.500]  And that was what the fat man showed us.
[05:25.500 --> 05:28.500]  And this was, like, a trip.
[05:28.500 --> 05:30.500]  And you can see all the things.
[05:30.500 --> 05:32.500]  So that's not too bad.
[05:32.500 --> 05:36.500]  So here the route is certain episodes.
[05:36.500 --> 05:39.500]  Then the tour.
[05:39.500 --> 05:44.500]  Then each episode has a target and a track.
[05:44.500 --> 05:55.490]  And then if we go on the page, a location coordinates.
[05:55.490 --> 06:07.560]  The problem here is that I'm not too happy with this because I think there is a concept that is called leg here.
[06:07.560 --> 06:08.560]  Yep.
[06:08.560 --> 06:11.560]  There's our concept leg.
[06:11.560 --> 06:16.560]  And the leg has, like, a from property, a true property, a transport property.
[06:16.560 --> 06:19.560]  And basically we did already do a context for that.
[06:19.560 --> 06:21.560]  That's called the trip context.
[06:21.560 --> 06:23.560]  That's on bike.bitplan.com.
[06:23.560 --> 06:26.560]  It's got a leg, a log, and a tour.
[06:26.560 --> 06:30.560]  And it's got an example of how we do that.
[06:30.560 --> 06:41.980]  And basically on context.bitplan.com, we can see whether the trip context is available here.
[06:41.980 --> 06:48.070]  Yep.
[06:48.070 --> 06:50.070]  As you can see, it's not.
[06:50.070 --> 06:53.070]  And the question is, how do we get this?
[06:53.070 --> 06:58.070]  So basically we have to teach the AI what a context is.
[06:58.070 --> 07:04.070]  So, A, a context is something you will find here on context.bitplan.com.
[07:04.070 --> 07:14.070]  And the most important context we have is a meter model because this is what organizes our wikis.
[07:14.070 --> 07:17.070]  So there is a model of it.
[07:17.070 --> 07:20.070]  Meter model has topics and so on.
[07:20.070 --> 07:23.070]  So later when this video is read.
[07:23.070 --> 07:26.070]  The AI will know on context.bitplan.com.
[07:26.070 --> 07:28.070]  Meter model, you find the meter model.
[07:28.070 --> 07:31.070]  And then you find context like the trip context.
[07:31.070 --> 07:37.070]  That's one that we want to improve on and see whether it fits our needs.
[07:37.070 --> 07:48.070]  And we want to show off how it works on the context.bitplan.com wiki by using our tool for that.
[07:48.070 --> 07:52.070]  And the tool we use for that is WipeAgain.
[07:52.070 --> 07:57.570]  Which is available on the internet.
[07:57.570 --> 08:00.570]  So this is WipeAgain.bitplan.com.
[08:00.570 --> 08:03.570]  And it's an open source project.
[08:03.570 --> 08:05.570]  So let's see.
[08:05.570 --> 08:15.220]  And I think one page that might be necessary to be read is the WipeAgain description.
[08:15.220 --> 08:22.490]  So we have to log into our wiki here.
[08:22.490 --> 08:29.710]  Then go to the WipeAgain page.
[08:29.710 --> 08:31.710]  Which describes how to use that.
[08:31.710 --> 08:33.710]  The Wipe principle generator.
[08:33.710 --> 08:37.710]  I think this page we can push later.
[08:37.710 --> 08:39.710]  To make it public.
[08:39.710 --> 08:41.710]  To make life easier.
[08:41.710 --> 08:51.710]  And then the AI should be capable of doing what we want just based on the video that I just recorded.
[08:51.710 --> 08:53.710]  So let's try that out.
[08:53.710 --> 08:57.710]  I'm going to stop sharing and stop the recording.
[08:57.710 --> 08:59.710]  And then see what happens.
Transcription results written to '/tmp/tmp.qpOZweyCdx' directory
[0;32m✓ 108 segments in ./2026-09-11-TripContext-transcript-raw.txt[0m
