Community Purpose

This is a Makeup community for transgender, non-binary, and other gender-wobbled individuals. Post makeup that you're wearing today, or tips for beginners, or ask questions!

Rules & Guidelines

• this is a trans community. hate, bigotry, or anything anywhere near it will be deleted on sight and expect to be banned for breaking this rule.
• be respectful and polite. especially while learning it takes a lot of courage to post your progress pics, we're here to support people who are brave enough to do so.
• people appreciate product recommendations. its not required, but what to buy can be one of the most overwhelming things about learning makeup, and recommendations can help.

Suggested Post Tags:

• [MMT] or just title your post My Makeup Today: Show off what you're wearing today!
• [TIP]: for quick tips and smaller bits of information
• [TUTORIAL] or [GUIDE]: a longer post about a particular topic
• [PRODUCT]: recommend a specific product you l

This is an old YT reference I've come back to several times just for a basic reference to know how to prepare a few different cuts that my family randomly brings me.

This is framed loosely around some kind of mail service that specializes in shipping high quality cuts. I've never looked into it or used it myself; just a full disclosure. The person's perspective is that of a geek nerding out, not some marketing wank.

Typical USA grocery stores do not break down a side like this guy, but if you want to know the details about a cut and what you're really looking at from the details on the label, this guy breaks it all down well. In fact, I'm kinda bummed about being disabled and unable to regularly go shopping myself after seeing this video and mulling it over. This person's perspective clearly shows how your local butcher sees the meat and the potential knowledge they may have related to your culinary goals.

cross-posted from: https://slrpnk.net/post/847900

A few years ago, while we were cooking, my SO showed me a blog post about common spices and their substitutions. I thought it'd be cool to use that to make a chart we could hang on the wall.

It turned into a fun light research project, then a fun art project.

I started reading various blogs and realized that while many covered the same core spices, there were a lot of others that only one blog or another mentioned. So I started gathering them all up.

As I read about them on Wikipedia I'd stumble into their histories, and scope creep hit. I decided to add a column for interesting facts about each. (While gathering those, I was kind of struck at the disparity between them - some spices, have centuries of warfare, murder, and espionage wrapped around them, while others are so common or easy to grow that nobody seems to have stabbed anyone at all for it.)

I built it first as a spreadsheet in Google sheets while I was researching, pas

I think i may have a new food hack. If you're ever out shopping and don't know what or how to make for dinner you can goto the gravy aisle and the seasoning packets read like recipes. Just pick what you want to make, it'll tell you what you need and how to make it. The packet also tells you what is in it so you can learn what spices to put on things instead of buying seasoning packets forever.

cross-posted from: https://lemmy.ml/post/4593804

Originally discussed on Matrix.

---

TLDR; Ansible handlers are added to the global namespace.

---

Suppose you've got a role which defines a handler MyHandler:

 undefined

    
- name: MyHandler
  ...
  listen: "some-topic"

  

Each time you import/include your role, a new reference to MyHandler is added to the global namespace.

As a result, when you notify your handler via the topics it listens to (ie notify: "some-topic"), all the references to MyHandler will be executed by Ansible.

If that's not what you want, you should notify the handler by name (ie notify: MyHandler) in which case Ansible will stop searching for other references as soon as it finds the first occurrence of MyHandler. That

cross-posted from: https://lemmy.ml/post/4593804

Originally discussed on Matrix.

---

TLDR; Ansible handlers are added to the global namespace.

---

Suppose you've got a role which defines a handler MyHandler:

 undefined

    
- name: MyHandler
  ...
  listen: "some-topic"

  

Each time you import/include your role, a new reference to MyHandler is added to the global namespace.

As a result, when you notify your handler via the topics it listens to (ie notify: "some-topic"), all the references to MyHandler will be executed by Ansible.

If that's not what you want, you should notify the handler by name (ie notify: MyHandler) in which case Ansible will stop searching for other references as soon as it finds the first occurrence of MyHandler. That

Originally discussed on Matrix.

TLDR; Ansible handlers are added to the global namespace.

Suppose you've got a role which defines a handler MyHandler:

 undefined

    
- name: MyHandler
  ...
  listen: "some-topic"

  

Each time you import/include your role, a new reference to MyHandler is added to the global namespace.

As a result, when you notify your handler via the topics it listens to (ie notify: "some-topic"), all the references to MyHandler will be executed by Ansible.

If that's not what you want, you should notify the handler by name (ie notify: MyHandler) in which case Ansible will stop searching for other references as soon as it finds the first occurrence of MyHandler. That means MyHandler will be executed only once.

cross-posted from: https://lemmy.ml/post/4027414

TIL that I can use Perl's Benchmark module to time and compare the performance of different commands in an OS-agnostic way, ie as long as Perl is installed.

For example, to benchmark curl, wget and httpie you could simply run:

 Perl

    
$ perl -MBenchmark=:all \
     -E '$cmd_wget    = sub { system("wget  https://google.com/ > /dev/null 2>&1") };' \
     -E '$cmd_curl    = sub { system("curl  https://google.com/ > /dev/null 2>&1") };' \
     -E '$cmd_httpie  = sub { system("https https://google.com/ > /dev/null 2>&1") };' \
     -E '$timeresult  = timethese(15, { "wget" => $cmd_wget, "curl" => $cmd_curl, "httpie" => $cmd_httpie });' \
     -E 'cmpthese($timeresult)'

  

which on my old T530 produces:

 undefined

    
Benchmark: timing 15 iterations of curl, httpie, wget...

      curl:  2 wallclock secs ( 0.00 usr  0.00 sys +  0.42 cusr  0.11 csys =  0.53 CPU) @ 28.30/s (n=15)
    httpie:  8 w
  

TIL that I can use Perl's Benchmark module to time and compare the performance of different commands in an OS-agnostic way, ie as long as Perl is installed.

For example, to benchmark curl, wget and httpie you could simply run:

 Perl

    
$ perl -MBenchmark=:all \
     -E '$cmd_wget    = sub { system("wget  https://google.com > /dev/null 2>&1") };' \
     -E '$cmd_curl    = sub { system("curl  https://google.com > /dev/null 2>&1") };' \
     -E '$cmd_httpie  = sub { system("https https://google.com > /dev/null 2>&1") };' \
     -E '$timeresult  = timethese(15, { "wget" => $cmd_wget, "curl" => $cmd_curl, "httpie" => $cmd_httpie });' \
     -E 'cmpthese($timeresult)'

  

which on my old T530 produces:

 undefined

    
Benchmark: timing 15 iterations of curl, httpie, wget...

      curl:  2 wallclock secs ( 0.00 usr  0.00 sys +  0.42 cusr  0.11 csys =  0.53 CPU) @ 28.30/s (n=15)
    httpie:  8 wallclock secs ( 0.00 usr  0.01 sys +  4.63 cusr  0.79 csys =  5.43 CPU) @  2.76/s (n=15)
     
  

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/sffpc by /u/andrebrait on 2023-08-23 17:13:39.