for - sensory substitution - after 6 month - signal on skin - sounds like there is an external source of sound - same thing happens with our ear - David Eagleman

for - quote - first thing to understand is that humans are relational beings - John Churchill - adjacency - humans are relational beings John Churchill - Deep Humanity - individual / collective gestalt - self / other gestalt

for - interesting perspective - Karl Marx - He wasn't principally interested in equality - book - Capitalism: the word and the thing - perspectival knowledge of - Michael Sonenscher - misunderstanding - modern capitalists - misunderstand Karl Marx's work - Michael Sonenscher - Karl Marx and Capitalism - Maximizing each individual's freedom while not trampling on the same aspiration of other individuals within a society

Interesting perspective - Karl Marx wasn't principally interested in equality - Sonenscher offers an interesting interpretation and perspectival knowledge of Karl Marx's motivation in his principal work paraphrase - Marx's thought centered on is interest in individuality and the degree to which in certain respects being somebody who is free and able to make choices about his or her lives and future activities is going to depend on each person's: - qualities - capabilities - capacities - preoccupations - values, etc - For Marx, freedom is in the final analysis something to do with something - particular - specific and - individual w - What matters to me may not matter entirely in the same sort of way to you because ultimately - in an ideal State of Affairs, my kinds of concerns and your kinds of concerns will be simply specific to you and to me respectively - For Marx, the problems begin as is also the case with Rosseau - when these kinds of absolute qualities are displaced by - relative qualities that apply equally to us both - For Marx, things like - markets - prices - commodities and - things that connect people - are the hallmarks of equality because they put people on the same kind of footing prices and productivity - Whereas the things that REALLY SHOULD COUNT are - the things that separate and distinguish people that make each individual fully and and entirely him or herself and - the idea for Marx is that capitalism - which is not a term that Marx used, - puts people on a kind of spurious footing of equality - Getting beyond capitalism means getting beyond equality to a state of effect in which - difference , - particularity, - individuality and - uniqueness - in a certain kind of sense will prevail

comment - This perspective is quite enlightening on Marx's motivations on this part of his work and is likely misconstrued by those mainstream "capitalists" who vilify his work without critical analysis - Of course freedom - within a social context - is never an absolute term. - It is not possible to live in a society in which everyone is able to actualize their full imaginations, something pointed out in the work of two other famous thought leaders of modern history: - Thomas Hobbes observed in his famous work, Leviathan, and - Sigmund Freud also made a primary subject of his ID, Ego and Superego framework. - Total freedom would lead - first to anarchy and then - the emergence within that anarchy of those which possess the most charisma, influence, self-seeking manipulative skills and brutality - surfacing rule by authority - Historically, as democracy attempts to surface from a history of authoritarian, patriarchal governance, - democracy is far from ubiquitous and authoritarian governance is still alive and well in many parts of the world - The battle between - authoritarian governments among themselves and - authoritarian and democratic governments - results in war, violence and trauma that creates the breeding ground for the next generation of authoritarian leaders - Marx's main intent seems to be to enable the individual existing within a society to live the fullest life possible, - by way of enabling and maximizing their unique expression, - while not constraining the same aspiration in other individuals who belong to the same society

for - capitalism - etymology - book Captialism: The Word and the Thing - Michael Sonenscher - from - Princeton University Press

Summary - Michael Sonenscher discusses the modern evolution of the word "capitalism". Adding the suffix "ism" to a word implies a compound term. - Capitalism is a complex, compound concept whose connotations from the use in 18th and 19th century France and England is quite different from today's. - How meaning evolved can give us insight into our use of it today.

from - Princeton University Press - book - Capitalism: the word and the thing - to - https://hyp.is/kVaURoxREe-x7MtVDX2t3Q/press.princeton.edu/ideas/capitalism-the-word-and-the-thing

for - capitalism - etymology - modern - book Capitalism: The Word and the Thing - Michael Sonenscher - from - Discussion of "spiritual capitalism" on Kansas Missouri Fair Shares Commons chat thread - to - youtube - New Books Network - interniew - Captialism: The word and the thing - Michael Sonenscher

Summary - Michael Sonenscher discusses the modern evolution of the word "capitalism". Adding the suffix "ism" to a word implies a compound term. - Capitalism is a complex, compound concept whose connotations from the use in 18th and 19th century France and England is quite different from today's. - How meaning evolved can give us insight into our use of it today.

