I started running an private MediaWiki instance during the pandemic as I wanted something with a nice editing experience rather than editing markdown documents. I almost went with a self-hosted Confluence instance :P
Mediawiki is very very nice and it has a lot of cool features i've been loving over the years.
One of the things i like the most is the ability to embed a PDF document so that it's both downloadable and browsable from the wiki page itself (it embeds the browser pdf engine).
This means that i can, say, have a page for my microwave oven and have its user manual easily available.
Lately I've been thinking how to connect that with some LLM, most likely there's a chance to do some interesting things :)
Right, my suspicion was correct. When I interacted with them a few years ago they seemed perfectly nice and friendly, but seem to have gone off the rails more recently. It's an uncomfortable situation and I've a feeling people are afraid to discuss this kind of thing but we really need to. People are a risk factor in software projects and we need to be resilient to changes they face. Forking is the right way, but places like GitHub have sold people on centralisation. We need to get back to decentralised dev.
> but places like GitHub have sold people on centralisation. We need to get back to decentralised dev.
I don’t think that’s the case. It’s more of a marketing/market incentive. It’s great pr to be associated with the most famous project, way less so to be associated with a fork, at least until the fork becomes widespread and well recognised.
GitHub does make it fairly easy to fork a project, I wouldn’t blame the situation on github.
Just look at how much of the drama is caused by who "owns" the repository. In a decentralised model, which git perfectly supports, everybody owns their own branch(es). But all the issues etc. are stuck on the GitHub project.
> In a decentralised model, which git perfectly supports, everybody owns their own branch(es). But all the issues etc. are stuck on the GitHub project.
yeah i'm gonna call BS on this. this kind of drama already existed when communities were "decentralised" and each one had its own forum, mailing list or whatever.
the core of the issue here is about wanting to be the owner of a repository.
so people should just not bother with being owner of a specific repository, but just fork it and move on. and github supports forking sufficiently well for this purpose.
I think that may be the first time I've seen licensing drama over something as minor as adding another author to the copyright list.
Pretty sure those are completely standard for major changes in maintainers/hostile forks/acknowledging major contributors. I've seen a lot of abandoned MIT/BSD projects add a new line for forks/maintainers being active again in order to acknowledge that the project is currently being headed by someone else.
From my "I am not a lawyer" view, Kludex is basically correct, although I suppose to do it "properly", he might need to just duplicate the license text in order to make it clear both contributors licensed under BSD 3-clause. Probably unnecessary though, given it's not a license switch (you see that style more for ie. switching from MIT to BSD or from MIT/BSD to GPL, since that's a more substantial change); the intent of the license remains the same regardless and it's hard to imagine anyone would get confused.
I suspect (given the hammering on it in responses), that Kludex asking ChatGPT if it was correct is what actually pissed off the original developer, rather than the addition of Kludex to the list in and of itself.
The original author said they were “the license holder”, specifically with a “the”, in discussions around both Starlette and MkDocs, which yes, just isn’t true even after rounding the phrase to the nearest meaningful, “the copyright holder”. This appears to be an honest misconception of theirs, so, not the end of the world, except they seem to be failing at communication hard enough to not realize they might be wrong to begin with.
Note though that with respect to Starlette this ended up being essentially a (successful and by all appearances not intentionally hostile?) project takeover, so the emotional weight of the drama should be measured with respect to that, not just an additional copyright line.
lovelydinosaur appears to be undergoing a mental health crisis. Besides the drama and lies, I notice they (I think they?) seemed to misname the maintainer on purpose. They did it in the first thread, which the maintainer tried to correct, and they misnamed him again in the second thread.
Mia Kimberly Christie seems like dangerous person.
This has been ongoing for some time. I’ve raised valid issues in several encode projects and received rude/dismissive comments from this individual. I’ve reviewed their recent interactions with others on GitHub and it’s obvious that Mia (tom?) is super toxic/drama seeking
At least it can be easily disassembled, compared to other Apple products. Then the third party components will be available for cheaper prices than Apple.
I was more worried by the 600kW power requirement... that's 200 houses at full load (3kw) in southern europe... which likely means 400 houses at half load.
the town near my hometown has 650 – 800 houses (according to chatgpt).
I think the above commentor is reflecting on the total energy use from having a 600KW load running 24/7. I suppose the more interesting observation is the 14 MWh of daily consumption, enough to charge 100 Rivians every day.
> and heat pump cooling / heating became the norm.
We're not all solidly middle-class (especially in Southern and Eastern Europe) and as such we cannot afford those heat pumps. But we'll have to eat the increased energy costs brought by insane server configurations like the ones from the article, so, yeey!!!
This particular project is making a small political point, that this attempt at regulation of FOSS is useless and easily circumvented. The impact is proportional to the effort (small) but it’s not useless any more than running an ad would be.
Ageless Linux is a similar project, but with a larger possible impact, as it has the potential to serve as a test case for overturning the law. By directly and flagrantly violating the law, it serves as a magnet for prosecution.
You could have avoided the worry completely. Ssh goes over tcp that does transport control (literally the “tc” in “tcp”) and this includes retransmission in case of packet loss.
If you are on a high latency ssh connection and your password does not register, you most likely mistyped it.
I am aware of that but you forgot the other conditions. Keys sometimes don't register, I'm not sure why but I do experience missing keystrokes.
The passwords get updated irregularly with the org IAM so you aren't sure what the password even is. Pasting doesn't work reliably sometimes, if you're on windows you need to right click to paste in terminals, sometimes a shortcut works. Neither gives me any feedback as to what event was ever registered though.
reply