reply to u/stjeromeslibido at https://www.reddit.com/r/Zettelkasten/comments/10qw4l5/are_there_symbols_for_supported_by_or/

In addition to the other excellent suggestions, I don't think you'll find anything specific that that was used historically for these, but there are certainly lots of old annotation symbols you might be able to co-opt for your personal use.

Evina Steinova has a great free cheat sheet list of annotation symbols: The Most Common Annotation Symbols in Early Medieval Western Manuscripts (a cheat sheet).

More of this rabbit hole:

• Steinová, Evina. Notam Superponere Studui: The Use of Annotation Symbols in the Early Middle Ages. Brepols, 2019.
• Cappelli, Adriano. The Elements of Abbreviation in Medieval Latin Paleography. University of Kansas Libr., 1984.
• Coulson, Frank, and Robert Babcock. The Oxford Handbook of Latin Palaeography. Oxford University Press, 2020.
• Lindsay, W. M. Notae Latinae. Cambridge University Press, 2013. https://archive.org/download/notaelatinaeacco00lindrich/notaelatinaeacco00lindrich.pdf.
• Bains, Doris. A Supplement to Notae Latinae (Abbreviations in Latin Mss. of 850 to 1050 A.D.). Cambridge [England] University Press, 1936. http://archive.org/details/supplementtonota0000bain.

(Nota bene: most of my brief research here only extends to Western traditions, primarily in Latin and Greek. Obviously other languages and eras will have potential ideas as well.)

Tironian shorthand may have something you could repurpose as well: https://en.wikipedia.org/wiki/Tironian_notes

Some may find the auxiliary signs of the Universal Decimal Classification useful for some of these sorts of notations for conjoining ideas.

Given the past history of these sorts of symbols and their uses, perhaps it might be useful for us all to aggregate a list of common ones we all use as a means of re-standardizing some of them in modern contexts? Which ones does everyone use?

Here are some I commonly use:

Often for quotations, citations, and provenance of ideas, I'll use Maria Popova and Tina Roth Eisenberg's Curator's Code:

• ᔥ for "via" to denote a direct quotation/source— something found elsewhere and written with little or no modification or elaboration (reformulation notes)
• ↬ for "hat tip" to stand for indirect discovery — something for which you got the idea at a source, but modified or elaborated on significantly (inspiration by a source, but which needn't be cited)

Occasionally I'll use a few nanoformats, from the microblogging space, particularly

• L: to indicate location

For mathematical proofs, in addition to their usual meanings, I'll use two symbols to separate biconditionals (necessary/sufficient conditions)

• (⇒) as a heading for the "if" portion of the proof
• (⇐) for the "only if" portion

Some historians may write 19c to indicate 19th Century, often I'll abbreviate using Roman numerals instead, so "XIX".

Occasionally, I'll also throw drolleries or other symbols into my margins to indicate idiosyncratic things that may only mean something specifically to me. This follows in the medieval traditions of the ars memoria, some of which are suggested in Cornwell, Hilarie, and James Cornwell. Saints, Signs, and Symbols: The Symbolic Language of Christian Art 3rd Edition. Church Publishing, Inc., 2009. The modern day equivalent of this might be the use of emoji with slang meanings or 1337 (leet) speak.

Tip

If you see something, say something is a lot over-the-top for a Hollywood rag.

Ning, C., Wu, H., & Liu, Y. (2021). Deliberation in health-related headlines. PsyArXiv. https://doi.org/10.31234/osf.io/e5bn7

Seems like this would be a very common need: once you switch to a custom failure track, you want it to stay on that track until the end!!!

The problem is that in a Railway, everything automatically has 2 outputs. But we really only need one (which is exactly what Path gives us). And you end up fighting the defaults when there are the automatic 2 outputs, because you have to remember to explicitly/verbosely redirect all of those outputs or they may end up going somewhere you don't want them to go.

The default behavior of everything going to the next defined step is not helpful for doing that, and in fact is quite frustrating because you don't want unrelated steps to accidentally end up on one of the tasks in your custom failure track.

And you can't use fail for custom-track steps becase that breaks magnetic_to for some reason.

I was finding myself very in need of something like this, and was about to write my own DSL, but then I discovered this. I still think it needs a better DSL than this, but at least they provided a way to do this. Much needed.

For this example, I might write something like this:

step :decide_type, Output(Activity::Left, :credit_card) => Track(:with_credit_card)

# Create the track, which would automatically create an implicit End with the same id.
Track(:with_credit_card) do
    step :authorize
    step :charge
end

I guess that's not much different than theirs. Main improvement is it avoids ugly need to specify end_id/end_task.

But that wouldn't actually be enough either in this example, because you would actually want to have a failure track there and a path doesn't have one ... so it sounds like Subprocess and a new self-contained ProcessCreditCard Railway would be the best solution for this particular example... Subprocess is the ultimate in flexibility and gives us all the flexibility we need)

