inmysocks (version: awoo) @inmysocks@awoo.space

this comes up because the gitlab install on my local pieserver was way out of date. I had version 1.1.0 and the newest version is 1.9.6.

I need to figure out what the updates are, aside from topics. Topics are awesome and the one thing that I was missing compared to gitlab/hub.

Someone makes a huge complex piece of software and tries to sell administration and maintenance as a service, then someone else comes along and is like 'or you could do it in this really simple way that requires almost no resources'.

Not that I don't like gitlab, they are rather important in the alternative to GitHub sense, but you are going to have maybe 100 organisations in the world that need something that can support the type of traffic required to justify something that complex.

I will always be a bit entertained by how gitlab is a (relatively) big bulky installation that affects a bunch of stuff and takes up a bunch of resources. My pi 2 had some troubles with it with more than one person. then gitea is like 'the executable is less than 100mb, requires no external dependencies and it take about 30mb of ram if you have 2 or 3 people using it'

I get that gitlab is made for a much larger workload, but the difference in complexity is amusing.

also there is the whole npm vc thing going on.

That makes breaking the reliance on npm a bit urgent.

Disclaimer: There are plenty of amazing things about Node, I use it all the time.

My biggest complaint is still that node indicates synch/async backwards. Almost everything is synchronous aside from a few functions. But instead of naming the function that are different (in the sense of asynchronous) they label the versions that match the behaviour of everything else.

That is bad design.

Also:
path.delimiter
path.sep

WHAT THE FUCK? Pick a convention node, you're drunk.

and now, same douche, is pushing to follow the progressive web app standards because 'otherwise the available technologies won't be available to us'....

Somehow not fitting googles standards now mean that browser caches and the like aren't available to you?

This guy has to just be fucking with me.

@zatnosk it is getting very close to the point where flying to Australia for that seems reasonable

@zatnosk I don't think that he is willing to learn even that much. I am pretty certain in his mind it means that if I just did this magic thing he could suddenly have his browser autosave files anywhere on his hard drive.

This is after multiple explanations from me and me sending him a bunch of references about what both progressive web apps are, what local storage is and restrictions on browser access to the file system.

Like I said, ARGH

also, progressive web apps certainly feel like a Trojan horse that is there to help move people from having any local applications to using applications that are purely on remote servers like chromebooks

this same douche keeps harping about how we can just make a progressive web app because they use localStorage which means we can save whatever we want to the local file system.

This is after me explaining multiple times that localStorage is not the same as file system access, it is a browser cache with some makeup on it.

And the 30 seconds later he says 'what do you have against progressive web apps? They would let us access the file system!'

CORS headers seem counter productive to me.

The browser doesn't allow cross-origin requests for security.

But there are times when you want to be able to do cross-origin things.

CORS to the rescue. But instead of going with the whole 'security' thing where your browser would determine if cross origin things are allowed, the remote server gets to tell your browser that it is allowed.

'Don't talk to strangers, unless the stranger says it is ok, then they can do whatever they want'

@ekaitz_zarraga quite possibly, it has come up before.

Every time I have a client project that takes me away from python for a while I forget all the ways that it makes me hate it.

I may have a complicated relationship with python.

*ahem*

WHY THE FUCK DO YOU HAVE ANY SITUATION WHERE A FUNCTION CAN HAVE AN INTERNAL STATE YOU FLAMING DOUCHE BISCUIT???

In case you are wondering:

Setting a default function parameter to a mutable value means that the default parameter changes for every function call if the parameter gets changed inside the function.

I remember reading that before, but it was still 2 hours of my life

I think that a lot of the privacy and security problems with DHTs are made much simpler if you just don't assume a global DHT.

There are plenty of uses for resilient meshes with a distributed data store.

The more I look at how the back-end works the more I want to make a c++ version of pouchdb so bindings into other languages like python work better.

LevelDB already does most of the heavy lifting.

Some npm modules really confuse me.

One is a wrapper on the core crypto library. In the sense of:

module.exports = require('crypto')

and one is a wrapper on a single one-line function that just calls a function in another library with the same arguments it is passed.

This seems gratuitous.

@desikn it makes for a much nicer fediverse experience.

There are a few people on M.S. that I care enough to worry about which is why I have this account. I just haven't been bothering to separate out tech stuff to put here.