13.5 miles yesterday morning, Austin’s entire Lady Bird Loop(6) plus a roundtrip to Jo’s(1) and back.
Starting just before sunrise, I snapped some colorful building art(2) on the way to the river/lake. I caught a view of buildings on both sides of the river and a bridge spanning it, reflected in dim dawn light under overcast clouds(3). Barely caught the sun rising between buildings, swans in the foreground, before it disappeared behind clouds(4).
Many things caught my eye, like this almost symmetrical under bridge(5). Caught a better lit shot of the LIVE A GREAT STORY artwork on the MoPac bridge(7). The south bank trails had long stretches of paved paths that wandered just above the river/lake, saw a few birds stretching their wings(8).
Ran around to and crossed over the Longhorn Dam(9) before continuing around back to Congress Avenue, crossing the Congress bridge south to Jo's just for a photo. Ran back to the hotel to quickly get cleaned up, pack, and head to the airport to fly home.
Added a Recent Photos embed to my homepage sidebar (or bottom of the mobile view) at #IndieWebCamp Austin projects day! Still tweaking, yet quite happy with how it looks, e.g. compared to an @Instagram profile. #indieweb #takebackyourweb #ownyourphotos #iOS #Firefox #screenshot
Made it to @Nov_Project_ATX yesterday morning! Ran, worked out, and caught up with pal Holly who I haven’t seen since she moved from SF, and Madison friends Jen and Nicole (who herself also moved to Austin).
Ran back to downtown and the river afterwards, for a calm reflection(2), and sunrise over nearby buildings(3).
@IndieWebCamp Austin, facilitating a session on All Things Photos. E.g. taking photos, curating, editing, posting.
My incremental #indieweb #photo workflow: 📷 take photos in the moment, but not post* 🖼 curate photos, e.g. delete duplicates or non-HDR versions (or keep the non-HDR version if it was sharper, less blurry, or if the HDR versions had weird motion artifacts) ❤️ favorite photos, in the iOS Photos app, that I want to actually consider posting publicly, or perhaps uploading e.g. to a wiki ✍🏻 edit photos, e.g. rotate & crop, especially favorited photos, to align the horizon, crop out extraneous/distracting things, etc. 👇🏻 choose a favorited photo from that day as my main photo to post 📝 write a narrative caption based on that photo 📓 more photos: include more favorited photos if they make sense as part of the narrative, perhaps seek out more (non-favorited) photos to help illustrate the narrative 📮 post that photo or multiphoto post (its own process) ♡ unfavorite the photos I posted, except those I might want to view or show to friends later
I’m looking to simplify my process where I can, as it often takes me up to half an hour to actually get from curating my photos to posting a particular (multi)photo post!
*I don’t post photos in the moment any more in order to stay present in whatever I’m actually doing IRL. Instead at "in between times" like standing in line, or on transit, I take incremental steps towards publishing photos.
#IndieWebCamp Austin keynote by Pace from the future where: - We never build the same thing twice - Nobody gets betrayed - No more sexual predators - No more marketing - No more bad science - No more capitalism & it’s all built on #IndieWeb technologies!
Great first #IndieWebCamp Austin keynote by Natalie on the upsides and downsides of #socialmedia, how she started her #IndieWeb Gratitude Joural @microdotblog, did #DeleteFacebook, yet still posts @Instagram, though with a much more limited circle.
🌆🌴🌙 Distant low clouds and a delayed sunrise @Nov_Project_SF yesterday morning(1). We had a clear view of the crescent moon earlier as dawn blues were turning purple(2). The sun did eventually rise a few minutes later(3), as some of us went to work, others to breakfast.
where GitHubURL is a URL that starts with https://github.com/ ... and ends with a number segment (optional # fragment), just as it currently supports the "github topic: GitHubURL" syntax, because it is easier to remember, and 100% of past uses of "topic: GitHubURL" were clearly intended to do just that, and had to be unnecessarily followed up by a redundant "github topic: GitHubURL" command.
Note that this is a very precise request for what to allow, with the text after "Topic: " immediately being an https://github.com/ URL without anything else preceding, and ending with a URL segment that is a number, to avoid errant use of other GitHub URLs.
Given that level of precision, this reflects existing attempted use in the logs 100%, and is sufficiently guarded against false positives, at least from the past ~4 years of history in the logs.
No Tam Tuesday today. Instead of 1hr+ driving solo (carbonguilt) back and forth, I decided to stay local and do Twin Peaks repeats.
Tough morning, barely made it up to Tank Hill for a chilly NPSF yoga led by Sam, where we watched the sky change colors and the sun rise(2). Afterwards I invited her to run up to Twin Peaks with me, to get warmed up again.
We chatted about many things, recent challenges (I’m grateful for her presence). She ran up the last steep dirt path and snapped a photo(1) as I was catching up. Took a couple of photos myself(3,4).
We sprinted back down and got coffee with other #NPSF friends in Cole Valley.
Much later (after a late lunch) I went out for another run. Ran down to the Panhandle and then up to the top of Twin Peaks(5). Twice, which barely completed half the elevation gain of running up Tam once!
With both morning and afternoon runs I completed 10+ miles, and three Twin Peaks ascents for the day.
🌲⭕️🌲 8mi + ~1400' to finish a 40mi + ~9000' week. #50mileTraining
While the weather app says Mostly Cloudy, I see Partly Blue, with a clear view of downtown #SF and the Port of Oakland(2) from the top of Corona Heights Park. Our distinctive Sutro Tower space claw(3) never gets old.
Someone was flying a red kite from the top of Corona Heights Park(4). After running to the summits of Buena Vista, Corona Heights, and Mount Olympus, I ran down to Cole Valley and then Kezar Stadium. I’ve been missing track workouts.
The setting sun lit up the clouds so brightly they were overexposed above the track. I spotted a runner crushing it in lane 1; not the only one getting in a late Sunday run(5).
Ran around the outer level of the stadium to the other side for a better view(1), completed the 800m lap and ran home. Pause. Quick change of shirts, cleaned up, packed my headlamp and ran with a friend to sushi dinner, paused again. Ran her home afterwards and then back in the dark (with headlamp). Finished my Sunday 8.
⛰🏃🏻♂️ 27 days (<4 weeks!) til #MUC50. 10 miles at #SFRC yesterday, practicing a few more of the race course trails.
Yesterday morning’s Coastal Fire Road ascent was much clearer than the week before, with a nice view of Tennessee Valley, the tiny lagoon and beach where it meets the ocean(2). Feeling more confident about the Pirates Cove descent & ascent(3) after running it two Saturdays in a row. The view from the top(1) of that trail could be so many places along the California coast, or even parts of Hawaii.
Ran down near Muir Beach, and up Middle Green Gulch trail, to Coyote Ridge, then down Miwok back to the Tennessee Valley parking lot. Had a bit more time so ran up Old Springs Trail, taking in the view(4), and imagining what it might look like at dusk.
We are generally in favor of this effort, however, we request submission to WICG.
We also have some concerns about the specific implementation. In particular,
WebCrypto took a real “no seatbelts” design approach which we now
think is wrong. That's perpetuated here and we’d like to revisit that.
It would probably be good to add some other algorithms as well
None of the existing groups really seem appropriate so maybe we need
to reboot WebCrypto (whether in W3C or WHATWG). Not sure if this
needs incubation, but in the interest of getting it out of a private
repo, please submit to WICG while we figure out the rest.
☁️🌉 Overcast morning, no sunrise, just Bay Bridge Lights sparkling on the bay as we started the @Nov_Project_SF Cupid’s span workout where your reward for sprinting then offering or being offered a flower was 10 burpees together 🌹😅
Example 2: @benwerd’s own site, werd.io,
shows photos backwards through
however if you click "Older" there, you will see at offset=440 (or perhaps the next one) that one or more photo posts are missing their images, and are falling back to rendering only their alt text.
🌄 First 2020 #MountTam summit, yesterday with @BryanTing(1). Rough morning in a few ways, still got my 3rd fastest time to the door at the top(2). Stopped once to take a photo of the pre-dawn blue gradients and orange horizon(3), click thru the photo on my site for a mobile wallpaper version.
After that ritual touching of the door, I took a shot of the beautiful sunrise above East Bay hills(4). Moments earlier we knew the sun had crested when we saw the rocks we were climbing on the final scramble suddenly turn bright orange.
Bridgy Backfeed sends current and future silo responses to your posts as webmentions,
for your posts to handle as they come in. It would be great to have the complementary service of Bridgy Backfill (feel free to bikeshed the name) to send past silo responses to your posts as webmentions, as a way of backfilling / importing old responses to your posts, including your old posts.
The key use-case here is: help with migration away from social media.
If you can backfill/import the comments/responses on your old social media posts into your own site, then you have fewer reasons to keep around those old social media posts, and thus fewer reasons to keep around that social media account.
Such migration of responses to old social media posts would also enable deletion of those old social media posts, as a step towards de-activating and deleting a specific social media account.
Since it’s likely you may only want to run this "once" and it may take a while as it will likely require crawling your silo posts history which may be throttled, this makes sense as a separate service that you authenticate, activate, and then allow it to progress back through your old posts (and old responses to your posts),
perhaps with some progress indicator, and perhaps with some sort of notification when it has completed.
This new service would be in addition to the existing Bridgy services: Bridgy Backfeed, Bridgy Publish, Bridgy for Blogs, and Bridgy Fed.
↳ In reply to pull request 916 to GitHub project “bridgy”Rather than assuming, I checked the Bridgy source, which uses Granary for this, and verified that Granary does have an explicitly enumerated list for the reacji that GitHub allows.
I also strongly disagree with even hinting that we might think this API is "non-harmful" when that hasn’t even been mentioned in https://github.com/mozilla/standards-positions/issues/153 — in fact quite the opposite, I noted explicitly there that "I’m leaning towards expecting an eventual 'harmful' evaluation."
So I’m not ok with moving it into the description, and that is unnecessary for a defer position. I’d like us to be able to actually defer rather than debate more details in the description.
Re: "leaves their source unspecified", I’m ok with dropping that from the description, it’s not really an actionable criticism outside of a thorough evaluation. I’ll update the PR accordingly.
GitHub issues accept a set of special responses via their user interface:
As part of using our own websites to publish and POSSE issues instead of GitHub,
it would be great if Brigy Publish to GitHub could be expanded to handle these
special response types.
As a first step, this issue is a request to explore the possibility and document
any available GitHub API calls to do so, either purely as issue state change responses,
or perhaps in the case of "close", the ability to close with a comment in the UI of
an issue by clicking the "Close issue" button to the left of the "Comment" button
(when available to the user).
More documentation of brainstorming special responses to issues and broader
considerations, e.g. issues state change special responses on other systems, see
the IndieWeb wiki:
issue: Special Responses
🗼🌄 Raced the sunset to Twin Peaks yesterday and won. 6 hills in 6 miles & 1500'. Views from: 1. Buena Vista Park Summit(2) 2. Corona Heights Park Summit(1) 3. Mount Olympus(3) 4. Twin Peaks North Peak(4) 5. Twin Peaks South Peak(5) *. North Peak (again) just after sunset, looking down a lit Market street under a cloudless cotton candy sky(6) 6. Christmas Tree Point classic downtown SF view(7)
🌤⛰ 12 miles at #SFRC today with pal Brooke. Low hanging when we started in Tennessee Valley, the fog swirled and arced between the hills(2) up Coastal Trail. As we emerged from the fog, we could see the Pacific in the distance, framed by hills, most of the fog below(3).
Brooke and I got to the top and a stranger offered to take our photo above the fog and clouds(1). I took a photo closer to the edge(4). We ran down to and through Pirates Cove, back up a bit, down to Muir Beach, then over to the Redwood Creek Trail.
Reached the Miwok Trail and turned right, heading south toward Coyote Ridge(5). The trail wound through ferns and moss lined trees(6) until peaking, downhill to crossing Highway 1, then back up in view of the opposite side of a valley(7). On the other side, a green view back down to Tennessee Valley where we started(8).
Got veggie burgers at Good Earth. More runner friends joined us and we enjoyed catching up in the warm sunshine.
🦜🦜 Quiet day @MozSF yesterday, til the #parrots came to visit. Such a distinctive squawk, I heard it clear through the walls and windows. I looked over and one glanced at me, the other on the lookout(2). Walked out to the deck and they both looked over, now together(3). I walked over to the ledge and they looked at me and squawked more quietly, together(1).
I got the feeling they were saying one thing: hope.
For a while I have brainstormed designs for a user experience (UX) to create, edit, and publish notes and other types of posts, that is fully undoable (like Gmail’s "Undo Send" yet generalized to all user actions) and redoable, works local first, and lastly, uses progressive enhancement to work without scripts in the extreme fallback case of not being installed, and scripts not loading.
I’d like to be able to construct an entire post on a mobile device, like a
location tag etc. all locally, offline, without any need to access a network.
This is like how old email applications used to work. You could be completely offline, open your email application (there was no need to login to it!), create a message, add attachments, edit it etc., click "Send" and then forget about it. Eventually it synced to the network but you didn’t worry or care about when that step would happen, you just knew it would eventually work without you having to tend to it or watch it.
I want to approach this from user-experience-first design perspective, rather than a bottom-up protocol/technology/backend first perspective. For one, I don’t know if any existing protocols actually have the necessary features to support such a UX.
Micropub has a lot of what’s needed, and I won’t know what else is needed until I build the user flows I want, and then use those to drive any necessary Micropub feature additions. I absolutely do not want to limit my UX by what an existing protocol can or cannot do (essentially the software design version of the tail wags dog problem).
I wrote up a brief stub article on the IndieWeb wiki on
I see local first as an essential aspect of an authoring experience that is maximally responsive to user input, and avoids any and all unnecessary ties to other services.
I want a 100% local first offline capable creating / editing / posting workflow which then “auto-syncs” once the network shows up. The presence / absence of internet access should not affect user flow at all. Network presence or absence should only be a status indicator (e.g. whether / how much a post has been sent to the internet or not, any edits / updates etc.). It should never block any user actions. I’ll say it again for emphasis:
The absence or presence of network access must not block any user actions. Ever. Any changes should be effective locally immediately, with zero data loss.
Nearly no one actually builds apps like that today. Even typical mobile “native” apps fail without network access (a few counter-examples are the iOS built-in Notes & Photos apps, as well as the independent maps.me 100% offline mapping program). Some
apps get close. But even those, especially on mobile, fail in both predictable (like requiring logging into a website or network service, just to edit a local text document) and strange ways.
Full Undo Redo
Every such user action should be undoable and redoable, again, without waiting for the network (it’s reasonable to apply some time limits for some actions, e.g. Gmail Undo can be configured to work for 30 seconds). Now imagine that for any user action, especially any user action that creates, edits, or deletes content or any aspects thereof (like name, tags, location etc.).
In the case where a web application has not yet been installed, I also want it to be 100% capable without depending on loading any external scripts.
This JS-Optional approach is more broadly known as
progressive enhancement, which does require that you have at least some connection, enough for a browser to submit form requests and retrieve static HTML (and preferably though not required, static CSS and image files too).
Once you are connected and are running at least a
for the site, local first requires execution of some scripts, though even then dependencies on any external scripts should be minimized and preferably eliminated.
I believe aspects of this experience can be built and deployed incrementally, iterating over time until the full system is built.
I’ve got a handful of paper sketches of local-first undoable/redoable user flows. I have a Service Worker deployed on my site that allows offline browsing of previously visited pages, and I have a form submission user interface that handles part of publishing. There are many more aspects to design & implement. As I think of them I’m capturing them in
part of my “Working On” list on the IndieWeb Wiki, iteratively reprioritizing and making incremental progress at IndieWebCamps.
↳ In reply to issue 153 of GitHub project “standards-positions”I read and re-checked the Explainer, and frankly given the repeated past Contacts API failures and zero mention of them in the Explainer, I’m going to deem this proposal not worth taking the time to thoroughly evaluate until the Explainer at a minimum:
1. Documents previous Contacts API standards attempts (see https://tantek.com/2020/026/t2/ for some links to start) 2. Provides summary explanations for their failures 3. Describes how the current proposal is different from previous proposals in such a way as to at least avoid those failures (i.e. there should be a logical chain of reasoning from identifying key differences and how those either cause or prevent different outcomes from prior attempts).
Also given the critical comments in that discussion, especially from https://github.com/torgo, and knowing how much more abusive social network/media "apps" have become with aggressive sign-up, spam, user-acquisition tactics in recent years, I’m leaning towards expecting an eventual "harmful" evaluation.
If the purely markup-only approaches were separated out into another proposal, I’d be more optimistic of more quickly evaluating those, and expecting browsers could implement those simpler (fewer ways to use/abuse) feature(s) in such a way that could be "worth prototyping".
Per and as promised in
my reply to issue 796
(comment on #796),
it may be of some value to add Micropub as a generic Bridgy Publish destination,
that is, Bridgy Publish acting as a Micropub client to post to Micropub servers.
One possible use-case would be Bridgy Publish to silo.pub, and thus potentially enabling use of Webmention to Bridgy Publish as a method to gain access to any additional destinations that silo.pub itself supports. I.e.:
The IndieWeb This Week newsletter’s "New Wiki Pages" section, e.g.
2020-01-31 New Wiki Pages
should also include pages that are not literally new in MediaWiki terms,
but were a redirect page,
and during the week before the newsletter were edited to no longer redirect,
and have their own content instead.
Currently in order to make a redirect page that’s been converted to a content page
show up in the "New Wiki Pages" section, you have to delete the redirect page,
and then recreate it with the new content. For example I did this today with the
local first page.
Ideally there would be no need to take that extra step of deleting the redirect page first.
⭕️🏃🏻♂️ Track Tuesday. Made it just before sunrise for a warm-up and several 400s. Finished 5k total including the warm-up and cool-down jogs to/from the track. Snapped a photo at the top of the South bleachers, revealing slight asymmetries.
@ToddFahrner & I invented standards mode via DOCTYPE switch.
@ToddFahrner proposed DOCTYPE switching and strict/standards mode conceptually.
I was the first to implement it, because I invented the specifics of which DOCTYPEs should mean what with/without URL (through a lot of personal research of existing sites), and which features to flip. I worked with the Tasman team to slowly, conservatively grow the list of quirky or quirks mode features as needed.
I shared the specifics of this design with @cwilso and the Windows IE team, who eventually re-implemented it in IE6/Windows.
I deliberately did not publicly document the full set of quirky features because we wanted the option to remove them one at a time, as sites were updated to be standards compliant. We encouraged web authors to always use standards mode or strict mode in any new sites and site updates.
At the time (over 20 years ago) I published a few notes on a static HTML page as I developed the details:
As someone who has written a few custom parsers for HTTP headers, I welcome this.
Agreed with at least "worth prototyping".
With the potential to reduce duplication of code, and especially reduce infrequently-run code paths for rare(r) headers, I think there are likely security benefits as this is adopted for new (and possibly old headers).
For that reason I think Mozilla should consider this as "important" or at least state that we can see this being/becoming "important".
🌅⛰ 9 miles of #MUC50 course practice, 12.5 total, 2900' climbed. Saw badass ultra runner @HeatherRoseSF at the Rodeo Beach start and proceeded to set a PR up to Hill 88 by several minutes, even with stops to photograph Rodeo Beach and the Golden Gate(2). Ran down Wolf Ridge, down Miwok, then up Coastal where I ran into pal Rebecca, before #running to SCA for a view of downtown SF(3).
Climbed up Alta to the top of Marincello to complete my 9 miles of course practice (41 to go 😂) then #ran up Miwok to VORTAC hill for another distant view of SF behind the Headlands(4), and the VORTAC itself, backlit by the sun(5). Ran down Miwok all the way to Rodeo Valley where I caught the setting sun shimmering on Rodeo Lagoon(1), just before it slid behind an ocean fogbank, disappearing by the time I finished where I started.
🗓 Home for February 1st, reflecting & anticipating in solitude. Deep breaths.
January went mostly as expected. Completed one phase of a #transformation, just enough to consider and plan the next. Peace & distance provided space for healing, restoring empathy, sensing & seeing more. Picked up my ultra training again, found it difficult to keep up while away in Berlin. Ended the month on a different higher note than expected.
The past month’s shedding continues, to new depths of self-disruption. Growth from recovery will shift to growth from discomforts. My last training cycle for my first 50 miler, I’m expecting physical & mental challenges like never before. Returning to regular yoga classes and restarting my yoga sutra philosophy studies. Healing and growing capacities. Writing and reflecting on building blocks for positive self-propagating changes.
#MOZILLA in lights. The #Brrrlin All Hands was packed, half filled with pre-planned sessions & discussions, and half with spontaneous or late planned meetings. Plus video meetings with other folks back in California, late night our time.
Will take a while to go through my notes and summarize, a few highlights.
#Environment. We had nearly a day of environment related sessions. I am super excited about the progress made here since we did a last minute grass roots session at the last all hands.
The Museum of the Fossilized Internet.
State of the Internet Exhibit and all the thoughtful critique of the Surveillance Economy.
The Standards lunch and all the standards meetings in general.
Many people calling for a return to working more in the open, encouraging people to blog the things they’re working on, with progress and updates.
It’s been a great week and I’m looking forward to returning home.
🏙☁️🏃🏻♂️ Out & back 3.5 mile run along the #Landwehrkanal to the Dovebrücke(1) just before dark, after being cooped up indoors all day @Mozilla #Brrrlin All Hands.
I ran past where I had gone on Monday (https://tantek.com/t54o1) until the path ended and I had to cross a couple of bridges to resume another branch of the canal. After another bridge I noticed a quirky bold blue industrial building on tall stilts with a giant pink pipe(2) looping out, under, and back in, like a massive intestine resting on the opposite shore of the canal.
A brightly colored orange & yellow houseboat was docked on the near shore(3). A little up the shore was an object that looked like a giant bright yellow mallet from a video game(4). For a moment my years of practice with adventure problem solving video games kicked in.
I stood back(5) and briefly tried to assess if I needed to grab the mallet before hopping onto the houseboat to cross the canal, then use the mallet to bust into the pink pipe to enter the blue building on stilts where presumably there'd be a boss of some sort inside to defeat and/or someone to rescue.
Decided to skip that level and keep running. Ran under another bridge where I encountered another pink pipe(6), purpose unknown. There are various brightly colored (pink, purple, etc.) exposed pipes adjacent to public footpaths across Berlin. I have no idea if they’re functional, decorative, or both.
Checked the time at the next bridge, realizing I was beyond my temporal halfway point, ran up to take a photo looking down the canal the way I came(7) before running back at a quicker pace, without stopping for any more photos.
Privacy Community Group charter in the Mission, Scope, and other sections, should explicitly mention incubation, and drop & avoid language which implies working-group-like standards development.
should explicitly list where incubations are intended to graduate to,
separately from groups expected to coordinate with as relevant.
Also the Process
section should also describe exit conditions for an incubation,
for how / whether a proposal should be abandoned/dropped from the group,
or how a proposal should complete incubation and considerations for how to choose
which Working Group it should graduate to.
Some specifics: in the
section up front it says
“to develop privacy-focused web standards and APIs”.
That should for example be changed to say incubate, e.g.
“to incubate privacy-focused web standards and APIs”.
there is mention of
“2. The deliverable phase, AKA specification.”
This should be dropped from the CG charter, as when the incubation phase has completed
for a proposal, the next step should be to transition it to a working group.
Nicknamed “der hohle Zahn” (the hollow tooth), the Memorial Church is known for its damaged spire, bombed out in a 1943 raid. Characterized as the “heart of Berlin”, it was left ruined due to public outcry against tearing it down.
At a minimum its presence poses questions for anyone unfamiliar with it. Why is it so damaged? How did that happen? Why has it not been repaired or rebuilt? All of which inevitably serve as a reminder of WWII. Perhaps it helps discourage a return to the horrors of war.
“Reality ahead of schedule”. Saw the Syd Mead Exhibition at the gallery O&O Depot, where many of his Future Cities paintings and sketches were on display.
It’s fascinating viewing his paintings in the context of the years he painted them (1970s-2000s). There are aspects of both #utopia and #dystopia, depending on how you view them, which details you explore and analyze.
The paintings pose provocative questions about the implied systems behind the structures and the people.
What are the economic and political systems that enabled the construction of these cityscapes?
What are people’s roles in them, what purposes do they serve, and how are the structures maintained?
Could they be maintained by different political systems than those that built them or do they assume or reinforce particular systems?
The first photo is the only one that I saw that integrated present city features (Los Angeles city hall!) into a vision for the near future(1), with multiple generations and layers of construction. Others have apparently completed or fully formed visions.
There was also only one based on another world(5), likely the moon. Only a few show adjacency with the existing natural environment(3) or integration of planned natural features(6,7). In general the artwork shows fully developed or urbanized environments(2,4,8,9), or an indoor scene: Deckard’s kitchen from Blade Runner(10) lacking any apparent plantlife.
Fragmention processing model
says “the outer element that contains the text completely” which is not precisely defined. Depending on how leading/trailing text is handled, especially
(Issue #7), it may affect which element can be considered to “contain” the text “completely”.
In addition “the outer element” could always be returned as the body element, which is clearly not the intent of the Fragmention specification. The processing model needs some clarifications about the most precise, or minimal, or most deeply nested element or whatever is the intended meaning of the specification for “the outer element”.
Short run today before today’s #Brrrlin reception. Explored the #Landwehrkanal, found a dirt #trail. Moments appreciating just being here, outside, running. Thinking of Kobe & his daughter’s tragic deaths. Can have it all and never know for how long.
Turned around at a train bridge, saw bald eagles caged(2) in the adjacent Berlin Zoo. Overcast, warmer than yesterday. Caught a reflection of a green bridge over the canal(1) on the way back.
Welcome to #Berlin (& #Brrrlin) fellow #Mozillians! Be sure to check out the Berlin Victory Column, AKA the Siegessäule. Photographed from a bus, got a face-on view of the bronze sculpture of #Victoria, #goddess of #victory.
🌳🏰🌳 Ran to a #castle(1) and back, #overcast & freezing cold. 5 miles done. Ran along the #Spree river, bit more industrial(2) than yesterday’s path.
Reached the Castle Charlottenburg grounds, ran up a path lined with leafless trees planted in perfect rows(3), until coming upon a pond. Ducks congregated near the shore, one of them braving the kids on shore to snack on crumbs left behind(4). Ran to the other side of pond, crossed a foot bridge, took in a distant view of the castle(5).
Ran back to the other side of the pond just as a single swan swam slowly(6) across the shore. It was rejoining its mate, the two of them seemingly communicating with physical motions and gestures, without a single sound(7).