shoeffner

I use pass to manage such things separately. This allows to script around hard-coded secrets:

     export MY_TOKEN="$(pass token | head -n 1)"

Pandoc even poses codeblock execution as an exercise in their custom-filter documentation: https://pandoc.org/filters.html The python package panflute is also really nice if you don't want to play around with haskell or the AST JSON directly.

Fraunhofer Institute for Digital Medicine MEVIS | Public sector collective wage agreement | Full-Time | Bremen/Lübeck/Berlin, Germany | DevOps Engineer

At Fraunhofer MEVIS we pursue a patient-centered and clinical workflow-oriented approach to solving clinically relevant challenges in image- and data-based diagnosis and therapy (e.g., MRI analysis and surgery planning). To deliver excellent results, our research and development teams increasingly rely on our on-premises cluster and cloud infrastructure to compile, test, and deploy our software products, or train state of the art deep learning models.

As a DevOps Engineer, you will join a motivated team and improve the on-premise infrastructure. Our daily work involves the HashiCorp stack (Nomad, Vault, Terraform), Puppet, Ansible, OpenStack, and more. Additionally, we support our research personnel with CI/CD setups employing Jenkins and GitLab.

For more information, visit our job board or contact me directly:

https://jobs.fraunhofer.de/job/DevOps-Engineer-Digital-Medic... sebastian.hoeffner@mevis.fraunhofer.de

It's below the related and recommended products.

