From Jiri Vlasak to ~qeef/damn-project
An (a bit late) update on this. > 1.- It´s possible to add "back link" [...] the "get areas" link has been added to the manager [1] and the mappy [2] clients. > 2._ I don't know if this is impossible [...] This was about JOSM update to include changeset URL in note comment if feasible [3]. Thanks to the Taylor Smock it will be available in the next JOSM version. (Even the patch is "by qeef", it is by Taylor, who more likely get inspired by what I drafted.)
From Jiri Vlasak to ~qeef/damn-project
>1.- It´s possible to add "back link" on manager specific area to go back "manage area" list? Make sense? ( actually you click the browser back button, it´s fine for me ). This is completely legit and makes perfect sense. I will improve the navigation for all the web clients. A link to "list of all areas" is truly missing. >2._ I don't know if this is impossible but i'm asking anyway... My actual workflow: I need to check the JOSM documentation and I will let you know. I will start working on both issues after the weekend. Thank you for your ideas!
From Jiri Vlasak to ~qeef/damn-project
The issue was solved [1], sorry for late reply here. Indeed, the problem was in the redirection -- the header with the authentication is dropped, what is confirmed by the log. Please, upgrade the damn JOSM plugin to version 0.13.0. [1]: https://mastodon.social/@risturiz/110922561936537821
From Jiri Vlasak to ~qeef/damn-project
Looks we are back online. Please, let me know if something does not work. Thanks.
From Jiri Vlasak to ~qeef/damn-project
Short remainder that the outage happens today, UTC night.
From Jiri Vlasak to ~sircmpwn/sr.ht-discuss
> > I am curious, how is that done that writefreesoftware.org project [1] > > has single source [2] redirected to directly? > > That's the case for all projects with only one repository source. For > your own projects, though, you always see the list so that you can > configure more repos to add. Oh, nice, didn't try to test in incognito window. It works. Thanks!
From Jiri Vlasak to ~sircmpwn/sr.ht-discuss
I am curious, how is that done that writefreesoftware.org project [1] has single source [2] redirected to directly? Thanks [1]: https://sr.ht/~sircmpwn/writefreesoftware.org/ [2]: https://git.sr.ht/~sircmpwn/writefreesoftware.org
From Jiri Vlasak to ~qeef/damn-project
Dear mappers, I am going to upgrade the server where damn-project.org is hosted. Unfortunately, the server will be down a bit longer than usually due to testing. My plan is to start on Wednesday UTC evening, August 16. If you have an event planned on UTC night between 16th and 17th, please, let me know and I will postpone the upgrade by day. Thank you.
From Jiri Vlasak to ~sircmpwn/public-inbox
Hello zig, thank you for your feedback. > Regarding variable-length integer encoding in BARE, there's an > alternative to (U)LEB128 encoding that is simpler and faster. Variable-length integer encoding was discussed in the following threads: - https://lists.sr.ht/~sircmpwn/public-inbox/%3C1dfb75c3-86a3-276a-ca9a-ba9da0df376d%40elvinger.fr%3E - https://lists.sr.ht/~sircmpwn/public-inbox/%3CCAFFTG-a-Vci%2BkS_d_%3DuaX8kyxszqtB-79pcb5580Z9xw72V5kw%40mail.gmail.com%3E Please, note that changing the encoding would break current implementations, which is strong argument against. > Another thing regarding varints is that often a signed integer type is > used to store only positive values. Which makes it storing as zigzag
From Jiri Vlasak to ~sircmpwn/public-inbox
Hi Victorien, > I am wondering if this could be simply done by treating the message as > an opaque sequence of bytes of another message: I am afraid that not. To my understanding, when using streamed protocol like TCP, you don't know where is the end of the message. So you need to send the message length first. BARE message with data primitive type (of arbitrary length) requires the length of the data to be encoded before the data itself as uint. However, the uint data type has no fixed length, so the length of the uint is not known in advance, resulting in the same problem as the original one.