| Time |
Nick |
Message |
| 00:23 |
|
fling joined #minetest |
| 00:39 |
|
Lumia joined #minetest |
| 00:47 |
|
Thermoriax joined #minetest |
| 00:53 |
|
Lesha_Vel joined #minetest |
| 01:20 |
|
smk joined #minetest |
| 01:28 |
|
Trifton_ joined #minetest |
| 02:10 |
|
Unit193 joined #minetest |
| 02:17 |
|
Bombo joined #minetest |
| 02:17 |
|
Bombo joined #minetest |
| 02:29 |
|
Trifton joined #minetest |
| 02:40 |
|
sys4 joined #minetest |
| 02:57 |
|
Verticen joined #minetest |
| 03:25 |
|
Lumia joined #minetest |
| 03:40 |
|
bodiccea joined #minetest |
| 03:54 |
|
sometalgoo joined #minetest |
| 04:00 |
|
MTDiscord joined #minetest |
| 04:43 |
|
Trifton_ joined #minetest |
| 04:47 |
|
Trifton_ joined #minetest |
| 04:49 |
|
calcul0n joined #minetest |
| 05:03 |
|
est31 joined #minetest |
| 05:04 |
|
YuGiOhJCJ joined #minetest |
| 05:17 |
|
YuGiOhJCJ joined #minetest |
| 05:53 |
lissobone |
No, testing is part of minetest. |
| 05:53 |
lissobone |
The only alternative name (but still with 'test') I can think of is rubenwardy's Nubetest. |
| 05:54 |
lissobone |
Or even ",omryrdy". |
| 05:57 |
|
TomTom joined #minetest |
| 06:39 |
lissobone |
I think that you'll like my new mod. It's fun. |
| 06:39 |
lissobone |
It is recommended to turn off any acceleration and gravity before using it for best gravityless experience. |
| 07:01 |
|
sec0nd joined #minetest |
| 07:07 |
|
orwell96 joined #minetest |
| 07:17 |
|
Noisytoot joined #minetest |
| 07:45 |
|
Abdou-31 joined #minetest |
| 07:50 |
Abdou-31 |
Hi folks! |
| 07:51 |
Abdou-31 |
is there something called `timpstamp`or it's just a typo? |
| 07:56 |
MTDiscord |
<ROllerozxa> most likely not, that would be "timestamp" |
| 07:56 |
MTDiscord |
<ROllerozxa> (as in, yes that's a typo) |
| 07:56 |
Abdou-31 |
nice! thx dude! |
| 07:57 |
Abdou-31 |
how are you doing today btw? |
| 07:57 |
MTDiscord |
<ROllerozxa> I'm doing good, thanks |
| 07:57 |
Abdou-31 |
nice |
| 08:01 |
MTDiscord |
<Abdou-31> can I change the avatar that shows on Discord whenever I type from irc? it's ugly |
| 08:01 |
MTDiscord |
<Abdou-31> that green thingy |
| 08:14 |
MTDiscord |
<Abdou-31> >* minetest.register_on_chatcommand(function(command, params)) * Called always when a chatcommand is triggered, before minetest.registered_chatcommands is checked to see if that the command exists, but after the input is parsed. |
| 08:14 |
MTDiscord |
<Abdou-31> should I remove "that" or "the" ? |
| 08:14 |
|
orwell96 joined #minetest |
| 08:21 |
|
sec0nd joined #minetest |
| 08:22 |
|
YuGiOhJCJ joined #minetest |
| 08:22 |
|
est31 joined #minetest |
| 08:22 |
|
lissobone joined #minetest |
| 08:22 |
|
fling joined #minetest |
| 08:22 |
lissobone |
My mod induces nausea. |
| 08:39 |
lissobone |
Potentionally dangerous memetic properties are yet to be discovered. [REDACTED]. |
| 08:48 |
|
Noisytoot joined #minetest |
| 08:52 |
|
fizi joined #minetest |
| 08:53 |
|
jadzia joined #minetest |
| 09:05 |
|
Noisytoot joined #minetest |
| 09:12 |
rubenwardy |
Abdou-31: is checked to see whether the command exists |
| 09:12 |
rubenwardy |
hmm I suppose that needs an "or not" |
| 09:13 |
rubenwardy |
is checked to see if the command exists |
| 09:17 |
|
jaca122 joined #minetest |
| 09:18 |
|
orwell96 joined #minetest |
| 09:26 |
|
fling joined #minetest |
| 09:28 |
|
Noisytoot joined #minetest |
| 09:44 |
|
wallabra joined #minetest |
| 10:03 |
|
calcul0n_ joined #minetest |
| 10:08 |
|
Noisytoot joined #minetest |
| 10:16 |
|
jaca122 joined #minetest |
| 10:28 |
|
jaca122 joined #minetest |
| 10:34 |
MTDiscord |
<Abdou-31> is checked to see if the command exists? |
| 10:34 |
MTDiscord |
<Abdou-31> Ok |
| 10:38 |
MTDiscord |
<Abdou-31> In doc/menu_lua_api.txt: core.show_path_select_dialog(formname, caption, is_file_select) ^ shows a path select dialog ... ^ -if dialog was canceled "_cancelled" |
| 10:40 |
MTDiscord |
<Abdou-31> "_cancelled" shouldn't be replaced by "_canceled" right? |
| 10:44 |
|
Noisytoot joined #minetest |
| 10:45 |
MTDiscord |
<Abdou-31> that sentence sounds off |
| 10:46 |
MTDiscord |
<Abdou-31> -if dialog was canceled "_cancelled" ^ will be added to fieldname value is set to formname itself |
| 10:46 |
MTDiscord |
<Abdou-31> I don't get the last part: is set to... |
| 10:49 |
|
definitelya joined #minetest |
| 11:09 |
MTDiscord |
<ROllerozxa> yeah don't fix typos in the API itself, it won't reflect in the actual source code and will lead to incorrect documentation |
| 11:19 |
|
Thelie joined #minetest |
| 11:28 |
MTDiscord |
<Abdou-31> Gotcha |
| 11:28 |
MTDiscord |
<Abdou-31> Thx |
| 11:29 |
MTDiscord |
<Abdou-31> But what about that last part that sounds off? |
| 11:29 |
MTDiscord |
<ROllerozxa> (the path select dialog is due for a nuking though but that's besides the point 8)) |
| 11:29 |
MTDiscord |
<ROllerozxa> what about it? |
| 11:29 |
MTDiscord |
<Abdou-31> Doesn't sound odd? |
| 11:31 |
MTDiscord |
<ROllerozxa> yeah does sound odd, might need a comma or something |
| 11:31 |
MTDiscord |
<ROllerozxa> btw while you're at it, menu_lua_api.txt is written in this weird not-markdown format, you could go ahead and reformat it while you're at it |
| 11:44 |
|
proller joined #minetest |
| 11:49 |
|
proller joined #minetest |
| 12:08 |
MTDiscord |
<Abdou-31> Might do it, but not now |
| 12:13 |
MTDiscord |
<Abdou-31> Why are there those ^ at the beginning of lines? |
| 12:16 |
|
lemonzest joined #minetest |
| 12:16 |
MTDiscord |
<ROllerozxa> some weird thing to signify the function a description is for |
| 12:17 |
MTDiscord |
<Abdou-31> hmm |
| 12:17 |
MTDiscord |
<Abdou-31> ok |
| 12:18 |
MTDiscord |
<Abdou-31> so I'm about to push a commit that fix typos in files inside /doc directory |
| 12:18 |
MTDiscord |
<Abdou-31> I've spell-checked all the files inside that directory |
| 12:19 |
MTDiscord |
<Abdou-31> is Fix typos in doc files a good commit message? |
| 12:19 |
MTDiscord |
<Abdou-31> don't think so |
| 12:19 |
MTDiscord |
<Abdou-31> I need a better one |
| 12:20 |
MTDiscord |
<Abdou-31> help |
| 12:21 |
MTDiscord |
<Abdou-31> btw, the README.md file is typo-free! |
| 12:21 |
MTDiscord |
<Abdou-31> 👏 |
| 12:26 |
MTDiscord |
<Warr1024> "Fix typos in doc files" looks good to me, especially if it's a whole bunch of typos everywhere and you can't be more specific. |
| 12:27 |
MTDiscord |
<Warr1024> "typos" always looks like it should be "typoes" but then the latter looks even MORE wrong 😄 |
| 12:27 |
MTDiscord |
<Abdou-31> X) |
| 12:27 |
|
definitelya joined #minetest |
| 12:27 |
MTDiscord |
<Abdou-31> oh! I almost forgot!! |
| 12:28 |
MTDiscord |
<Abdou-31> there are those centred/centered and behaviour/behavior changes that need to be done |
| 12:28 |
MTDiscord |
<Warr1024> Oh gross, en_GB... |
| 12:28 |
MTDiscord |
<Abdou-31> lol |
| 12:28 |
MTDiscord |
<Abdou-31> wait |
| 12:29 |
MTDiscord |
<Warr1024> Sorry I guess that should be "grouss" 🙄 |
| 12:29 |
MTDiscord |
<Abdou-31> not files everywhere, but only files inside the /doc folder |
| 12:29 |
MTDiscord |
<Abdou-31> I think Fix typos in files inside doc directory would be clearer |
| 12:29 |
MTDiscord |
<Abdou-31> because doc files is ambiguous |
| 12:31 |
MTDiscord |
<Warr1024> Houw dou en_GB users knouw where to sprinkle the extra u's? Or wheer re should be ervresed? It boggles my mind. |
| 12:31 |
MTDiscord |
<Abdou-31> T__T |
| 12:32 |
MTDiscord |
<ROllerozxa> *bouggles my midn |
| 12:37 |
MTDiscord |
<Abdou-31> in doc/fst_api.txt, there is: on_change = function(type,old_tab,new_tab) -- called on tab chang, does it need to be "change" or "changing"? |
| 12:39 |
MTDiscord |
<Warr1024> I'd say "called on tab change" |
| 12:39 |
MTDiscord |
<Abdou-31> thx a lot! |
| 12:52 |
MTDiscord |
<Abdou-31> https://github.com/minetest/minetest/pull/12882 |
| 12:52 |
MTDiscord |
<Abdou-31> My second baby |
| 13:00 |
|
Taoki joined #minetest |
| 13:10 |
MTDiscord |
<Abdou-31> Should I add [NO SQUASH]? |
| 13:11 |
|
Alnotz joined #minetest |
| 13:21 |
|
Noisytoot joined #minetest |
| 13:27 |
|
Noisytoot joined #minetest |
| 13:29 |
|
Fixer joined #minetest |
| 14:06 |
|
calcul0n joined #minetest |
| 14:11 |
|
orwell96_ joined #minetest |
| 14:20 |
|
Noisytoot joined #minetest |
| 14:24 |
MTDiscord |
<Abdou-31> Test |
| 14:32 |
|
Noisytoot joined #minetest |
| 14:40 |
|
srifqi joined #minetest |
| 14:42 |
srifqi |
Abdou-31: I do not think that is needed as those commits can be squashed as "fix typo" or something similar. |
| 14:42 |
|
Noisytoot joined #minetest |
| 14:45 |
MTDiscord |
<Warr1024> agreed, no-squash seems like it's mainly for larger, complex cases where arguably something should have been multiple PRs, but couldn't because of complex prerequisite relationships that would entail, or something. |
| 14:46 |
MTDiscord |
<Abdou-31> Ok |
| 14:47 |
MTDiscord |
<Abdou-31> A quick question: why the lines in lua_api.txt don't end with a trailing space? I'm reading that in markdown, that's how you make line breaks |
| 14:47 |
MTDiscord |
<Abdou-31> So if processed with a md processor, many seperate lines will show as one long line |
| 14:48 |
MTDiscord |
<Abdou-31> A trailing space here means two or more spaces |
| 14:48 |
MTDiscord |
<Abdou-31> Even one trailing whitespace won't make markdown create a line break |
| 14:49 |
MTDiscord |
<Warr1024> First of all, trailing spaces are 🤢 and the markdown spec doesn't have the authority to make them acceptable. |
| 14:50 |
MTDiscord |
<Warr1024> Secondly, we don't want to force line breaks in a markdown render, we want long lines to flow and wrap automatically. If we wanted specific line-breaks then we'd probably use preformatted blocks, or plaintext... |
| 14:50 |
srifqi |
I am also guessing that those line breaks are due to the line limit and not because new paragraph. All paragraphs inside that file is separated by an empty line IIRC. |
| 14:51 |
MTDiscord |
<Abdou-31> Does markdown support wrap word? |
| 14:51 |
MTDiscord |
<Abdou-31> or whatever that feature is called |
| 14:52 |
|
Noisytoot joined #minetest |
| 14:52 |
MTDiscord |
<Abdou-31> But they say something about using nothing to indicate new lines: >And at least a couple lightweight markup languages don’t require anything at the end of the line — just type return and they’ll create a line break. |
| 14:52 |
MTDiscord |
<Abdou-31> But it's the least compatible |
| 14:53 |
MTDiscord |
<Warr1024> Markdown is written IN plain text, so it's the author's responsibility to manually wrap the markdown source if they want to ensure that all editors consistently fit the text on the display for other doc editors. Markdown's default and correct behavior is to UNWRAP those lines, and then allow them to REWRAP to fit the actual display at render time. |
| 14:53 |
MTDiscord |
<Abdou-31> O.O |
| 14:53 |
MTDiscord |
<Abdou-31> I don't understand |
| 14:53 |
MTDiscord |
<Abdou-31> But that's fine |
| 14:53 |
MTDiscord |
<Abdou-31> I'm still reading about it |
| 14:54 |
MTDiscord |
<Warr1024> There is actually very little practical use for simple line breaks that aren't paragraph breaks (i.e. indicated by separating whitespace or an indentation) because those line breaks may disappear if the display width is close enough to the point where the line above would have wrapped naturally. |
| 14:54 |
MTDiscord |
<Abdou-31> I agree with you that trailing spaces are weird |
| 14:54 |
MTDiscord |
<Warr1024> You almost always either want paragraph breaks or no breaks. |
| 14:54 |
MTDiscord |
<Abdou-31> I see |
| 14:54 |
MTDiscord |
<Abdou-31> Wait |
| 14:55 |
MTDiscord |
<Warr1024> If I put a single line break in the source, that's because I wanted a line break in the source, NOT in the rendered output. If I put 2 line breaks in the source, then that's an indication that I want actual separation in the output. |
| 14:55 |
MTDiscord |
<Abdou-31> So you mean even if there is NO trailing space at the end of a line, a md processor will wrap the lines so they don't go outside the screen? |
| 14:57 |
MTDiscord |
<Warr1024> That's up to the viewer (e.g. it's often rendered to HTML and then viewed in a browser) but that's the standard behavior across all viewers I know |
| 14:57 |
MTDiscord |
<Abdou-31> I see |
| 14:58 |
MTDiscord |
<Abdou-31> So the lines on yhe viewer will be different from those line breaks on the source, that we see now? |
| 14:58 |
MTDiscord |
<Abdou-31> Weird |
| 15:00 |
srifqi |
Markdown is not WYSIWYG (like LibreOffice Writer/Office Word). What you see from the markdown file may be different than the rendered file. |
| 15:00 |
srifqi |
Have you tried to open lua_api.txt as a markdown file? You can see the effects of how it was written immediately. |
| 15:00 |
MTDiscord |
<Abdou-31> Oh You're right! I've never tried it |
| 15:00 |
MTDiscord |
<Abdou-31> Thx guys |
| 15:01 |
MTDiscord |
<Abdou-31> But as warr said, the "manual" line break thing is rarely used, we can just paragraphs or let the rendrer decide |
| 15:02 |
MTDiscord |
<srifqi> https://cdn.discordapp.com/attachments/749727888659447960/1032670095371149322/lua_api-preview.png |
| 15:02 |
srifqi |
That's an example between markdown file and its rendered view. |
| 15:03 |
MTDiscord |
<Abdou-31> Nice! Is it vscode? |
| 15:03 |
MTDiscord |
<Abdou-31> I didn't know it had a md processor |
| 15:04 |
srifqi |
Almost! I use VSCodium instead. |
| 15:04 |
srifqi |
You can tell the IDE to treat lua_api.txt as Markdown file (Ctrl+K then M). The preview button is at the top-right corner. |
| 15:04 |
srifqi |
(the magnifying glass) |
| 15:05 |
MTDiscord |
<Warr1024> Really, that rendered view is the MAIN reason why most people use MD in the first place (even though the code could be considered readable and theoretically I guess some of the markup in it does disambiguate stuff) |
| 15:05 |
srifqi |
It can be read as is or by using a Markdown processor. |
| 15:06 |
MTDiscord |
<Abdou-31> Nice! I'll try it later! |
| 15:06 |
MTDiscord |
<Abdou-31> What's vscodium? Vscode's brother? |
| 15:07 |
MTDiscord |
<GreenXenith> Vscode but demicrosofted |
| 15:07 |
srifqi |
According to its website, VSCodium = VSCode - telemetry. |
| 15:08 |
MTDiscord |
<Warr1024> Good markdown should always strive to be readable both with and without the processor/viewer. If "readable without" weren't one of the goals, then there are saner ways the text could be structured to be easier to process. |
| 15:22 |
MTDiscord |
<Abdou-31> 👍 |
| 15:23 |
MTDiscord |
<Abdou-31> But I've read that you can just turn off the telemetry option on the menu and that's it. |
| 15:23 |
MTDiscord |
<Abdou-31> I think i've read that on Wikipedia |
| 15:24 |
|
Noisytoot joined #minetest |
| 15:28 |
MTDiscord |
<ROllerozxa> the only thing that can turn off telemetry in a proprietary program is a strong firewall drop rule |
| 15:33 |
muurkha |
sometimes not even that |
| 15:35 |
|
jaca122 joined #minetest |
| 15:41 |
|
fluxionary joined #minetest |
| 15:56 |
MTDiscord |
<Abdou-31> Wow |
| 16:23 |
|
Rafi591 joined #minetest |
| 16:27 |
|
Rafi591 joined #minetest |
| 16:45 |
MTDiscord |
<Abdou-31> A question: In README.md there is: Table of Contents --------------------- 1. [Further Documentation](#further-documentation) ... Further documentation ---------------------------- In the rendering, the table of content's entry is a clickable link that takes directly to the h1 header. My question is: how are they linked? Shouldn't be a {#further-documentation} beside the header? |
| 16:47 |
MTDiscord |
<LandarVargan> [URL Text](url link) |
| 16:47 |
MTDiscord |
<LandarVargan> https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#relative-links |
| 16:50 |
rubenwardy |
Markdown automatically gives headers anchors |
| 16:55 |
|
garywhite joined #minetest |
| 16:55 |
|
garywhite joined #minetest |
| 17:00 |
|
est joined #minetest |
| 17:02 |
|
jaca122 joined #minetest |
| 17:08 |
muurkha |
no, Markdown doesn't |
| 17:08 |
muurkha |
but Github does |
| 17:08 |
rubenwardy |
markdown doesn't have a standard |
| 17:08 |
rubenwardy |
most markdown variants add header anchors (<h1 id>` |
| 17:09 |
rubenwardy |
*implementations |
| 17:10 |
muurkha |
markdown certainly does have a standard, even if not a standard implementation |
| 17:10 |
rubenwardy |
it has an info page but it's very vague on a lot of things |
| 17:10 |
rubenwardy |
there's no one standard markdown version |
| 17:10 |
muurkha |
and I don't think it's true that most markdown variants add header ids (which are not anchors; the <a> tag is an anchor) |
| 17:11 |
ecraven |
rubenwardy: even worse, there's *multiple* "standards" :P |
| 17:11 |
muurkha |
no, there's just one |
| 17:11 |
MTDiscord |
<Warr1024> I'm not sure if "being a mess" is exactly what one normally thinks of when they hear "standard", but I guess whatever works 🤷 |
| 17:12 |
muurkha |
fortunately Gruber was able to browbeat the Commonmark people out of calling their effort "Markdown" |
| 17:12 |
muurkha |
the standard is https://daringfireball.net/projects/markdown/, though it does leave a lot to be desired |
| 17:12 |
rubenwardy |
I'm well aware of how HTML and <a> works, I was simplifying |
| 17:14 |
muurkha |
using the wrong terminology doesn't simplify things |
| 17:14 |
muurkha |
https://babelmark.github.io/?text=Title%0A%3D%3D%3D%3D%3D%0A%0Ah21%0A-----%0A%0Ah22%0A----- shows 16 implementations generating headers without IDs |
| 17:14 |
muurkha |
9 implementations generating headers with IDs (including, importantly, pandoc) |
| 17:15 |
muurkha |
and one implementation generating headers with anchors (GFM) |
| 17:15 |
|
Talkless joined #minetest |
| 17:16 |
muurkha |
several implementations that claim to implement GFM omit the IDs |
| 17:17 |
|
fluxionary joined #minetest |
| 17:17 |
muurkha |
oh and gambas is totally broken on that example but it also doesn't generate IDs |
| 17:17 |
muurkha |
nine of the backends it tries to hit are broken now |
| 17:20 |
MTDiscord |
<Warr1024> Honestly we are probably going to have to pick which implementations we support at some point and disavow the rest; it's impractical to expect us to maintain documentation such that it works equally well across all renderers when the spec is so jank. |
| 17:21 |
MTDiscord |
<Warr1024> MT is supposed to be a net exporter of jank, we don't need no imports. |
| 17:24 |
|
___nick___ joined #minetest |
| 17:24 |
muurkha |
:) |
| 17:25 |
muurkha |
my own approach to this for Dercuano was to just use a single renderer for the Markdown, and then mangle the HTML output further with some custom Python |
| 17:26 |
muurkha |
but having now written books' worth of Markdown I look askance at renderers that claim to be "Markdown" but corrupt what I've written |
| 17:28 |
MTDiscord |
<Abdou-31> Thx guys for your explanation! |
| 17:29 |
|
calcul0n joined #minetest |
| 17:33 |
|
___nick___ joined #minetest |
| 17:34 |
|
sofar joined #minetest |
| 17:34 |
rubenwardy |
ContentDB uses python-markdown with a bunch of extensions to try and get close to GFM. There not being a strict standard is a pain for making md portable |
| 17:35 |
|
sofar joined #minetest |
| 17:36 |
|
___nick___ joined #minetest |
| 17:37 |
rubenwardy |
"fenced_code", "tables", "codehilite", "toc", a custom strikethrough plugin, and custom mention plugin |
| 17:37 |
|
sofar joined #minetest |
| 17:38 |
|
sofar joined #minetest |
| 18:12 |
|
Noisytoot joined #minetest |
| 18:36 |
sofar |
"Inside the box" server is back up. |
| 18:52 |
rubenwardy |
I'd like it if you could release the tutorial boxes at least, inside the box would be a really good singleplayer game. There's a fork that makes it work in singleplayer, but it's missing content |
| 18:56 |
muurkha |
there is a strict standard, though, and it doesn't have fenced code blocks, tables, code highlighting, or tables of contents in it |
| 18:57 |
muurkha |
for tables of contents I usually use http://canonical.org/~kragen/sw/addtoc.js |
| 18:57 |
|
sparky4 joined #minetest |
| 18:58 |
muurkha |
this has the disadvantage that it's JS though. also it adds IDs to headers |
| 18:59 |
muurkha |
the biggest problem I think is that Markdown was designed to *not* be extended, unlike HTML |
| 19:00 |
muurkha |
so when people add LaTeX, tables, etc., there's not a good way to do it in a fully backward-compatible way |
| 19:00 |
muurkha |
the fenced code blocks in GFM and CommonMark (which are not in Markdown, despite popular belief) do offer a useful extension mechanism |
| 19:01 |
muurkha |
used by things like PlantUML |
| 19:01 |
muurkha |
if you want a standardized Markdown-like language that supports the GFM features, maybe CommonMark is it? |
| 19:11 |
|
Noisytoot joined #minetest |
| 19:56 |
|
proller joined #minetest |
| 20:46 |
|
Verticen joined #minetest |
| 21:01 |
|
Noisytoot joined #minetest |
| 21:07 |
|
frostsnow joined #minetest |
| 21:29 |
|
est31 joined #minetest |
| 21:40 |
|
est31 joined #minetest |
| 21:55 |
|
est31 joined #minetest |
| 22:08 |
|
TomTom joined #minetest |
| 22:34 |
|
panwolfram joined #minetest |
| 22:41 |
|
wallabra_ joined #minetest |
| 22:45 |
|
HanSaul joined #minetest |
| 22:46 |
HanSaul |
hi i wonder if minetest downloaded cache is shared between all servers so once minetest_game is downloaded once it wont re-download for other servers? |
| 22:47 |
MTDiscord |
<Warr1024> I think it's supposed to work that way, yes. Media is identified by its exact content hash, so there should be no issues with servers with different versions. |
| 22:48 |
MTDiscord |
<Warr1024> That being said, minetest_game itself should be by far not the main cost of media downloading on most servers :-) |
| 23:16 |
HanSaul |
thanks wwar |
| 23:25 |
muurkha |
can you use that to fingerprint what other servers someone else has been playing on? |
| 23:30 |
|
Izaya left #minetest |
| 23:30 |
|
Izaya joined #minetest |
| 23:45 |
|
est31 joined #minetest |
| 23:51 |
|
Lesha_Vel joined #minetest |
| 23:52 |
|
Lesha_Vel joined #minetest |
| 23:55 |
fluxionary |
muurkha: ish. the server doesn't get a list of which hashes the client has seen before, but the server can query whether the client has seen a particular hash. you can get info that way, but it'd be hard to track an individual, let alone create a system to track thousands of them. |
| 23:58 |
|
fossdev2 joined #minetest |
| 23:58 |
fluxionary |
if someone doesn't clear their cache, it's easy (w/ a hacked server) to see whether a player is new to your server (or set of servers), or not. |
| 23:59 |
fluxionary |
https://en.wikipedia.org/wiki/Spy_pixel |
| 23:59 |
fluxionary |
https://en.wikipedia.org/wiki/Web_beacon |