to - youtube - New Books Network - interniew - Captialism: The word and the thing - Michael Sonenscher - https://hyp.is/ftWWfoxQEe-FkUuIeSoZCA/www.youtube.com/watch?v=ZpNaxyPpOf0

for - sustainable building - cement mortar is the worst thing for re-using bricks

Failure to assemble an appropriate IEP team:

for - quote - most important thing to practice as an artist - Rick Ruben

quote - single most important thing to practice as a musician - Rick Ruben - (see below)

• Understanding how you feel in the face of other voices,
  • without second guessing yourself,
• is probably the single most important thing to practice as an artist.

for - chronic disease - usually chronic is not a good sign - too much of a good thing turns out to be bad - it means too much of something, like inflammation will cause harm - when inflammation knob is stuck on high, it becomes a problem

metaphor - inflammation and forest fire - If you are camping in the forest, a small fire keeps you warm and you can cook - Inflammation is like that small fire going out of control and burning the whole forest down

// Not recommended: log into the application like a user // by typing into the form and clicking Submit // While this works, it is slow and exercises the login form // and NOT the feature you are trying to test.

only partial match: the most important thing is the information (more than presentation/formatting)

https://www.investopedia.com/terms/t/tanstaafl.asp

<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>John Mount</span> in Good Stationery as a Tool of Thought | MZLabs (<time class='dt-published'>11/30/2022 13:11:31</time>)</cite></small>

Read 2022-12-31

container images: whether to use full init process: implied here: don't need to if only using for single process (which doesn't fork, etc.)

I took along my son, who had never had any fresh water up his nose and who had seen lily pads only from train windows. On the journey over to the lake I began to wonder what it would be like. I wondered how time would have marred this unique, this holy spot--the coves and streams, the hills that the sun set behind, the camps and the paths behind the camps. I was sure that the tarred road would have found it out and I wondered in what other ways it would be desolated. It is strange how much you can remember about places like that once you allow your mind to return into the grooves which lead back. You remember one thing, and that suddenly reminds you of another thing. I guess I remembered clearest of all the early mornings, when the lake was cool and motionless, remembered how the bedroom smelled of the lumber it was made of and of the wet woods whose scent entered through the screen. The partitions in the camp were thin and did not extend clear to the top of the rooms, and as I was always the first up I would dress softly so as not to wake the others, and sneak out into the sweet outdoors and start out in the canoe, keeping close along the shore in the long shadows of the pines. I remembered being very careful never to rub my paddle against the gunwale for fear of disturbing the stillness of the cathedral.

https://slate.com/culture/2022/06/book-titles-eleanor-oliphant-women-fiction.html

This article has a nice number of examples of the naming convention: "Protagonist Does a Thing"

I am a bit shocked to see Hypothes.is indicates that there are 31 (private) annotations on this particular page. What is going on here?!

in particular ?

support or supporting

substantial

hanging sentence

a researcher or researchers

The Sunday Thing

The love of money is the root of all evil

This week, Michael Gungor asked us to discuss money in our breakout groups.

Money is power

We outsource our power and authority to those who claim to have greater access to capital, because we underestimate and undervalue our own social influence, economic capacity, and political agency. The entreprecariat is designed for learned helplessness (social: individualism), trained incapacities (economic: specialization), and bureaucratic intransigence (political: authoritarianism). https://hypothes.is/a/667dOC0bEeyV6Itx3ySxmw

Indigenous cultures in Canada were disempowered by outlawing the cultural practice of generosity (potlatch) and replacing the practice with centralized power over the medium of exchange: money. Money is a mechanism of disempowerment.

Money is a shared story we tell ourselves about what has value. https://www.npr.org/transcripts/795246685

We translated “ekklesia” as church. It is the deliberative body of the experiment in democracy in Athens, Greece. The people who are figuring out how to live together in the commons. The work of the people. The Liturgists.

The Story of Money

In this hour, On the Media looks at the story of money, from its uncertain origins to its digital reinvention in the form of cryptocurrency.

On the Media: Full Faith & Credit

Squid Game

People were also discussing Squid Game.

Squid Game was on my mind today before the call. “The reality of the history of Canada’s mining industry makes #SquidGame look like child’s play.” https://twitter.com/bauhouse/status/1449726452098682881?s=20

The truth is that all of the gold that was mined out of the Klondike was under Indigenous land. There was no treaty with any of Indigenous peoples in the Yukon.

Commons: Mining

I was at the bookstore yesterday and ran into two new useful resources that looked interesting in this space.

Specific to birdsong, there was

