This is why Firefox chose to implement a custom PDF reader in pure JS for better sandboxing leveraging the existing browser JS sandboxing.
As a side effect, it's been a helpful JS library for embedding PDFs on websites.
The Chrome PDF parser, originating from Foxit (now open-sourced as PDFium), has been the source of many exploits in Chrome itself over the years.
And the end of their self hosting offerings (Server, Data Center), which is currently driving a lot of people towards XWiki, for other reasons than money. XWiki SAS being mainly in Europe makes it attractive to EU users too.
> do you have any migration tips?
I don't have specific migration tips. I hope the docs are complete enough!
The Confluence Migration Toolkit is based on the Confluence XML module you found, but it adds a nice and convenient UI, converts some more macros that XWiki SAS sells, there's support, and there's consulting for larger migration projects or projects with special requirements.
(note: despite some paying features, everything is open source)
(disclaimer in case it was not obvious, I work for XWiki SAS)
Amusingly, exactly opposite experience here. That said, our on-prem is jira and confluence integrated with db on same machine, and apache in front doing additional caching. I imagine like so many things it is how you set it up...
Well, the article notes that it seemed effective on human tissue samples.
The researchers also tested cartilage taken from patients undergoing total knee replacement for osteoarthritis. After one week of treatment with the 15-PGDH inhibitor, the tissue showed fewer 15-PGDH-producing chondrocytes, reduced expression of cartilage degradation and fibrocartilage genes, and early signs of articular cartilage regeneration.
So, IMO that shows hope for once it goes to trials.
Checking the Firefox bugs on this, it seems they decided to replace the C++ libjxl with a rust version which is a WIP, to address security concerns with the implementation. All this started a few months ago.
Maybe the zen fork is a bit older and still using the C++ one?
... update. after reading the comments in the rust migration security bug, I saw they mentioned "only building in nightly for now"
I grabbed the nightly firefox, flipped the jxl switch, and it does indeed render fine, so I guess the rust implementation is functioning, just not enabled in stable.
... also, I see no evidence that it was ever enabled in the stable builds, even for the C++ version, so I'm guessing Zen just turned it on. Which... is fine, but maybe not very cautious.
Google Chrome is using a Rust implementation. The existence and sufficient maturity of it is the reason they were willing to merge support in the first place.
I suspect that applies specifically to their cloud rewrite which was apparently a bloat of JS libs and hundreds of requests even by Atlassian standards. The on-prem self-host Confluence I've used is still pretty snappy and pleasant to use and without throwing an absurd amount of resources at it. We do have quite a lot of actually-useful documentation in it.
That said, Atlassian is busy relentlessly raising the price for self-host to push people into their cloud roach motel, so we'll probably be on some alternative (either FOSS or commercial, but self-host) soon too.
In mercurial you could have those in phase hidden for future reference.
In jujutsu you can have those in a local set, but not push upstream. Only unfortunate thing with jujutsu is because it is trying to be a git overlay, you lose state that a mercurial clone on another machine would have.
Click Reader mode on a web page, then the read aloud option in the sidebar.
Note that how well it works on Linux will depend on your distro and default settings, as is common for Linux world. They do try to provide setup instructions if your linux distro has issues.
... now whether that model is integrated by default, no idea. I imagine that depends on size.
Oh, and mozilla's off-line translate for private translation of web pages... that's another neat AI thing they added that I've found super helpful. Chrome still requires sending the content to their servers.
Ah cool, thanks, didn't know this existed. I just get a dummy message when playing audio, so I'll play around with some speech dispatcher[1] solutions later!
> Oh, and mozilla's off-line translate for private translation of web pages... that's another neat AI thing they added that I've found super helpful.
Yes, it's awesome! And one of my favorite additions to Firefox in many years, it's stuff like that they should focus on if they want AI, imo.
I tried it, and I'm sure it's not a based on any language model. Sounds like espeak-ng or its ilk, so it probably uses whatever's available?
The TTS repo was updated 5 years ago and links to installation instructions for Ubuntu are broken :/. Also the docker repo is archived, but only recently, so maybe it works.
All in all, doesn't look like the project is alive at all.
It definitely uses whatever is available, but on review of the models (and there are quite a few) the ones I checked included instructions for integrating into linux speech engines.
What your distro uses by default might be espeak-ng, but you could use mozilla TTS or festival or piper or anything else. It makes sense to not bundle an entire system that repeats things that are available on all desktop environments and mobile these days, but instead call out to those from the browser functionality - especially given the enormous size of high quality speech models - not to mention the localisation issue. I think the TTS project was just to increase availability of high quality FOSS alternatives. Getting those into your distro is more of a distro packager thing.
It's probably a pretty natural path for the wasp assuming it survived the initial time you were running the vac. The shopvac is just a big container with at the top an exit path following the wall naturally out the tube. They don't even tend to have a flap like smaller hand vacs might have to keep dust from falling out during use.
And performs very well on the latest 100 puzzles too, so isn't just learning the data set (unless I guess they routinely index this repo).
I wonder how well AIs would do at bracket city. I tried gemini on it and was underwhelmed. It made a lot of terrible connections and often bled data from one level into the next.
I mean, the repo has <200 stars, it's not like it's so mainstream that you'd expect LLM makers to be watching it actively. If they wanted to game it, they could more easily do that in RL with synthetic data anyway.
Belated update on this. Gemini reasoning did much better than quick on bracket city today (an easy puzzle but still). It only failed to solve one clue outright, got another wrong but due to ambiguity in the expression referenced and in a way that still fit the next level down making the final answer fairly cleanly solved. Still clearly has a harder time with it than the connections puzzle.
The Chrome PDF parser, originating from Foxit (now open-sourced as PDFium), has been the source of many exploits in Chrome itself over the years.
reply