We were all hoping AI would do the dishes, laundry, vacuuming, and mow the lawn - so we would have more time for art, music, coding, crafts. Instead, we get second rate "art" from the AI and rather lame "roomba" machines for vacuuming and mowing.

This bread, non-organic, is for sale in our grocery in Eastern US. My question: can I be confident it is not grown with glyphosate (Roundup™)? I wonder if the loaves are imported, or baked in the US under direction of the company. The unopened loaves do have a long shelf life sufficient for shipping by sea.

https://www.mestemacher.de/

Woe to him who amasses what is not his and makes himself rich with many loans! How long will this go on?’

Will not your creditors suddenly arise and those who disturb you awaken? Then you will become their prey.

Habakkuk 2:6-7

It pops up four time. A fifth time if you post a note.

It forgets them all if you close the tab.

There's an IRS form for "barter income".

Self hosted email is easy. Google requires you to register DNS cookies for your email domain if your IP4 is not a class C or better (or you are IPv6). That is evil, yes.

Dealing with spam is NOT so easy. One low tech way is to give out a unique email address to each correspondent (just edit the aliases file, or use a simple gui that automates most of this).

I wrote the pymilter package to make custom mail filters for sendmail and postfix coded in Python. I use a bayesian filter.

At this point, 90% of spam comes from gmail.com. I am about to make that domain "whitelist only". But in case it is a legit would be correspondent, what method could I offer in the rejection message (not that anyone ever reads the rejection message) for requesting contact? Maybe tell them to use XMPP or IRC? That is beyond most "normies" as well.

Is this with or without intentional mortality (e.g. abortion)?

"massively reduce spending" - and right there is your problem. A substantial percentage of that spending goes to השרים ("the officials"/administrative state/deep state) . Similar problem to endless unconstitutional wars. All that money funding both sides to kill each other siphons back to support American families in the Shadow of Mordor and Defense Industry areas.

As a lightning channel, you *could* transfer an amount equal to the small change you have on hand to another channel - perhaps overpaying the imbalance. That would require software support (rather tedious to calculate manually).

“I give you bitter pills, in a sugar coating. The pills are harmless - the poison's in the sugar.” ― James St. James, Party Monster: A Fabulous But True Tale of Murder in Clubland

Yes, the solution is "don't spend small amounts". That's why we have layer 2 protocols.

Gold had a similar problem in ancient times. Small amounts would get lost/stolen. Hence the eventual development of layer 2 protocols consisting of pieces of paper representing gold deposits. And the cycle continues.

No. Just sent email. To your protonmail listed in your commits.

Hope I did that right. It's been decades since I sent patches via email.

I added proposed rules as an HTML comment. I'm figuring out how to send the patch. Might have to be email.

We could mandate html "code" style for identifiers. I'll be inconsistent and do that only when then end a sentence for this pass.

Or we could go with "period as separator, not terminator". Current style is inconsistent.

Hmmm. What about sentences ending in an identifier? E.g.

ngit is more opinionated focusing on nip34+

Is `src/routes/about/+page.svelte` the source for the about page? Or something generated?

The style is inconsistent. Some sentences begin with upper case. Some paragraphs end with a period. Dropping the traditional "capitalize first letter of every sentence" style is handy for tech documents which often begin sentences with identifiers which are confusing when capitalized (e.g. "git").

* I propose to keep starting sentences with lower case, but end all sentences with punctuation. (Even some paragraphs currently end with period.)

* Titles (headers) are capitalized.

* Some FAQ questions are capitalized, some not. I think they should be capitalized in traditional style. Rewording can avoid starting with an identifier (like "git"). The answers follow the (no initial capital) paragraph/sentence style above.