But what if you had a path that you needed to direct to from 2 different tasks' outputs?

Example: I came up with this, but it takes a lot of effort to keep my custom path/track hidden/"isolated" and prevent other tasks from automatically/implicitly going into those steps:

class Example::ValidationErrorTrack < Trailblazer::Activity::Railway
  step :validate_model, Output(:failure) => Track(:validation_error)
  step :save,           Output(:failure) => Track(:validation_error)

  # Can't use fail here or the magnetic_to won't work and  Track(:validation_error) won't work
  step :log_validation_error, magnetic_to: :validation_error,
    Output(:success) => End(:validation_error), 
    Output(:failure) => End(:validation_error) 
end

puts Trailblazer::Developer.render o
Reloading...

#<Start/:default>
 {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
 {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
 {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<End/:success>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Left} => #<End/:validation_error>
 {Trailblazer::Activity::Right} => #<End/:validation_error>
#<End/:success>

#<End/:validation_error>

#<End/:failure>

Now attempt to do it with Path... Does the Path() have an ID we can reference? Or maybe we just keep a reference to the object and use it directly in 2 different places?

class Example::ValidationErrorTrack::VPathHelper1 < Trailblazer::Activity::Railway
   validation_error_path = Path(end_id: "End.validation_error", end_task: End(:validation_error)) do
    step :log_validation_error
  end
  step :validate_model, Output(:failure) => validation_error_path
  step :save,           Output(:failure) => validation_error_path
end

o=Example::ValidationErrorTrack::VPathHelper1; puts Trailblazer::Developer.render o
Reloading...

#<Start/:default>
 {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
 {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<End/:validation_error>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
 {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<End/:success>
#<End/:success>

#<End/:validation_error>

#<End/:failure>

It's just too bad that:

• there's not a Railway helper in case you want multiple outputs, though we could probably create one pretty easily using Path as our template
• we can't "inline" a separate Railway acitivity (Subprocess "nests" it rather than "inlines")

That's what I keep telling people. Glad to see I'm not the only one...

Konstantinos, A. (2021). Tips on countering conspiracy theories and misinformaton. CommsFlyer.

You should start with CIFAR-10 and MNIST only to get some initial results, but to see if those ideas hold up more broadly, test them on more realistic datasets like ImageWoof, ImageNet.

ScD, N. N. A. (2020, June 11). A Guide to Understanding Pandemic Predictions. Medium. https://elemental.medium.com/a-guide-to-understanding-pandemic-predictions-8ae3439b8224

Trickt to quickly find discount codes on a website:

site:curology.com ("coupon" | "referral code" | "affiliate code" | "discount code" | "VIP")

Trisha Greenhalgh 😷 #BlackLivesMatter on Twitter: “Mask steaming up your glasses? Fix here. https://t.co/Yn3wf7remH” / Twitter. (n.d.). Twitter. Retrieved July 7, 2020, from https://twitter.com/trishgreenhalgh/status/1279413188367454209

Petrie-Flom Center on Twitter: “Here are @CaulfieldTim’s top tips for effective debunking! #COVID19andData https://t.co/AjkoTZSPjW” / Twitter. (n.d.). Twitter. Retrieved June 3, 2020, from https://twitter.com/PetrieFlom/status/1267856811962466304

😁👍

You can use emojis in osX by holding down command+control+spacebar to open up the emoji keyboard.