Haketilo

07/16/2021

11:57 AM General discussion: RE: NLnet fund application

> (So I don't confuse things, have you had any contact with Katarina after the first e-mail you sent her?)
Nope, n... koszko

11:54 AM General discussion: RE: NLnet fund application

> Sure, if this is not a problem for you :)
Not at all! I'll CC you in this time to remove the delay in exchange.
... jahoti

09:55 AM General discussion: RE: NLnet fund application

> I can ask if you want.
Sure, if this is not a problem for you :)
I guess there's nothing we can lose by simply ... koszko

05:22 AM General discussion: RE: NLnet fund application

> Did the ones who responded actually mention how much money they applied for and whether in the end they got funded ... jahoti

07/14/2021

04:33 PM General discussion: RE: NLnet fund application

Did the ones who responded actually mention how much money they applied for and whether in the end they got funded th... koszko

11:40 AM General discussion: RE: Coding convention

>> That is indeed the problem; unfortunately it took me two tries at rewriting the module using crypto.subtle to real... jahoti

09:51 AM General discussion: RE: Coding convention

> >> A more useful restriction in my opinion would be to avoid putting mixing code and comments on a line (which I so... koszko

08:24 AM General discussion: RE: Coding convention

> Let's also follow Linux here - when the body of a loop/conditional fits within a single line, braces should be omit... jahoti

07/13/2021

11:14 AM General discussion: RE: Coding convention

jahoti wrote:
> the only thing missing is an explicit standard for loops/conditionals *without* braces.
Let's als... koszko

07/12/2021

12:42 AM General discussion: RE: Coding convention

Any conventions I haven't commented on I am perfectly satisfied with and cannot further elaborate.
> Function defi... jahoti

04:39 PM General discussion: Coding convention

We should probably define some. Most of the code I wrote obeys the following:
1. Lines are no longer than 80 chara... koszko

07/09/2021

01:36 AM General discussion: RE: NLNet application- critical jobs

>> Firstly, koszko , are you happy to submit the application?
> More than happy. However, I can think of at least 2 ... jahoti

05:36 PM General discussion: RE: NLNet application- critical jobs

jahoti wrote:
> * Firstly, @koszko , are you happy to submit the application?
More than happy. However, I can thi... koszko

03:49 AM General discussion: NLNet application- critical jobs

There's a few questions we need input on:
* Firstly, @koszko , are you happy to submit the application? Either way... jahoti

01:12 AM General discussion: RE: Name considerations

> Once we create something more (e.g. a Hydrilla-enabled http proxy), we shall need more names. We can collect ideas ... jahoti

05:40 PM General discussion: RE: Name considerations

jahoti wrote:
> I'm certainly happy with that- we really do need a different name for the repository software.
On... koszko

05:08 AM General discussion: RE: Name considerations

> How about naming the extension "Hachette" and the repo "Hydrilla"?
I'm certainly happy with that- we really do n... jahoti

03:14 AM Development - archive: RE: server technology considerations

Really only Python, JavaScript, and shell scripting (if that can really be called a language). I've studied theoretri... jahoti

07/08/2021

09:39 PM Development - archive: RE: server technology considerations

@jahoti wrote:
> somebody who has almost no experience with *any* of those languages...
Out of curiosity: what la... koszko

11:13 AM Development - archive: RE: server technology considerations

My comment about Go was probably too emphatic; it was only intended as an alternative explanation for why Go might be... jahoti

10:50 AM Development - archive: RE: server technology considerations

> >> Go is a language with build system that fetches dependencies from places like github repos, right? That kind of ... koszko

07/07/2021

01:49 AM Development - archive: RE: server technology considerations

>> If you are committed to your existing vision, how would you feel about writing such a "server" that is intended to... jahoti

07:18 PM Development - archive: RE: server technology considerations

> We get decentralization "for free" this
> way--anyone with access to a free/cheap static web host can dump their s... koszko

04:59 PM Development - archive: RE: server technology considerations

> Or do you mean we would then finally develop our own server software,
> as I want to do right now?
No one can d... colby

04:51 PM Development - archive: RE: server technology considerations

> Annotations seem suitable for advertising facts about websites and getting
> feedback. But are they also for shari... colby

12:53 PM Development - archive: RE: server technology considerations

colby wrote:
> Just to be clear: the Hypothesis server and client are free software
Doesn't server rely on nonfre... koszko

03:50 AM Development - archive: RE: server technology considerations

Just to be clear: the Hypothesis server and client are free software, but I'm proposing that we not even worry about ... colby

03:46 AM Development - archive: RE: server technology considerations

I suggest holding off on this indefinitely. Or at least in the meantime, we can piggyback off the https://hypothes.i... colby

12:29 AM General discussion: RE: NLnet fund application

That assumption would be correct. jahoti

12:28 PM General discussion: RE: NLnet fund application

colby wrote:
> If you've recently finished university, you could probably reach out to someone to ask for help.
I... koszko

03:27 AM General discussion: RE: NLnet fund application

I have no close contacts. If you've recently finished university, you could probably reach out to someone to ask for... colby

07:18 PM Development: RE: Trust and the Repository

Related topic: https://hachettebugs.koszko.org/boards/1/topics/17 koszko

12:59 PM Development: Trust and the Repository

Perhaps this would be better as an issue; however, I've promised a forum thread and a forum thread I will deliver.
... jahoti

12:55 PM General discussion: RE: Name considerations

Ok, so it stays as "Hachette"
EDIT: How about naming the extension "Hachette" and the repo "Hydrilla"? koszko

04:02 AM General discussion: RE: Name considerations

Alas, you were right; the link is dead. Your judgment on that point is however evidence enough, and I agree we're mos... jahoti

03:14 AM General discussion: RE: Name considerations

I like Hachette. Pretty good chance it's in the clear, at least in the US, I think. The Hachette Group is a brand, ... colby

07/06/2021

12:41 AM Development - archive: RE: server technology considerations

Use whatever you feel most comfortable with in all cases, I think- the most important thing for now is to have someth... jahoti

09:48 PM Development - archive: server technology considerations

What to write our platform (i.e. repo software) in? What comes to my mind right now are:
C - because that's what I... koszko

12:18 AM General discussion: RE: NLnet fund application

To be fair, if you make different modifications depending on who you're writing to that's probably much better; it li... jahoti

09:15 PM General discussion: RE: NLnet fund application

Interesting. I found myself doing such kind-of-spamming several times. And I used to make different modifications to ... koszko

12:03 PM General discussion: RE: NLnet fund application

Sorry for the lack of clarity- I meant getting agreement here on the message before actually sending it. There's no s... jahoti

11:42 AM General discussion: RE: NLnet fund application

Really good idea!
What do you mean by "a pre-vetted message"? koszko

09:51 AM General discussion: RE: NLnet fund application

Would it be worth contacting projects that are currently working with funds from NLNet and asking them if they have a... jahoti

11:48 AM General discussion: RE: Remine setup

Email notifications and account activation via email should work now. Something in Redmine seems to be queuing emails... koszko

11:39 AM General discussion: RE: Name considerations

Lol
I think I like Hydrilla marginally more that Lernette. Let's wait for at least one more opinion. Maybe from Co... koszko

09:23 AM General discussion: RE: Name considerations

That idea was very good- it seems like a promising path!
I *would* support the genuinely lovely Hydrette if not fo... jahoti

08:51 AM General discussion: RE: Name considerations

Remember the Hydra idea? Maybe "Hydrette"? Or "Lernette"? koszko

08:58 AM Development: RE: Revamped javascript build system

On Mon, 5 Jul 2021 15:51:36 -0500
Colby Russell <js-extensions-discussion@x.colbyrussell.com> wrote:
> On 7/5/21 ... koszko

07/05/2021

01:45 AM General discussion: RE: Name considerations

Not a very nice one either it seems :/.
While I don't think the overlap is semantically close enough or widely rec... jahoti

02:25 PM General discussion: Name considerations

Somebody on the Trisquel forum noted the name "Hachette" is already being used by some book publisher. See:
https://... koszko

07/02/2021

11:40 PM Development: RE: Revamped javascript build system

It's definitely a nice hack. However, to actually implement it risks creating a real inconvenience for the sake of pu... jahoti

09:21 PM Development: Revamped javascript build system

Colby suggested making the build system cross-platform by rewriting it in javascript contained in a standalone html f... koszko

11:09 PM General discussion: RE: NLnet fund application

In other words, it would be incredibly and profoundly helpful to have support from someone- or some people- with more... jahoti

09:31 PM General discussion: NLnet fund application

On Thu, 1 Jul 2021 08:30:00 +0000
jahoti wrote:
> The beginnings of an NLNet application are now in the
> brows... koszko

09:39 PM General discussion: Remine setup

On Thu, 1 Jul 2021 10:05:58 +0200
"W. Kosior" wrote:
> Hi,
>
> I set up an issue tracker[1]. Come and make aco... koszko