200 Bird Songs from Around the World by Les Beletsky (Becker & Mayer, 2020, ISBN: ‎ 978-0760368831)

Read about and listen to birds from six continents. A beautiful painting illustrates each selection along with concise details about the bird's behavior, environment, and vocalizations. On the built-in digital audio player, hear each bird as it sings or calls in nature with audio of the birds provided by the Macaulay Library at the Cornell Lab of Ornithology.

This could be useful in using the book itself as a memory palace in addition to the fact that the bird calls are built directly into the book for immediate playback while reading/memorizing. There are a few other related books with built in sound in this series as well.

The other broader idea was that of

"A bird a day"

I saw the book A Bird A Day by Dominic Couzens (Batsford, 2021, ISBN: 978-1849945868) to help guide one towards learning about (or in our context maybe memorizing) a bird a day. It had names, photos, and other useful information which one might use to structure a palace to work at in small chunks. I know there are also many other related calendars which might also help one do something like this to build up a daily practice of memorizing data into a palace/journey/songline.

The broader "Thing-a-day" calendar category might also be useful for other topics one might want to memorize as well as to have a structure set up for encouraging spaced repetition.

git is neutral/unbiased/agnostic about default branch name by design

And that is a good thing

So you think it's better to make people post a new "answer" (as if it were actually a distinct, unrelated answer) instead of just letting them comment on the answer that they actually want to comment on? Yuck.

That would probably be a better name because you're actually testing/verifying that there hasn't been any regression.

You're testing for the absence of regression. But I guess testing for one also tests for the other, so it probably doesn't matter. (If something is not true you know it is false, etc.)

.

Il dit que la sorcellerie n'existe pas.

nee -- pr. circ. so, demonstratively distant. Cf. nale.

na -- 1. pr. circ. so, defined distant. How? 'Or' What. 2. function indicator. As.

ndëmm gi -- symbolic anthropophagia. 🧙

am+ul (am) v. -- to exist, to have.

And now that it's deprecated (presumably due to no longer needing these polyfills), not only do the polyfills go away (no longer maintained), but also these unrelated "extras" that some of us may have been depending on are now going away with no replacement ...

If those were in a separate package, then there would have been some chance of the "extras" package being updated to work without the base webshims polyfills.

In particular, I was using $.webshims.addCustomValidityRule which adds something that you can't do in plain HTML5 (that I can tell), so it isn't a polyfill...

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")

I don't think we would/should really want to make this the "success" (Right) path and :credit_card be the "failure" (Left) track.

Maybe it's okay to repurpose Left and Right for something other than failure/success ... but only if we can actually change the default semantic of those signals/outputs. Is that possible? Maybe there's a way to override or delete the default outputs?

Wow, that's a lot of different ways.

The inline_form way in particular seems interesting to me, though it's worth noting that that method is just an example, not actually part of this project's code, so it's not really a first-class option like the other options.

Seems like these helper functions could be just as easily used in ActiveRecord models. Therefore, they should be in a separate gem, or at least module, that can be used in both these objects and ActiveRecord objects.

the crux of the problem is: trade-offs

This could be both good and bad.

potential downside: If people only fix things locally, then they may be less inclined/likely to actually/also submit a merge request, and therefore it may be less likely that this actually (ever) gets fixed upstream. Which is kind of ironic, considering the stated goal "No more waiting around for pull requests to be merged and published." But if this obviates the need to create a pull request (does it), then this could backfire / work against that goal.

Requiring someone to fork a repo and push up a fix commit -- although a little extra work compared to just fixing locally -- is actually a good thing overall, for the community/ecosystem.

Ah, good, I see they touched on some of these points in the sections:

• Benefits of patching over forking
• When to fork instead

Even the author of this library forgot this about Svelte?? :) (Or maybe he didn't and this response misunderstood/falsely assumed that he had.)

I assume this gets search traffic because people hope/assume that since there's a React "material-ui" that there might already be a "svelte-material-ui" port/adaptation available. So they search for exactly that (like I did). That and being the first to create that something (with that name).

There seems to be an artificial pressure and a false assumption that the version that gets printed and included in the box be the "magic number" 1.00.

But I think there is absolutely nothing bad or to be ashamed of to have the version number printed in the rule book be 1.47 or even 2.0. (Or, of course, you could just not print it at all.) It's just being transparent/honest about how many versions/revisions you've made. 

The caveat/mistake here is if you treat it / think that it is equivalent to if a then b else c. That is not the case if b has any chance of failing.

Linked to from: https://security.stackexchange.com/a/183973/43759