> @@ -566,11 +574,11 @@ readerview_app_window_display_response_text_plain(struct gemini_response *resp,
>  	int contents_length = 0;
>  
>  	for (int n = 1; n > 0;) {
> -		n = BIO_read(resp->bio, &contents[contents_length], contents_size - contents_length - 1);
> -		if (n == -1) {
> +		n = br_sslio_read(&resp->body, &contents[contents_length], contents_size - contents_length - 1);
> +		/*if (n == -1) {
>  			fprintf(stderr, "Error: read");
>  			return;
> -		}
> +		}*/

This is maybe silly question, but why to commit comented code?

Just for completeness -- it was not fair to remove panel subdomain even
if the panel was merged to the client.

Panel subdomain was revived, see https://panel.damn-project.org/

Just for completeness -- since manager v0.3.0 (Fri Dec 18 2020,) there
is regular HTML form for _creating new area_.

Particularly, for _intstructions_, the HTML form says:

> Put one world describing what to map. Put some (wiki) link to more
> information. To delete the instruction, delete the first field.

Hi Gustavo,

> I recently updated my DAMN instance (https://tarefas.mapeia.space) so I
> had a surprise with the new client, I really liked the old one, it was
> easy and intuitive to use, although the UI was a bit simplistic, but it
> worked well...

I'm sorry for surprises, that was not an intention. Also, I'm trying to
keep the UI still simple.

The reason to make unlock actions _hidden in text_ is to avoid rushed
clicking for newbie mappers. Experienced mappers are still encouraged to
use "open panel" in the area or https://mappy.damn-project.org/.

Because the https://client.damn-project.org/ is being used a little bit more
than a half year ago, I removed the areas I created that are testing and
unused.

I also wrote to the authors of unused areas or the areas with bad grid.

On Mon, Nov 30, 2020 at 06:56:06PM -0700, Colin Reeder wrote:
> It looks like a recent change has made the map unreadable, I have no
> idea what I'm looking at

It's fixed now. I am really sorry for that. I though you already finished
mapping.

> Especially for `instructions`, I'm not sure what I'm expected to put there

This is not yet decided, sorry.

The original idea is that there is *key* and *value*, where *key* is one word
(e.g. highways) and *value* is link (e.g. link to highway tag africa.)

Thanks guys.

> Unfortunately, Docker assumes every HTTPS git URL ends with ".git", 

Thanks for pointing me out! I found the issue where it's discussed [1].

> which Sourcehut does not support.

I just renamed `my-repository` to `my-repository.git`. Ugly hack from [1] but
it works.

> You can use the SSH clone URL, but (unless this has changed recently)

It didn't changed and I don't want to use that. (It works for me locally but

Hello,

I do have a beginner question. Is it possible to build a docker image directly
from the sr.ht? If so, how?

I do:

    $ docker build -t www https://git.sr.ht/~qeef/damn-www

That returns the error:

    Sending build context to Docker daemon  17.41kBs://git.sr.ht/~qeef/damn-www 15.59kB
    Error response from daemon: Dockerfile parse error line 1: unknown instruction: <!DOCTYPE

---
 src/pslot.rs | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/src/pslot.rs b/src/pslot.rs
index e24fc37..c13c2cd 100644
--- a/src/pslot.rs
+++ b/src/pslot.rs
@@ -110,4 +110,24 @@ impl PSlot {
         ).sqrt();
         d1 < d2
     }
+
+    /// Return if the parking slot is on the right side.
[message trimmed]