There are so many secrets spread across dot files. Is it possible to encrypt and store them in remote and de-encrypt when it’s pulled to local machines?
I use pass to manage such things separately.
This allows to script around hard-coded secrets:
Readit Newsshoeffner commented on Show HN: Lnk – Git-native dotfiles manager github.com/yarlson/lnk... · Posted by u/yar-kravtsov
Oh wow that looks really neat. I'm using Pandoc a lot anyways, so this might fit nicely into my workload. Thanks for sharing!
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
I could not find a product description. Stopped scrolling when I reached the related products and could not find a hyperlink in the sidebar. Is this just me stuck in old ways?
It's below the related and recommended products.
Does it fix incorrect Unicode chars? I've had a huge problem with that recently when for some reason Kbibtex insisted on converting {\"O} into Ö. I believe Jabref fixed it but I've made very bad experiences with Jabref in the past and would prefer not to use it.
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
}
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}
}
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.
I would consider ligatures a text rendering concept, which allows for but is distinct from the linguistic concept described by GP.
Edit: to further illustrate my point, in the ligatures I'm familiar with (including the ones in your link), the component characters exist standalone and can be used on their own, unlike GP's example.
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.
shoeffner commented on Learn RegEx step by step, from zero to advanced regexlearn.com/... · Posted by u/aykutkardas
Deleted Comment
How about keeping connection open from the webcam server or any host on the same LAN with a ssh reverse tunnel to a cheap cloud server?
For example when the webcam server is reachable on LAN at 192.168.1.2:1337 you can do
$ ssh -N -T -R 1338:192.168.1.2:1337 user@cloudserver.com
on a raspberry pi on the same LAN or locally in the webcam server and then you can access the webcam server from anywhere using cloudserver.com:1338
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!
People talk a lot of bad things about German ISPs, but I have IPv6 on my DSL connection since 2015 and on my phone since 2019 (maybe earlier).
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.