| Time |
Nick |
Message |
| 00:58 |
|
figboot joined #minetest-dev |
| 01:01 |
|
sugarbee1 joined #minetest-dev |
| 01:04 |
|
Pexin joined #minetest-dev |
| 03:00 |
|
SFENCE_arch joined #minetest-dev |
| 05:00 |
|
MTDiscord joined #minetest-dev |
| 06:25 |
|
SFENCE_arch joined #minetest-dev |
| 07:25 |
|
wasm1234 joined #minetest-dev |
| 07:26 |
wasm1234 |
what if a native WASM runtime was used as a sandbox for SSCSM |
| 07:44 |
|
hwpplayer1 joined #minetest-dev |
| 08:12 |
|
tibtoblezob joined #minetest-dev |
| 08:36 |
|
MTDiscord joined #minetest-dev |
| 11:34 |
|
pgimeno joined #minetest-dev |
| 12:10 |
|
SFENCE joined #minetest-dev |
| 13:50 |
MTDiscord |
<exe_virus> Appropriate username. It's actually been discussed on the discord. The answer is we'll probably just use the Lua runtime for safety, not WASM. There are other things we'll need to pull off before we go that route. Check the roadmap |
| 13:50 |
sfan5 |
they left seconds after posting, so not like they'll see it anyway |
| 15:40 |
sfan5 |
merging #15705, #15700, #15707 in 10m |
| 15:40 |
ShadowBot |
https://github.com/minetest/minetest/issues/15705 -- Update github URL references by sfan5 |
| 15:40 |
ShadowBot |
https://github.com/minetest/minetest/issues/15700 -- Add setting callbacks for Camera and TouchControls by grorp |
| 15:40 |
ShadowBot |
https://github.com/minetest/minetest/issues/15707 -- Restore proper rollback database indexing by appgurueu |
| 15:40 |
sfan5 |
does anyone want to review #15680 or should I merge it too? |
| 15:40 |
ShadowBot |
https://github.com/minetest/minetest/issues/15680 -- Propagate peer ID change to outgoing reliables by sfan5 |
| 15:52 |
MTDiscord |
<warr1024> "they left just after asking" ... I can't be the only person who has thought of the workflow of just popping in, asking a question, leaving, and then grepping the public logs the next day to see if it got answered. I might be the only person who's likely to setup a cronjob script to do the grepping and push me a notification if it did get answered, though... |
| 17:49 |
[ |
SSCSM is a mistake, for both software freedom and security reasons |
| 18:54 |
MTDiscord |
<exe_virus> You assume it'll be forced on users. It won't be. |
| 18:54 |
MTDiscord |
<exe_virus> Especially because we're all so paranoid |
| 18:56 |
sfan5 |
if we move features to SSCSM at high pace I can see base Minetest Game requiring SSCSM in 4 years |
| 18:56 |
|
Desour joined #minetest-dev |
| 18:57 |
MTDiscord |
<warr1024> Haha I have a hard time imagining MTG changing that much in any number of years |
| 18:58 |
sfan5 |
I'm thinking more like "movement gets moved to sscsm" so MTG is forced to step in with a legacy implementation |
| 19:24 |
MTDiscord |
<luatic> heh yeah |
| 19:24 |
MTDiscord |
<luatic> What we call "SSCSM" is a necessity for something that wants to call itself a game engine in the long run. |
| 20:06 |
|
SFENCE joined #minetest-dev |
| 20:11 |
|
tibtoblezob joined #minetest-dev |
| 23:33 |
|
panwolfram joined #minetest-dev |
