@icedquinn I think the idea is that websites need to gain consent in order to use cookies.
@icedquinn @zleap Well, now I can at least give a nice "f u" when someone want me to allow Zuck and Pichai to track me
@Archivist @icedquinn I just tell people I don't use faceook, may have to start assuming some fb users are thick as they don't get it
btw who is Pichai
@icedquinn @Archivist Never heard of him, LOL
@zleap @icedquinn Just the CEO of the Alphabet Group that contains Google, Youtube and all their other pet projects
The fact you never heard of him is sign he takes his role as a villain very seriously
@Archivist @icedquinn Yeah, or that I don't use / care about google enough. I do know that @cwebber is one of the people behind Activity Pub.
I use Google mostly because (ironically) the GNU guys make a terrible job at documenting stuff in a navigatable way. They also have to discover PDF as an information format as for most of them.
@Archivist @icedquinn @cwebber
I am not sure how to address this, we need to educate people, thing is when you document you start to realise how easy or difficult your software is to use, as you need to think as a user and not a techy / programmer that created it.
As someone that has to teach people how to use git and had to make my own textbook for it. I concur.
I would also say you don't have mastery over that you can't explain to a non-expert. This is part of what makes me wary of most GNU projects: the bad documentation is a sign of a more devious, subtle problem
@Archivist @icedquinn @cwebber
Good point,
LibreOffice has a whole team of people working on Documentation, they care about the project enough to create good documentation.
I am guessing as you can also buy copies of the manuals it is a good way to generate income for the project overall.
@Archivist @icedquinn @cwebber @libreoffice
I am with you on LaTeX, it is handy to know how to use LibreOffice though,
@Archivist @icedquinn @cwebber @libreoffice
I am currently writing the OU Space Science Club newsletter in LaTeX, I like being able to do \href{url}{link text} or from issue 3 use
\includefile{filename} to include other sections, this also makes re-arranging them a very simple process.
And being able to have a nice blue box with consistent rounded corners and a nice consistent gradient background, beautifully arranged title sections and consistent and easy page numbering... It is a godsend
@Archivist @icedquinn @cwebber @libreoffice
Indeed, are you using tcolorbox for that or similar, nice package, getting my head round it slowly.
@Archivist @cwebber @libreoffice @zleap i was more excited about booklit syntax before i read the part that parsing is somewhat selective. you have to look up mid-parse if a function wants you to parse the body text or just hand it in as-is which complicates things a bit but we’ll see.
scribble is a bit onerous to parse but i’ve done most of that work and you just get a pile of plain old s-expressions to run through to whatever format you want.
but in the end its either \foo{...}
or @foo{...}
most of the time.
Yeah but why not just use TeX with next to no premade macros? Would it be that different? I feel like simple TeX-like macros would be easier to implement and do the job mostly fine while compartimenting the workload more easily
New project: making an "HyperTeX" processor that generate html with a TeX syntax. Probably a few hundred lines of C, but definitely useful.
Booklit doesn't really follow the correct syntax though, and it doesn't have environments either. It doesn't support defining new commands in itself or all of the bells and whisles of TeX
@zleap
I am pretty familiar with Calc and Draw, but letting me in charge of doing something consistent with something that is not automated is clearly a way to end up with Cthulu taking a nap in your bathtub
@icedquinn @cwebber @libreoffice