What do you mean? I tried placing Ö and {\"O} in the author's name of the example and tidied it:

    Click Tidy to clean up the entries below      
    @Book{sweig42,
      Author =  { Stef{\"O}{n} SwÖig },
      title =  { The impossible book },
      publisher =  { Dead Poet Society},
      year =  1942,
      month =        mar
    }

This is the output:

    Click Tidy to clean up the entries below
    @book{sweig42,
     title        = {The impossible book},
     author       = {Stef{\"O}{n} SwÖig},
     year         = 1942,
     month        = mar,
     publisher    = {Dead Poet Society}
    }

And \"O should be Ö, so I guess I do not really understand what is "incorrect" in your use case.

I know that the Zoteroplugin BetterBibTeX converts Ö to {\"O} when exporting as BibTeX, but keeps it as Ö when exporting as BibLaTeX – maybe Kbibtex has similar options?

edit: It actually "fixes" Ö to {\"O} if you tick "Escape special characters" or supply the command line argument `--escape`, which should be the default according to GitHub.

In the example "Straße", the ß is, in fact, derived from an ancient ligature for sz. Old German fonts often had s as ſ, and z as ʒ. This ſʒ eventually became ß.

We (completely?) lost ſ and ʒ over the years, but ß was here to stay. Its usage changed heavily over time (replacing ss instead of sz), I think for the last time in the 90s (https://en.wikipedia.org/wiki/German_orthography_reform_of_1...), where we changed when to use ß and when ss.

So while we do replace ß with ss if we uppercase or have no ß available on the keyboard, no one would ever replace ß by sz (or even ſʒ) today, unless for artistic or traditional reasons.

Many people uppercase ß with lowercase ß or, for various reasons, an uppercase B. I have yet to see a real world example of an uppercase ẞ, it does not seem to exist outside of the internet. For example, "Straße" could be seen capitalized in the wild as STRAßE, STRASSE, STRABE, with Unicode it could also be STRAẞE. It would not be capitalized with sz (STRASZE) or even ſʒ (STRAſƷE – there is no uppercase ſ) – at least not in Germany. In Austria, sz seeems to be an option.

So, for most ligatures I would agree with you, but specifically ß is one of those ligatures I would call an outlier, at least in Germany.

P.S.: Maybe the ampersand (&), which is derived from ligatures of the latin "et", has sometimes similar problems, alhough on a different level, since it replaces a whole word. However, I have seen it being used as part of "etc.", as in "&c." (https://en.wiktionary.org/wiki/%26c.), so your point might also hold.

P.P.S.: I wonder why the uppercasing in the original post did not use ẞ, but I guess it is because of the rules in https://www.unicode.org/Public/UCD/latest/ucd/SpecialCasing.... (link taken from the feed). The wikipedia entry says we adopted the capital ẞ in 2017 (but it is part of unicode since 2008). It also states that the replacement SZ should be used if the meaning would otherwise get lost (e.g. "in Maßen" vs. "in Massen" would both be "IN MASSEN" but mean either "in moderate amounts" or "in masses", forcing the first to be capitalized as MASZEN). I doubt any programming language or library handles this. I would not have even handled it myself in a manual setting, as it is such an extreme edge case. And I when I read it, I would stumble over it.

You need to press enter/return to advance.

I considered such options before but if I remember correctly, the webhost does not allow SSH. However, I haven't checked for some time and I will definitely look into this, thank you!

I also remember having IPv6 in Germany for years now, but it came with lots of problems: routers cannot forward things properly, thus self-hosting at home becomes tricky, or playing games with friends without dedicated servers (yes, they still exist, no, not all support IPv6). It gets even worse with "DS-Lite", where multiple customers share the same external IPv4 address, to enable support for all the webservices not supporting IPv6 yet.

All in all, I had so many troubles with setting up anything behind IPv6 or DS-lite, that I asked my ISP to give me an additional IPv4 address, so that I don't have troubles. While they usually provide bad service, this came for free -- but other ISPs, for example my parents' ISP, want you to pay 50 or more euros per month for an "enterprise contract" to get a dedicated IPv4. I still haven't found a way for my dad to setup his old webcam server at home such that others can reach it from the outside world, and I tried every couple months over the last 6 years or so.

In [1], pages 10 and 11 are the actual directive, the rest is the reasoning. And, although I don't know the previous directives and regulations, it reads as if this is essentially an extension of an exception to the ePrivacy directive for another five years.

Birgit Sippel says in her statement to the president of the parliament [2]: > Dieses Gesetz ist eine Übergangslösung für drei Jahre. Die Kommission hatte versprochen, noch vor der Sommerpause einen neuen, dauerhaften Rahmen für die Aufdeckung von Kindesmissbrauch vorzuschlagen. Jetzt dauert es noch bis September oder Oktober. Dafür erwarte ich einen deutlich verbesserten Vorschlag. Die langfristige Lösung muss sich mindestens an den Datenschutzgarantien der temporären Lösung orientieren. Sie muss zwingend Lösungen für das gezieltere Scannen privater Kommunikation finden, sonst wird sie vor nationalen und europäischen Gerichten kaum Bestand haben.

Translated (by myself): > This law is a short term solution for three years. The commission promised a permanent solution to combat child abuse before the summer break. Now, this will take until September or October. Thus, I await a much better proposal. The long term solution must have at least the same guarantees for data protection as the short term solution. It [the long term solution] must have solutions for purposeful/targeted ("gezielt") scanning of private communication, otherwise it will not hold up in front of national or European courts.

So maybe things do not change that much right now.

But back to [1], I am especially curious about article 3(e): > the provider annually publishes a report on its related processing, including on the type and volumes of data processed, number of cases identified, measures applied to select and improve key indicators, numbers and ratios of errors (false positives) of the different technologies deployed, measures applied to limit the error rate and the error rate achieved, the retention policy and the data protection safeguards applied

Do you know if and where such statistics are published? (today?)

[2]: https://www.europarl.europa.eu/doceo/document/CRE-9-2021-07-...

This answer how facebook does (did?) it and why is also very interesting: https://stackoverflow.com/a/21693931

https://docs.python.org/3/library/cgi.html All your prints are essentially sent as response with CGI, but I think for Python WSGI is the standard you should use, and you can e.g. use jinja to render HTML with templates where you can use variables, certain functions, etc. Is that what you are looking for?

iPad, iPod, iPhone, MBP, iMac, AppleWatch, ... oh, that's already six devices tied to the same account.

I think the idea is that you don't tie all your friends' devices to your account to share apps etc., but I am just guessing.

Maybe it's related to the https://en.wikipedia.org/wiki/Blue_field_entoptic_phenomenon .

The original article links to a different PDF, namely https://files.orf.at/vietnam2/files/fm4/202045/783284_fh_st1..., which also contains a number of additions and deletions.

If I got it correctly, they do not have do-while, it was only shown as an example operation. Instead, they only use "for each", i.e., bounded loops directly on the data structures list/array.

Changing the language, yes. But translating at a glimpse will get lost this way.

The quote is not about logs making you unsafe. The quote is about ssh login and connection attempts on port 22 which clutter your log files.

Assume you move ssh to another port, say 23. In that case, anyone trying to connect to port 22 would find a closed port and the connection would fail, on a layer before login attempts get logged.

This is just the valve, as the ventilators are much more complex.

There has been some discussion on 3D printing medical ventilators on the local hackerspace mailing list. One of the participants used to work at a company which builds those and made similar points:

There are different systems, one are the C/VPAP which are only for ventilation during sleep, avoiding a closure of the pharynx by increasing the pressure to a certain maximum value. Some of those have parameters also taking care of the patient's breathing pressure etc. but in general can only help for "better sleep" – if they fail, then you have a bad sleep but won't die.

The systems they use in hospitals are the complex machines you describe: they have battery power, measure the flow of breath, have alarms etc. Even here they distinguish between "supported breathing" and "keeping alive", i.e. in the former case the machine helps you to breathe while the second takes care of breathing for you.

In Italy, a doctor asked for a replacement part of their ventilators which was then 3D printed – the valves mentioned in the article. This seems to have led to a surge in people now trying to build, design, etc. ventilators which can essentially be build anywhere, to combat supply chain shortages.

Again: You are right, medical ventilators are a tricky business and difficult to build. But in this case, the ventilators seem to be there, they just need the valves, which can be printed. And they put up a huge disclaimer that patients need to agree to use unapproved devices.

A German article covering this is [1].

[1] https://www.deutschlandfunk.de/kreative-loesungen-in-zeiten-...

You can try things such as:

- https://github.com/joshua-wu/deepfakes_faceswap

- https://github.com/Oldpan/Faceswap-Deepfake-Pytorch

You might have to run on a frame by frame basis, e.g. using `ffmpeg -i file.mpg $filename%03d.bmp` [1] and stitching the results back together [2]. I haven't tried it, though, and there might be better alternatives.

[1] https://stackoverflow.com/a/10962408 [2] https://hamelot.io/visualization/using-ffmpeg-to-convert-a-s...

https://github.com/sourcegraph/sourcegraph/blob/master/LICEN... says: "LICENSE.apache (Apache License) applies to all files in this repository, except for those in the enterprise/ and web/src/enterprise/ directories, which are covered by LICENSE.enterprise."

Thus, Apache 2.0 and some custom license requiring you to accept the terms, have a correct number of seats, and does not allow you to "copy, merge, publish, distribute, sublicense, and/or sell the Software."

I am not sure what all of this means, though. Better check out the licenses yourself :)

Nice, thank you for the upload and thank you for clarifying that small objects are not labeled, that explains it. I was suprised because other images do contain rather small labels for traffic lights or even cars, but I guess it's always in the eyes of the person who labels the data.

I think you did an amazing amount of work and huge improvements over the original, have you considered contributing the changes back upstream?

While I am happy about their efforts, it's interesting that in the bottom left image of their example I can clearly see another unlabeled car in the lower left half (standing at the sidewalk of the street). Also, I am not sure, but it seems like there's a cyclist on the sidewalk, visible between the stroller and the car (the wheel and hands are more clearly visible). The google image marks a car and a few pedestrians, but completely misses the traffic lights at the junction.

So I guess even their fixed dataset still misses many labels, if already their showcases miss some.

Some people tried way more sophisticated hoaxes: https://www.theatlantic.com/technology/archive/2012/05/how-t...

Yes, it was him, someone added an additional "Wilhelm" [0] and it was copied by many newspapers [1]. The Bild wrote (translation mine): "Do we have to remember this name?" [2], and some anonymous guest author on the blog claims to be responsible [2]. In 2016 the name was edited in for about 2 minutes [3], referencing a source from 2012. However, I do not recall it being a big issue to remove that additional name again – but it was more than 10 years ago. It did, however, draw some criticism to German journalism.

[0]: https://de.wikipedia.org/w/index.php?title=Karl-Theodor_Frei... [1]: https://bildblog.de/5731/wilhelm-ii/ lists a few of those newspapers [2]: https://bildblog.de/5704/wie-ich-freiherr-von-guttenberg-zu-... [3]: https://de.wikipedia.org/w/index.php?title=Karl-Theodor_zu_G...

And to remove the quarantine attribute when you are sure you want to run something:

    xattr -d com.apple.quarantine FILE

Regarding 2: I saw a talk yesterday by Alex Hernández-García in which he showed that dropout and weight decay can be replaced with data augmentation in many cases. The relevant paper by him and König is https://arxiv.org/abs/1806.03852v2

edit: changed to /abs/ instead of /pdf/ link

What I usually do is:

    xattr -d com.apple.quarantine FILE

It removes the extended attribute from the given file.