Hab‘ ich das richtig verstanden? 😳 Unsere Landwirtschaft (auch Bio) macht Männer potenziell unfruchtbar? Und sowohl das #BAG als auch das #EDI interessiert’s nicht wirklich?
Not specifically made for pride month, but I have some of the rainbow strap bags left if you are looking for something to add color or gift them to someone. :neofoxpeekowo: They are about 18x24 cm and all come with a really vibrant rainbow strap. The fox ones even have more foxes (and Eevees!) inside on the lining.
I raised my hand to order another drink, only to withdraw it when Emily said, “Don’t you think you’ve had enough?”
She softened her tone and continued, “It would be best if you were clear-headed while we plan this.”
“Sure,” I said. “I hardly feel alcohol, but if we slip up, who knows what those rabbits or Emily might do.”
“That’s what I mean. You loused up calling her Emily, not Miss. Pang. Little things like that can get you killed in the spy business.”
While I couldn’t die, and I wasn’t a spy, Emily was right; a minor mistake might set Ms. Pang off.
We stopped talking briefly as the steward arrived. I ordered a club sandwich and soda water. I’d taken Emily’s advice: no more alcohol.
“So tell me about your secret life,” I said.
Emily thought for a minute and turned scarlet. Whatever she was thinking must be juicy for our matter-of-fact reporter/spy to blush.
“For months, I was convinced I had to take orders. I even asked one of the school nuns. I was sure I’d go to hell after necking with a girl in one of the bathroom stalls. It was my first time.”
I was taken aback that she’d share that while stone sober. My face grew hot picturing it. I even had a quick flash of being groped in a car by a boy.
“That might be too personal,” I said. “Ms. Pang will think I’m a stalker from her high school days.”
“Right. Sorry. Let me think. When I was a kid, I let our pet hamster out to play. Then a friend dropped by, and I ran out to meet her, forgetting all about him. Mom found the cat stalking Billy, and my brother got blamed. I still feel guilty for never owning up. Father could be mean when he was angry, especially when he was in the #bag.”
“That’s good. How about some follow-up information?”
“Let’s see.” She paused again as my meal arrived.
When the steward was gone, she rattled off the information. “Someone once climbed through my window and broke the little crystal swan my mother gave me. Who it was is a mystery, but I kept it to myself. I didn’t want my parents to know I could shin down the oak at night; the first time I got drunk was in Germany, when I was an exchange student—on cheap schnapps; Miss McGuire never knew who let the #air out of her tires; my mother gave me a stuffed bear, it’s still on my bed; my favorite film was Morocco. Marlene Dietrich in white tie and top hat was as racy as they come.”
“That should do, and you can stand behind me, feeding information if I need it.”
“Morocco,” I thought. “She at least has good taste. Marlene’s scene in the club was indeed hot.”
Note: From the next chapter: "I was possibly a professor or librarian."
Monthly meetings are held on the first Thursday of each month, at 13h00 to 14h00 Eastern Time (currently 17h00 to 18h00 UTC). You can find them listed in the SocialCG Calendar. The next meeting will be held on 3 April 2025.
We will be discussing:
Review of brainstorm/whiteboarding session from March
Context Ownership
Brainstorm use cases/user stories
Moving objects (between contexts) and moving contexts (between audiences)
Relies on context ownership “FEP”
Brainstorm use cases/user stories
Support for multiple objects (forking)?
Same origin only? Support moving objects/contexts between instances? Different FEP?
Predates ActivityPub, was submitted to the W3C, has evolved up until ~2018 in some form. Concepts that could be relevant for Forum TF work:
sioc:Item is directly associated with a sioc:Container, whereas as:Object is included in an indirect list of items within as:Collection
Containers vs CollectionsFor more on the difference between a Container and a Collection, see RDF Schema sections 5.1 and 5.2
A Container has open membership. There might always be more items in a container that are unknown:
<#Bag> <contains> <#red_ball>.<#Bag> <contains> <#green_ball>.<#Bag> <contains> <#blue_ball>.# We do not know if the bag contains any other balls, such as a yellow ball.</contains></contains></contains>
A Collection can have closed membership. For example, Lists can be terminated with a nil element.
<#List> rdf:first <#A>.<#List> rdfs:rest rdf:nil.# We know that the list does not contain any more elements beyond A.
The way this is applied in ActivityStreams is like so:
<#Collection> as:items (<#Item>).# There is no way to signal that the Item is part of the Collection, and it is not expected that collection items will expose links back to every single collection they are a part of.
We probably want to separate eventually the idea of "i authored this" from "i have authority over this", especially if a forum "lives" somewhere on a host.
Comparison to NNTP / NetNews protocol / Usenet networkRFC 5536 defines an article format for sharing RFC 822/2822/5322 style Internet Messages with mandatory headers:
Date (as:published)
From (as:attributedTo)
Message-ID (@id)
Newsgroups (as:audience??)
Path (no analogue, represents the path taken as the article is shared across newsgroups? so an ordered list of where it was shared/reshared from?)
Subject (as:name or as:summary, but probably not required for AP Forum TF)
RFC 5537 describes architecture for distributing such articles as Internet Messages:
A "posting agent" passes an article to an "injecting agent"
The "injecting agent" injects the article into a group
A "reading agent" can then fetch articles from a group
Example of a successful posting: [C] POST [S] 340 Input article; end with <cr-lf>.<cr-lf> [C] From: "Demo User" <nobody> [C] Newsgroups: misc.test [C] Subject: I am just a test article [C] Organization: An Example Net [C] [C] This is just a test article. [C] . [S] 240 Article received OK Example of an unsuccessful posting: [C] POST [S] 340 Input article; end with <cr-lf>.<cr-lf> [C] From: "Demo User" <nobody> [C] Newsgroups: misc.test [C] Subject: I am just a test article [C] Organization: An Example Net [C] [C] This is just a test article. [C] . [S] 441 Posting failed Example of an attempt to post when posting is not allowed: [Initial connection set-up completed.] [S] 201 NNTP Service Ready, posting prohibited [C] POST [S] 440 Posting not permitted</nobody></cr-lf></cr-lf></nobody></cr-lf></cr-lf>
We could probably do something with Announce and/or Offer or similar?
In a simple model where there are only groups and posts, no threads (a la FEP-1b12)
Offer Note to Group
Group can then accept/reject the post and issue an Announce?
Once we introduce threads, we will want to have more control not at the group level but at the thread level.
There is a bit of a philosophical question of approach here -- given that the core mechanism here is fundamentally notification messages via LDN (POST to inbox), although it is arguable that Activity payloads gets used as a sort of JSON-RPC more than as a notification... should we therefore optimize for a notification-oriented flow or a more procedural flow instead?
In a notification flow, we just want some resource to be aware that we have made a new post, and they can then distribute it or not. Say something simple like this:
but instead of addressing or targeting you might instead address or target ? whichever application is listening to the thread's inbox then handles the cascade of distribution upward:
the challenge is in avoiding duplicate traffic, so ideally this would be under the control of a single controller who issues a single Announce to the sum total of the accumulated audience:
this is essentially an event driven architecture. you'd need to choose between "exactly once" and "at least once" delivery.
concerns:
what ends up in shares collection? for a single share action, do we end up with multiple Announce activities in there?
who gets addressed? inbox forwarding? this probably shouldn't be the responsibility of to have to be aware of every single downstream/upstream recipient, right?