🔲 🔲 **FUNDS RECOVERY **🔲 🔲

⬛️ **HAVE YOU FALLEN VICTIM TO A FRAUDULENT INVESTMENT SCHEME, CRYPTO SCAM Or OTHER TYPES OF SCAMS???**

⬛️ Are you struggling to get back the money you lost? You’re not alone. Every day, countless individuals face the devastating impact of scam operations that drain their hard-earned savings. But there’s good news – we are here to help you recover what’s rightfully yours.

⬛️ Truth be told, the only Specialists that is capable of retrieving your lost funds from online scams, fraud and scam investment websites are Team of PROFESSIONAL HACKERS & CYBER FORENSIC EXPERTS, we are the Funds Recovery Expert who knows various Retrieval Techniques and Strategies that suits different scenarios of Scam

⬛️ At Funds Retrieval Panel, we specialize in Funds Recovery using advanced technology with the help of our Top notch hackers and cyber forensic experts that works cooperatively with the use of various Advanced technology softwares, hardwares and AI’s to retrieve your funds from fraudulent investments, crypto scams, and malicious online schemes. With years of experience in the financial and tech sectors, we are the trusted solution for individuals looking to recover lost money.

⬛️ We don’t just promise results – we deliver them. Our expert team has successfully recovered Billions of dollars for clients who have fallen victim to scams

⬛️ CONTACT US NOW to schedule your free consultation and start the process of recovering your funds.
🌍 www.fundsretrievalpanel.com 🌍
📩 info@fundsretrievalpanel.com✉️

I think I understood something. Your logs contained:

out/web/bleach/hydrogen_sulfide/in-the-laboratory-h-2s.bigb

so probably this was a leftover from before we moved from out to _out, you should just remove that folder.

Installing ourbigbook locally is generally the best option, because this way you have a specific version for it on your package.json that you know conversion will work at. See e.g. the template repository for an example: github.com/ourbigbook/template But global install with -g should work too.

About the title of the first header of index.bigb, you can call it whatever you want. It will always have a magic empty ID + a synonym for the title e.g. pioyi-s-index. The title will only show up on static renders like github.com/ourbigbook/template, on ourbigbook.com you see "Home" and your username instead: ourbigbook.com/cirosantilli

All good!
I installed ourbigbook globally instead of locally and it worked. (I am not very experienced with web development hahahhaha)

Sorry for that...
Also by the way I changed the top header's name from index to

From what I understood this is the new way of doing things

Also just to check, which commands are you running exactly? Just ourbigbook --web for upload or something else?

Also, consider updating ourbigbook with:

npm install --save ourbigbook@latest

I've been doing releases regularly, and I can see you are not at latest because now they output directory is called _out. Just in case.

Hello!

It's just using the cute (and recommended) syntax:

= My header

as opposed of the saner longer one:

\H[1][My header]

I should rename this cute but confusing terminology: docs.ourbigbook.com/#insane-macro-shortcut

Could you double check that the sample code is displaying correctly? Backslash in \= should escape the = and not create a header, so I'm assuming it is a formatting error? Or do you actually have backslash in your source code?

You can just dump basically any code directly inside backticks for your sample, you don't need to escape special characters there unless the code contains backticks itself

I think I broke it again hahahhahaha

What are insane headers? I couldn't find any info in the documentation (only about insane block quote).

This is some relevant source code:

And this is the error message:
error: out/web/bleach/hydrogen_sulfide/in-the-laboratory-h-2s.bigb:1:24: insane header cannot contain newlines

I should probably read the whole documentation once. (Probably this message won't be formatted well enough. This is another reason why I should read the docs)

OK, I've now enabled the mhchem katex extension so you can write stuff like:

$$
\ce{H2O}
$$

Awesome, good luck in the exams 🤞 I'll give it a quick try later on.

Hello Ciro! That would be great!
I haven't posted anything new in a while... I have learned a lot of new things.
When the exams are over I will surely share some stuff about organic chemistry and spectroscopy.

No, the more people break it the better!

Didn't mean to break it, sorry for that XD

hahahhaha yes it was unintentional. Thanks for the info

OK, I've release a fix that will prevent the header newline issues from happening again on server and it also gives a local warning: github.com/ourbigbook/ourbigbook/commit/dc85cf067b926a73f4b17704afcfc29f75b164ea

Also consider:

npm install --save ourbigbook@latest

to get these local conversion updates and a few others I've added recently.

Thanks a lot once again for this report! Local to web upload is hard to get right, and I've had many issues myself, but I try to fix this with high priority, and new users stress it in different ways which is great.

A tip, during web upload, ourbigbook first splits the headers to separate files under out/web, so looking there can help understand what went wrong. But not something I want users to ever have to worry about of course, the goal is that if it converts locally without error, it should upload without error.

Hahahhahaha I had forgotten its purpose!

OK awesome!

Both of these issues will soon start giving a much clearer and early local error since: github.com/ourbigbook/ourbigbook/commit/c12a72172de22dd356e8b4cb3a9d5fe67c0555f9 which I had recently implemented I just haven't released it yet, I'll ping it when I do for npm update.

Your files have to be really huge before being in a single file starts becoming a problem, so don't worry too much about it.

Previously cirosantilli.com was one humongous README.adoc, but it reached a point where the HTML was too slow to load lol.

That was part of the motivation of ourbigbook. But when you reach that point, ourbigbook makes the transition to multifile will be as seamless as it can be.

BTW you might want to use the {parent= syntax rather than header levels.

= My h1

= My h2
{parent=My h1}

= My h3
{parent=My h2}

This allows you to move chunks around very easily (within the same file, or to other files), without having to change a billion header levels each time.

Don't mind the escape characters on the {scope}. This was not supposed to be written like that

I got it to work! There were two problems: First:

I solved this by adding a new line after the {scope}

Then:

This gave me an error of: Headers are not allowed in OBB Web Articles. Fixed it by adding a new line again.

I do not work with \Include because I had trouble figuring out how to do that. I will try it in the future again hahahha. Now it's a big monolithic mess

You could also consider pushing your local source to a public github repo to make it easier to inspect. Also a good idea to backup it in git anyways.

Hmm can you give a bit more of the error logs and perhaps local source? Also double check that every file is reachable from the README.bigb via \\Include (I'm going to add a local check for this soon).