AnswerOverflow VS memory64

> TOO many bots log entire channels out to public html sites. This is prevalent in everything like discord etc but the degree to it in IRC is just ridiculous god knows what any of those 1500 bots in a channel are doing.

These sorts of bots are quite rare on Discord, you usually have to make an account to be able to see anything. There have been attempts at standardizing this (like https://www.answeroverflow.com/) but they haven't taken off. Public logs are much more common on IRC than on Discord.

Related: AnswerOverflow makes Discord messages searchable on Google/ other search engines. It’s open source.

https://www.answeroverflow.com/

I agree that the discord centralization for Q&A is becoming problematic, it makes it less discoverable and searchable (Had this problem a lot with Svelte).

That said, I have had success so far using https://www.answeroverflow.com/ to search discord for questions. It sucks we have to use such tools, but given the current situation, it's also better to adapt.

We've started mirroring our Discord to the web using https://www.answeroverflow.com/

You could roll your own equivalent but AnswerFlow has some nice features and handles issues around consent nicely.

If you're starting a Discord then I'd strongly recommend stating upfront that you might mirror content to another location even if you're not doing it now - it makes it a lot easier than doing so further down the line.

A better solution would be to not use Discord but friction, push-back from my colleagues on alternatives and a fear of fragmenting the community made this the best option for us.

A completed implementation of memory64 for memory-hungry applications.

Indeed, webassembly is moving extremely slowly. I started a project years ago expecting https://github.com/WebAssembly/memory-control/blob/main/prop... and https://github.com/WebAssembly/memory64 to be fixed at some point. Neither are yet, and the project still suffers from it to this day.

I think wasm is still great without these fixes, but I have lost confidence in the idea that wasm will reach its full potential any time soon.

It's in the works: https://github.com/WebAssembly/memory64

Starting with 32bit had some performance advantages because 64bit runtimes can use virtual memory shenanigans to implement bounds checking with zero overhead. In wasm64 they'll have to do explicit bounds checking instead.

Right - currently, everything runs using WASM (32-bit, with 64-bit coming soon [1,2]), and I plan to add support for WebGPU soon!

(WebGPU is the successor to WebGL, which is coming out in April 2023 [3])

[1] https://github.com/WebAssembly/memory64/issues/36#issuecomme...

It shouldn't be a big surprise that a 64-bit pointer extension is out there and being worked on. The great thing about a VM is you can integrate major changes like this when they are needed and with the benefit of experience and hindsight. If the 4GB limit turns out to be restrictive then it can be lifted.

The goal of this proposal is to increase the amount of memory that canisters can access [eventually] bound only by the actual capacity of the subnet. Since, the Memory64 proposal is not standardized 1 yet and its implementation 1 in Wasmtime is not production ready yet, this proposal enables the increase by introducing a new stable memory API.