Well github is very much owned by Microsoft, and with the recent changes of the CEO there are a lot of reasons to prefer a non closed source and non-gigant-tech-corp-controlled software forge.
Not really. It probably got overloaded with requests and thought that another crawler was tergeting the repository so it probably bumped up the measures.
Once I reach the $5000 per month goal across all funding platforms, features currently exclusive to the private fork of Anubis for corpos (including changing the images and soon HTML templating support: https://anubis.techaro.lol/docs/admin/botstopper) will be merged into the open source repo.
Thanks for the answer. To be clear, although I'm not a huge anime person, I don't have any issue with the mascot itself. I meant my question as "why is the Anubis mascot an anime girl [instead of an Anubis]", but it seems my intention was misread over the internet.
I love the idea of Anubis, but in practice, it has turned more than a few sites that I visit into sites that don't work without javascript. So instead of being happy to see it, I find myself disappointed and frustrated, often deciding not to bother with the site after all.
It's off by default while the false positive, true positive, true negative, and false negative rates are being evaluated. This is how you make changes like that without breaking user expectations.
That's good news. That'll make me consider using Anubis.
Thanks for fighting the AI bots.
You get some hate for this anime girl image but this paid white label thing is a good idea I think. It's nice we have alternative ways of funding free software that doesn't involve ads and tracking and thank you for choosing this path.
There's a solid strategy behind it: give people what they want with a flaw that makes it unviable for corpos. Then sell the cure. I remember being told that monetization model as a joke and figured this would be one way to test it. The horrifying part in my book is that Anubis is a relative success story as far as open source funding goes, and it's barely a third of what a junior level software developer makes. It's maddening.
Interesting. I suppose I need to try this if I ever happen to build something to which it could apply. Thanks for the inspiration.
A third of a junior salary is not much but I guess it could help with at least turning a full time position into part time.
> I remember being told that monetization model as a joke and figured this would be one way to test it
Ah ah. Awesome.
It has happened to me once or twice that I jokingly share an idea, and it gets picked up seriously (in a professional setting). "But it was a joke! Too late. Oh no." - I guess it's not too bad in the end and shouldn't be fighted too hard. I guess I'll just make sure that if the idea is horrible, I don't make the joke if I think people around could seriously pick it up.
I took a look at the Github profile linked in your profile here, and it linked to a Steam profile with anime characters in the showcase section and that made your objection to the "anime girl" way more baffling.
egui is nice but its API changes a lot between versions which makes it hard to rely on. Slint is stable and well documented. Its license is open source and also free to use in many cases so there is no real issue there.
Tests do not account for all possible executions of the code, rather only a subset of it.
Rust is indeed a safe language, in terms of memory safety. Vulnerabilities are still very possible within a rust program, they just need to not rely on memory exploits, and the borrow checker won't catch them. That is why formal verification exists. If you have a really critical, high security application then you should ensure the maximum amount of safety and reliability.
Formal verification enables the developer to write a mathematical proof that the program behaves correctly in all situations, something that the borrow checker cannot do.
I guess apple works more as a "cultural monopoly", where if you don't own some apple device you're automatically ostracized by other apple customers. To them apple is more like a fashion clothing company like gucci than a technological one. Apple provides some sort of "privileged status" to their customers, just like purpur in ancient rome, so of course each apple stan considers themselves superior, and to keep their own privilege they need to buy more apple products.
What a bunch of nonsense. I don't buy Apple products because someone might make fun of me if I don't. It's because they are best in class and integrate so much better than any competing offering.
Good for you. That doesn't change the impression that many of us have when we see relatives and friends who buy Apple products yet have low incomes. I'm pretty confident they aren't doing it because of any technical superiority and they certainly aren't doing it because the devices last since they upgrade every couple of years.
I've tried hard to understand their perspective and I've had to conclude that there perspective does not include the technical superiority of the devices but is driven mostly by a wish to seen to be part of the IPhone owning group.
And so? Yes people (and companies) would fork your code, but the most realistic scenario would be that the original ladybird would still be the most relevant browser of it's family, just like firefox, so the problem kinda resolves by itself
Because apple themselves forked it. Only a handful of companies have the power to basically change the web browser market, and apple sure was one. Nowadays every company copies from chrome, so why would anyone bother forking ladybird?
Doesn't this contradict with what you said? According to your previous comment, even if Apple has forked KHTML, it shouldn't harm Konqueror, and it shall prevail as the most popular of its family.
However, Konqueror/KHTML is now dead and we only have a closed source Safari.
As I've already stated, any company that may fork a similar project would actually cause more benefit than harm. KHTML died because the web started to get very complex very fast and KDE volounteers couldn't keep up with that pace, unlike Apple employees. Now that the web is a bit more stable, with less standards that are more thought-out (webassembly), it's a lot easier to maintain a web browser. So if tomorrow Microsoft hops in and announces it's intent to fork ladybird, then the latter would not only be fine, but it would probably recieve a new wave of contributors.
Imagine if ladybird gets used regularly by ~1000 nerds, which is its current audience, then gets forked by microsoft and the current ME gets replaced by ladybird. Even if ladybird got over 9000 users, there's no competing with megacorps.
Well maybe they're ok with that? They want browser diversity. Getting Microsoft to use a new engine is better for diversity than if they just used chromium like now.
Getting Microsoft to use a new engine and contribute back to the original repository is better for diversity, but forking and running away with it is certainly not.
> Forking and running away with it is certainly not
If your goal is browser diversity, this would take an ecosystem of 2 browser engines and turn it into an ecosystem of 4. That seems in-line with the goal of browser diversity.
Currently we have an ecosystem of two browser engines, yes. One of them is weaponized against users by its designers, both in its open and closed form.
Having 4 (or 3.5 more realistically) browser engines where 2 of them weaponized against its users doesn't change things.
Instead, we should have 3 (or 2.5) browser engines where only one of them is (and can be) weaponized against its users. This is what brings diversity and change.
Ideally, yes. Microsoft should stay away from this, but I wanted to highlight that adopting a technology doesn't automatically make it better for diversity.
Google was almost killing Go overnight because they wanted more user data from people using the language.
Sorry for my grammatical mistake, English is not my first language.
That said, my point here was that realistically no company is going to fork ladybird since there's already chromium, plus even if ladybird was somehow forked by let's say microsoft and got popular, I don't think it would be detrimental to ladybird itself, if not even beneficial, since it would attract more users and, to a lesser extent, more contributors.
Isn't webGL's GLSL directly delegated to the driver just like normal OpenGL? Also one could easily write a lot of frontends and a single massive centralised backend with multiple processor targets and optimisation profiles. Think about V8 which works for both JavaScript and WebAssembly. This would create a much simpler codebase and if you're going to use a parser generator it could very well be a breeze.
> Isn't webGL's GLSL directly delegated to the driver just like normal OpenGL?
Perhaps you could in an MVP implementation, but in practice no, none of the serious implementations do that by default. First because native OpenGL drivers are generally a mess, so browsers actually implement WebGL on top of DirectX, Vulkan or Metal wherever they can, and even when those aren't available the browsers still parse, validate and reconstitute the GLSL rather than passing it straight through to OpenGL as a layer of insulation against driver bugs. Chrome and Firefox do have hidden feature flags which bypass that behavior and call the native GL implementation directly, but you probably shouldn't enable those unless you're really into ShaderToy and want it to compile faster.
Wow that was something I wasn't expecting. Well I guess it does kinda make sense that running untrusted code on a gpu wouldn't be the best idea, however I seriously thought that browsers just passed their glsl directly to the GPU. Also since linux doesn't have its own graphics API I am afraid that WebGL support would introduce a lot of complexity, since you can definitely pass via OpenGL but Vulkan could be also an option.
ANGLE is the de-facto standard library that all of the big browsers use to implement WebGL on top of other graphics APIs, if you want to read up on it.
To be fair, Catania has more fabs than any other city in Italy (2 with another fab in construction), also being home to the largest stmicroelectronics establishment in Italy, so I guess it kinda is Italy's silicon valley
