diff --git a/notes.md b/notes.md
index 464fd8f..d95a607 100644
--- a/notes.md
+++ b/notes.md
@@ -23,8 +23,8 @@ Other places I've written about WebPerl:
Talks:
- YAPC::EU 2018 in Glasgow - [lightning talk](http://act.perlconference.org/tpc-2018-glasgow/talk/7475), [Video Link](https://youtu.be/KrGSg7uVZj0?t=29520)
-- *(planned)* German Perl Workshop 2019 - [talk](http://act.yapc.eu/gpw2019/talk/7616) (in German 🇩🇪)
-- *(hopefully)* YAPC::EU 2019 ([PerlCon](https://perlcon.eu/)) in Rīga
+- *(planned)* German Perl Workshop 2019 in Munich - [talk](http://act.yapc.eu/gpw2019/talk/7616) (slides in English, talk in German 🇩🇪)
+- *(planned)* YAPC::EU 2019 (PerlCon) in Rīga - [talk](https://perlcon.eu/talk/40)
[](https://doi.org/10.5281/zenodo.1400490)
diff --git a/using.md b/using.md
index b22900d..0275cee 100644
--- a/using.md
+++ b/using.md
@@ -271,8 +271,9 @@ It is important to keep apart the different ways to access files:
- A `` tag will cause `webperl.js`
to fetch `foo.pl` from the *web server*, not the virtual filesystem!
- *However*, that Perl script will *also* only see the virtual filesystem,
- not the web server, so it won't even be able to see "itself". You can still
- fetch things from the webserver using e.g. AJAX requests.
+ not the web server, so it won't even be able to see "itself" (`webperl.js`
+ may save files such as `/tmp/scripts.pl`, but that's *not* guaranteed).
+ You can still fetch things from the webserver using e.g. AJAX requests.
While a WebPerl instance is running, you can modify files in the virtual file system
as you might be used to from regular Perl. But the virtual filesystem is reloaded every
@@ -294,6 +295,7 @@ either. If you need to safely store files, it's best to store them on the user's
In particular, even though you might make heavy use of `/mnt/idb` when testing with the "mini IDE",
remember that this storage is *not* a way to distribute files to your users, and in fact, some
users' browsers may automatically regularly clear the `IndexedDB`, or have it disabled altogether.
+It also may not work at all in a "sandboxed" `iframe`.
For providing your application to your users, either use `