It has been a while since I last posted a drone video, so here is a great
spring day flying the DJI Air 2S around Morro Bay.

<https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>

--
Regards,
Savageduck

On 2022-04-05 13:27, Savageduck wrote:
> It has been a while since I last posted a drone video, so here is a great
> spring day flying the DJI Air 2S around Morro Bay.
>
> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>

Boycott until you fly at magic hours.

Spend the night there - then you can shoot in the evening /and/ the morning!

--
"Mr Speaker, I withdraw my statement that half the cabinet are asses -
half the cabinet are not asses."
-Benjamin Disraeli

On 6/04/2022 5:27 am, Savageduck wrote:
> It has been a while since I last posted a drone video, so here is a great
> spring day flying the DJI Air 2S around Morro Bay.
>
> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>
>

Lovely. Will be nicer still when those smoke-stacks come down. Or a
local treasure ?

Do these videos have stabilisation (etc) done in post, or is the raw
actually that steady and level ?

And have you ever got 'lost' ?

geoff

On Apr 5, 2022, geoff wrote
(in article<D_ydnTqPZerud9H_nZ2dnUU7-LXNnZ2d@giganews.com>):

> On 6/04/2022 5:27 am, Savageduck wrote:
> > It has been a while since I last posted a drone video, so here is a great
> > spring day flying the DJI Air 2S around Morro Bay.
> >
> > <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>
> Lovely. Will be nicer still when those smoke-stacks come down. Or a
> local treasure ?

The plan is for demolition by disassembly rather than implosion to reduce the dust issue, and disturbance along the Embarcadero.
There are some who have a morbid sentimentality, and at least one has a financial interest, "The Three Stacks, and a Rock Brewery”. There is bigger money coming in turning the old power plant into a massive energy storage facility.
>
> Do these videos have stabilisation (etc) done in post, or is the raw
> actually that steady and level ?

There is no stabilization in post. The technology in today’s GPS camera drones is amazing, and is just one reason that drones with good tech, including software, and camera hardware are not inexpensive. I am always amazed at how solid the flight can be, even in strong, gusty wind.
>
> And have you ever got 'lost' ?

Fortunately, no. They provide some navigation/map tools in the software, that and I have always maintained a sense of locational awareness. That said, GPS drones such as my DJI Air 2S will set a home point at take off. In the event there is a low battery, or loss of RC controller signal the software will initiate an Auto Return To Home (RTH), and it will return to the home point and land. Also if you are totally lost, and have lost visual contact with the drone you can push/tap t6he RTH button on the controller to start a return to home. Best to learn how to navigate, and save the RTH for real emergencies.

--
Regards,
Savageduck

On 05/04/2022 18:27, Savageduck wrote:
> It has been a while since I last posted a drone video, so here is a great
> spring day flying the DJI Air 2S around Morro Bay.
>
> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>

Another excellent presentation.

So different to the many views we are seeing of the desecration in
Ukraine. :-(

Am 05.04.2022 um 19:27 schrieb Savageduck:
> It has been a while since I last posted a drone video, so here is a great
> spring day flying the DJI Air 2S around Morro Bay.
>
> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>

This is better than previous videos because it's more 3D (that big Morro
bay rock for instance + you are getting closer to structures). Also,
approaching things from the sea is a good idea.
--
Alfred Molon

Olympus 4/3 and micro 4/3 cameras forum at
https://groups.io/g/myolympus
https://myolympus.org/ photo sharing site

On 06/04/2022 17:58, Alfred Molon wrote:
> Am 05.04.2022 um 19:27 schrieb Savageduck:
>> It has been a while since I last posted a drone video, so here is a great
>> spring day flying the DJI Air 2S around Morro Bay.
>>
>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>
>
> This is better than previous videos because it's more 3D (that big Morro
> bay rock for instance + you are getting closer to structures). Also,
> approaching things from the sea is a good idea.

I agree. Probably the best drone video he's shown us. :-D

On 05/04/2022 18:27, Savageduck wrote:
> It has been a while since I last posted a drone video, so here is a great
> spring day flying the DJI Air 2S around Morro Bay.
>
> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>

I've just watched this again. It's a very special place.

Some of us are truly blessed! ❤️

On 17/08/2022 11:50, David Brooks wrote:
> On 05/04/2022 18:27, Savageduck wrote:
>> It has been a while since I last posted a drone video, so here is a great
>> spring day flying the DJI Air 2S around Morro Bay.
>>
>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>
>
> I've just watched this again. It's a very special place.
>
> Some of us are truly blessed! ❤️

Reposting the link to check again.

On 10/09/2022 17:03, HunterBD wrote:
> On 17/08/2022 11:50, David Brooks wrote:
>> On 05/04/2022 18:27, Savageduck wrote:
>>> It has been a while since I last posted a drone video, so here is a
>>> great
>>> spring day flying the DJI Air 2S around Morro Bay.
>>>
>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>
>>
>> I've just watched this again. It's a very special place.
>>
>> Some of us are truly blessed! ❤️
>
> Reposting the link to check again.

The video at the link above now plays perfectly using Safari! :-D

Does it play for you?

On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
> On 10/09/2022 17:03, HunterBD wrote:
> > On 17/08/2022 11:50, David Brooks wrote:
> >> On 05/04/2022 18:27, Savageduck wrote:
> >>> It has been a while since I last posted a drone video, so here is a
> >>> great
> >>> spring day flying the DJI Air 2S around Morro Bay.
> >>>
> >>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
> >>
> >>
> >> I've just watched this again. It's a very special place.
> >>
> >> Some of us are truly blessed! ❤️
> >
> > Reposting the link to check again.
> The video at the link above now plays perfectly using Safari! :-D
>
> Does it play for you?

https://i.imgur.com/cjploXD.png

I've noticed this before.. can be fixed though:

https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ

On 10/09/2022 20:03, sobriquet wrote:
> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>> On 10/09/2022 17:03, HunterBD wrote:
>>> On 17/08/2022 11:50, David Brooks wrote:
>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>> It has been a while since I last posted a drone video, so here is a
>>>>> great
>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>
>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>
>>>>
>>>> I've just watched this again. It's a very special place.
>>>>
>>>> Some of us are truly blessed! ❤️
>>>
>>> Reposting the link to check again.
>> The video at the link above now plays perfectly using Safari! :-D
>>
>> Does it play for you?
>
> https://i.imgur.com/cjploXD.png
>
> I've noticed this before.. can be fixed though:
>
> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ

THANK YOU :-D

--
Crossposted to ACW for Apd's attention.

On 10/09/2022 20:12, HunterBD wrote:
> On 10/09/2022 20:03, sobriquet wrote:
>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>> On 10/09/2022 17:03, HunterBD wrote:
>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>> It has been a while since I last posted a drone video, so here is a
>>>>>> great
>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>
>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>
>>>>>
>>>>> I've just watched this again. It's a very special place.
>>>>>
>>>>> Some of us are truly blessed! ❤️
>>>>
>>>> Reposting the link to check again.
>>> The video at the link above now plays perfectly using Safari! :-D
>>>
>>> Does it play for you?
>>
>> https://i.imgur.com/cjploXD.png
>>
>> I've noticed this before.. can be fixed though:
>>
>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>
> THANK YOU :-D

For Apd - and anyone else who may be curious - in a fresh install of
Firefox the link now works perfectly and gives an excellent
presentation, filling my screen, clearly and crisply. Odd!

On Saturday, September 10, 2022 at 9:03:13 PM UTC+2, sobriquet wrote:
> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
> > On 10/09/2022 17:03, HunterBD wrote:
> > > On 17/08/2022 11:50, David Brooks wrote:
> > >> On 05/04/2022 18:27, Savageduck wrote:
> > >>> It has been a while since I last posted a drone video, so here is a
> > >>> great
> > >>> spring day flying the DJI Air 2S around Morro Bay.
> > >>>
> > >>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
> > >>
> > >>
> > >> I've just watched this again. It's a very special place.
> > >>
> > >> Some of us are truly blessed! ❤️
> > >
> > > Reposting the link to check again.
> > The video at the link above now plays perfectly using Safari! :-D
> >
> > Does it play for you?
> https://i.imgur.com/cjploXD.png
>
> I've noticed this before.. can be fixed though:
>
> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ

Kind of mysterious that the link (with the %20 in the url) referred to at the start
of that groups.google thread does load in both safari and chrome on my ipad mini..
but it refuses to load on the win10 pc in chrome.

On 10/09/2022 20:55, sobriquet wrote:
> On Saturday, September 10, 2022 at 9:03:13 PM UTC+2, sobriquet wrote:
>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>> On 10/09/2022 17:03, HunterBD wrote:
>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>> It has been a while since I last posted a drone video, so here is a
>>>>>> great
>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>
>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>
>>>>>
>>>>> I've just watched this again. It's a very special place.
>>>>>
>>>>> Some of us are truly blessed! ❤️
>>>>
>>>> Reposting the link to check again.
>>> The video at the link above now plays perfectly using Safari! :-D
>>>
>>> Does it play for you?
>> https://i.imgur.com/cjploXD.png
>>
>> I've noticed this before.. can be fixed though:
>>
>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>
> Kind of mysterious that the link (with the %20 in the url) referred to at the start
> of that groups.google thread does load in both safari and chrome on my ipad mini..
> but it refuses to load on the win10 pc in chrome.

Mysterious indeed!

I'm hoping that Apd will be able to get to the bottom of it. You'll find
him in MY home Usenet group - 'alt.computer.workshop'.

HunterBD laid this down on his screen :
> On 10/09/2022 20:12, HunterBD wrote:
>> On 10/09/2022 20:03, sobriquet wrote:
>>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>>> On 10/09/2022 17:03, HunterBD wrote:
>>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>>> It has been a while since I last posted a drone video, so here is a
>>>>>>> great
>>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>>
>>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>>
>>>>>>
>>>>>> I've just watched this again. It's a very special place.
>>>>>>
>>>>>> Some of us are truly blessed! ❤️
>>>>>
>>>>> Reposting the link to check again.
>>>> The video at the link above now plays perfectly using Safari! :-D
>>>>
>>>> Does it play for you?
>>>
>>> https://i.imgur.com/cjploXD.png
>>>
>>> I've noticed this before.. can be fixed though:
>>>
>>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>>
>> THANK YOU :-D
>
> For Apd - and anyone else who may be curious - in a fresh install of
> Firefox the link now works perfectly and gives an excellent presentation,
> filling my screen, clearly and crisply. Odd!

Does Chrome work now too?

I just tested in Edge, both worked fine. I used the URLs from your
original post (offering the second video) and just copy/paste to the
address bar, that is not by clicking a blue URL. Buffering took some
time but it played automatically at almost full screen size.

Why would a modern browser accept unsafe characters in a URL and reject
properly encoded ones?

On 10/09/2022 23:45, FromTheRafters wrote:
> HunterBD laid this down on his screen :
>> On 10/09/2022 20:12, HunterBD wrote:
>>> On 10/09/2022 20:03, sobriquet wrote:
>>>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>>>> On 10/09/2022 17:03, HunterBD wrote:
>>>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>>>> It has been a while since I last posted a drone video, so here is a
>>>>>>>> great
>>>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>>>
>>>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>>>
>>>>>>>
>>>>>>> I've just watched this again. It's a very special place.
>>>>>>>
>>>>>>> Some of us are truly blessed! ❤️
>>>>>>
>>>>>> Reposting the link to check again.
>>>>> The video at the link above now plays perfectly using Safari! :-D
>>>>>
>>>>> Does it play for you?
>>>>
>>>> https://i.imgur.com/cjploXD.png
>>>>
>>>> I've noticed this before.. can be fixed though:
>>>>
>>>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>>>
>>> THANK YOU :-D
>>
>> For Apd - and anyone else who may be curious - in a fresh install of
>> Firefox the link now works perfectly and gives an excellent
>> presentation, filling my screen, clearly and crisply. Odd!
>
> Does Chrome work now too?

Yes - it does! :-D

> I just tested in Edge, both worked fine. I used the URLs from your
> original post (offering the second video) and just copy/paste to the
> address bar, that is not by clicking a blue URL. Buffering took some
> time but it played automatically at almost full screen size.
>
> Why would a modern browser accept unsafe characters in a URL and reject
> properly encoded ones?

I cannot answer that question. :-(

On Saturday, 10 September 2022 at 23:45:30 UTC+1, FromTheRafters wrote:
> HunterBD laid this down on his screen :
> > On 10/09/2022 20:12, HunterBD wrote:
> >> On 10/09/2022 20:03, sobriquet wrote:
> >>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
> >>>> On 10/09/2022 17:03, HunterBD wrote:
> >>>>> On 17/08/2022 11:50, David Brooks wrote:
> >>>>>> On 05/04/2022 18:27, Savageduck wrote:
> >>>>>>> It has been a while since I last posted a drone video, so here is a
> >>>>>>> great
> >>>>>>> spring day flying the DJI Air 2S around Morro Bay.
> >>>>>>>
> >>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
> >>>>>>
> >>>>>>
> >>>>>> I've just watched this again. It's a very special place.
> >>>>>>
> >>>>>> Some of us are truly blessed! ❤️
> >>>>>
> >>>>> Reposting the link to check again.
> >>>> The video at the link above now plays perfectly using Safari! :-D
> >>>>
> >>>> Does it play for you?
> >>>
> >>> https://i.imgur.com/cjploXD.png
> >>>
> >>> I've noticed this before.. can be fixed though:
> >>>
> >>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
> >>
> >> THANK YOU :-D
> >
> > For Apd - and anyone else who may be curious - in a fresh install of
> > Firefox the link now works perfectly and gives an excellent presentation,
> > filling my screen, clearly and crisply. Odd!
> Does Chrome work now too?
>
> I just tested in Edge, both worked fine. I used the URLs from your
> original post (offering the second video) and just copy/paste to the
> address bar, that is not by clicking a blue URL. Buffering took some
> time but it played automatically at almost full screen size.
>
> Why would a modern browser accept unsafe characters in a URL and reject
> properly encoded ones?

I wonder why it;s considered unsafe ? as I've not heard that before.

On 12/09/2022 13:26, Whisky-dave wrote:
> On Saturday, 10 September 2022 at 23:45:30 UTC+1, FromTheRafters wrote:
>> HunterBD laid this down on his screen :
>>> On 10/09/2022 20:12, HunterBD wrote:
>>>> On 10/09/2022 20:03, sobriquet wrote:
>>>>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>>>>> On 10/09/2022 17:03, HunterBD wrote:
>>>>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>>>>> It has been a while since I last posted a drone video, so here is a
>>>>>>>>> great
>>>>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>>>>
>>>>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>>>>
>>>>>>>>
>>>>>>>> I've just watched this again. It's a very special place.
>>>>>>>>
>>>>>>>> Some of us are truly blessed! ❤️
>>>>>>>
>>>>>>> Reposting the link to check again.
>>>>>> The video at the link above now plays perfectly using Safari! :-D
>>>>>>
>>>>>> Does it play for you?
>>>>>
>>>>> https://i.imgur.com/cjploXD.png
>>>>>
>>>>> I've noticed this before.. can be fixed though:
>>>>>
>>>>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>>>>
>>>> THANK YOU :-D
>>>
>>> For Apd - and anyone else who may be curious - in a fresh install of
>>> Firefox the link now works perfectly and gives an excellent presentation,
>>> filling my screen, clearly and crisply. Odd!
>> Does Chrome work now too?
>>
>> I just tested in Edge, both worked fine. I used the URLs from your
>> original post (offering the second video) and just copy/paste to the
>> address bar, that is not by clicking a blue URL. Buffering took some
>> time but it played automatically at almost full screen size.
>>
>> Why would a modern browser accept unsafe characters in a URL and reject
>> properly encoded ones?
>
> I wonder why it's considered unsafe ? as I've not heard that before.

FTR wouldn't have seen your post Dave.

(ACW group added)

It doesn't explain how the movie found its way onto my iCloud Drive though!

David Brooks presented the following explanation :
> On 12/09/2022 13:26, Whisky-dave wrote:
>> On Saturday, 10 September 2022 at 23:45:30 UTC+1, FromTheRafters wrote:
>>> HunterBD laid this down on his screen :
>>>> On 10/09/2022 20:12, HunterBD wrote:
>>>>> On 10/09/2022 20:03, sobriquet wrote:
>>>>>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>>>>>> On 10/09/2022 17:03, HunterBD wrote:
>>>>>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>>>>>> It has been a while since I last posted a drone video, so here is a
>>>>>>>>>> great
>>>>>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>>>>>
>>>>>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I've just watched this again. It's a very special place.
>>>>>>>>>
>>>>>>>>> Some of us are truly blessed! ❤️
>>>>>>>>
>>>>>>>> Reposting the link to check again.
>>>>>>> The video at the link above now plays perfectly using Safari! :-D
>>>>>>>
>>>>>>> Does it play for you?
>>>>>>
>>>>>> https://i.imgur.com/cjploXD.png
>>>>>>
>>>>>> I've noticed this before.. can be fixed though:
>>>>>>
>>>>>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>>>>>
>>>>> THANK YOU :-D
>>>>
>>>> For Apd - and anyone else who may be curious - in a fresh install of
>>>> Firefox the link now works perfectly and gives an excellent presentation,
>>>> filling my screen, clearly and crisply. Odd!
>>> Does Chrome work now too?
>>>
>>> I just tested in Edge, both worked fine. I used the URLs from your
>>> original post (offering the second video) and just copy/paste to the
>>> address bar, that is not by clicking a blue URL. Buffering took some
>>> time but it played automatically at almost full screen size.
>>>
>>> Why would a modern browser accept unsafe characters in a URL and reject
>>> properly encoded ones?
>>
>> I wonder why it's considered unsafe ? as I've not heard that before.

Some characters have meaning to the systems that they pass through,
they cause actions rather than just being interpreted as characters
passing through. The same sort of thing that makes content transfer
encoding necessary for NNTP.

For URI/URL in particular:

https://www.ietf.org/rfc/rfc1738.txt

" Unsafe:

Characters can be unsafe for a number of reasons. The space
character is unsafe because significant spaces may disappear and
insignificant spaces may be introduced when URLs are transcribed or
typeset or subjected to the treatment of word-processing programs.
The characters "<" and ">" are unsafe because they are used as the
delimiters around URLs in free text; the quote mark (""") is used to
delimit URLs in some systems. The character "#" is unsafe and
should
always be encoded because it is used in World Wide Web and in other
systems to delimit a URL from a fragment/anchor identifier that
might
follow it. The character "%" is unsafe because it is used for
encodings of other characters. Other characters are unsafe because
gateways and other transport agents are known to sometimes modify
such characters. These characters are "{", "}", "|", "\", "^", "~",
"[", "]", and "`".

All unsafe characters must always be encoded within a URL. For
example, the character "#" must be encoded within URLs even in
systems that do not normally deal with fragment or anchor
identifiers, so that if the URL is copied into another system that
does use them, it will not be necessary to change the URL encoding."

Also, reserved characters:

Reserved:

Many URL schemes reserve certain characters for a special meaning:
their appearance in the scheme-specific part of the URL has a
designated semantics. If the character corresponding to an octet is
reserved in a scheme, the octet must be encoded. The characters
";",
"/", "?", ":", "@", "=" and "&" are the characters which may be
reserved for special meaning within a scheme. No other characters
may
be reserved within a scheme.

Usually a URL has the same interpretation when an octet is
represented by a character and when it encoded. However, this is not
true for reserved characters: encoding a character reserved for a
particular scheme may change the semantics of a URL.

Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
reserved characters used for their reserved purposes may be used
unencoded within a URL.

On the other hand, characters that are not required to be encoded
(including alphanumerics) may be encoded within the scheme-specific
part of a URL, as long as they are not being used for a reserved
purpose.

> FTR wouldn't have seen your post Dave.
>
> (ACW group added)
>
> It doesn't explain how the movie found its way onto my iCloud Drive though!

On 13/10/2022 16:22, FromTheRafters wrote:
> David Brooks presented the following explanation :
>> On 12/09/2022 13:26, Whisky-dave wrote:
>>> On Saturday, 10 September 2022 at 23:45:30 UTC+1, FromTheRafters wrote:
>>>> HunterBD laid this down on his screen :
>>>>> On 10/09/2022 20:12, HunterBD wrote:
>>>>>> On 10/09/2022 20:03, sobriquet wrote:
>>>>>>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>>>>>>> On 10/09/2022 17:03, HunterBD wrote:
>>>>>>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>>>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>>>>>>> It has been a while since I last posted a drone video, so
>>>>>>>>>>> here is a
>>>>>>>>>>> great
>>>>>>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>>>>>>
>>>>>>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I've just watched this again. It's a very special place.
>>>>>>>>>>
>>>>>>>>>> Some of us are truly blessed! ❤️
>>>>>>>>>
>>>>>>>>> Reposting the link to check again.
>>>>>>>> The video at the link above now plays perfectly using Safari! :-D
>>>>>>>>
>>>>>>>> Does it play for you?
>>>>>>>
>>>>>>> https://i.imgur.com/cjploXD.png
>>>>>>>
>>>>>>> I've noticed this before.. can be fixed though:
>>>>>>>
>>>>>>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>>>>>>
>>>>>> THANK YOU :-D
>>>>>
>>>>> For Apd - and anyone else who may be curious - in a fresh install of
>>>>> Firefox the link now works perfectly and gives an excellent
>>>>> presentation,
>>>>> filling my screen, clearly and crisply. Odd!
>>>> Does Chrome work now too?
>>>>
>>>> I just tested in Edge, both worked fine. I used the URLs from your
>>>> original post (offering the second video) and just copy/paste to the
>>>> address bar, that is not by clicking a blue URL. Buffering took some
>>>> time but it played automatically at almost full screen size.
>>>>
>>>> Why would a modern browser accept unsafe characters in a URL and reject
>>>> properly encoded ones?
>>>
>>>   I wonder why it's considered unsafe ? as I've not heard that before.
>
> Some characters have meaning to the systems that they pass through, they
> cause actions rather than just being interpreted as characters passing
> through. The same sort of thing that makes content transfer encoding
> necessary for NNTP.
>
> For URI/URL in particular:
>
> https://www.ietf.org/rfc/rfc1738.txt
>
> " Unsafe:
>
>   Characters can be unsafe for a number of reasons.  The space
>   character is unsafe because significant spaces may disappear and
>   insignificant spaces may be introduced when URLs are transcribed or
>   typeset or subjected to the treatment of word-processing programs.
>   The characters "<" and ">" are unsafe because they are used as the
>   delimiters around URLs in free text; the quote mark (""") is used to
>   delimit URLs in some systems.  The character "#" is unsafe and should
>   always be encoded because it is used in World Wide Web and in other
>   systems to delimit a URL from a fragment/anchor identifier that might
>   follow it.  The character "%" is unsafe because it is used for
>   encodings of other characters.  Other characters are unsafe because
>   gateways and other transport agents are known to sometimes modify
>   such characters. These characters are "{", "}", "|", "\", "^", "~",
>   "[", "]", and "`".
>
>   All unsafe characters must always be encoded within a URL. For
>   example, the character "#" must be encoded within URLs even in
>   systems that do not normally deal with fragment or anchor
>   identifiers, so that if the URL is copied into another system that
>   does use them, it will not be necessary to change the URL encoding."
>
> Also, reserved characters:
>
> Reserved:
>
>   Many URL schemes reserve certain characters for a special meaning:
>   their appearance in the scheme-specific part of the URL has a
>   designated semantics. If the character corresponding to an octet is
>   reserved in a scheme, the octet must be encoded.  The characters ";",
>   "/", "?", ":", "@", "=" and "&" are the characters which may be
>   reserved for special meaning within a scheme. No other characters may
>   be reserved within a scheme.
>
>   Usually a URL has the same interpretation when an octet is
>   represented by a character and when it encoded. However, this is not
>   true for reserved characters: encoding a character reserved for a
>   particular scheme may change the semantics of a URL.
>
>   Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
>   reserved characters used for their reserved purposes may be used
>   unencoded within a URL.
>
>   On the other hand, characters that are not required to be encoded
>   (including alphanumerics) may be encoded within the scheme-specific
>   part of a URL, as long as they are not being used for a reserved
>   purpose.
>
>> FTR wouldn't have seen your post Dave.
>>
>> (ACW group added)
>>
>> It doesn't explain how the movie found its way onto my iCloud Drive
>> though!

Can YOU explain how the videos of Savageduck found their way onto my
iCloud Drive?

In article <Q8W1L.766423$qD%2.269032@fx08.ams1>, David Brooks
<BDB@not.on.your.life> wrote:

>
> Can YOU explain how the videos of Savageduck found their way onto my
> iCloud Drive?

you put them there.

On 13/10/2022 16:37, Steve Carroll wrote:
> On 2022-10-13, David Brooks <BDB@not.on.your.life> wrote:
>> On 13/10/2022 16:22, FromTheRafters wrote:
>>> David Brooks presented the following explanation :
>>>> On 12/09/2022 13:26, Whisky-dave wrote:
>>>>> On Saturday, 10 September 2022 at 23:45:30 UTC+1, FromTheRafters wrote:
>>>>>> HunterBD laid this down on his screen :
>>>>>>> On 10/09/2022 20:12, HunterBD wrote:
>>>>>>>> On 10/09/2022 20:03, sobriquet wrote:
>>>>>>>>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>>>>>>>>> On 10/09/2022 17:03, HunterBD wrote:
>>>>>>>>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>>>>>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>>>>>>>>> It has been a while since I last posted a drone video, so
>>>>>>>>>>>>> here is a
>>>>>>>>>>>>> great
>>>>>>>>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>>>>>>>>
>>>>>>>>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I've just watched this again. It's a very special place.
>>>>>>>>>>>>
>>>>>>>>>>>> Some of us are truly blessed! ❤️
>>>>>>>>>>>
>>>>>>>>>>> Reposting the link to check again.
>>>>>>>>>> The video at the link above now plays perfectly using Safari! :-D
>>>>>>>>>>
>>>>>>>>>> Does it play for you?
>>>>>>>>>
>>>>>>>>> https://i.imgur.com/cjploXD.png
>>>>>>>>>
>>>>>>>>> I've noticed this before.. can be fixed though:
>>>>>>>>>
>>>>>>>>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>>>>>>>>
>>>>>>>> THANK YOU :-D
>>>>>>>
>>>>>>> For Apd - and anyone else who may be curious - in a fresh install of
>>>>>>> Firefox the link now works perfectly and gives an excellent
>>>>>>> presentation,
>>>>>>> filling my screen, clearly and crisply. Odd!
>>>>>> Does Chrome work now too?
>>>>>>
>>>>>> I just tested in Edge, both worked fine. I used the URLs from your
>>>>>> original post (offering the second video) and just copy/paste to the
>>>>>> address bar, that is not by clicking a blue URL. Buffering took some
>>>>>> time but it played automatically at almost full screen size.
>>>>>>
>>>>>> Why would a modern browser accept unsafe characters in a URL and reject
>>>>>> properly encoded ones?
>>>>>
>>>>>   I wonder why it's considered unsafe ? as I've not heard that before.
>>>
>>> Some characters have meaning to the systems that they pass through, they
>>> cause actions rather than just being interpreted as characters passing
>>> through. The same sort of thing that makes content transfer encoding
>>> necessary for NNTP.
>>>
>>> For URI/URL in particular:
>>>
>>> https://www.ietf.org/rfc/rfc1738.txt
>>>
>>> " Unsafe:
>>>
>>>   Characters can be unsafe for a number of reasons.  The space
>>>   character is unsafe because significant spaces may disappear and
>>>   insignificant spaces may be introduced when URLs are transcribed or
>>>   typeset or subjected to the treatment of word-processing programs.
>>>   The characters "<" and ">" are unsafe because they are used as the
>>>   delimiters around URLs in free text; the quote mark (""") is used to
>>>   delimit URLs in some systems.  The character "#" is unsafe and should
>>>   always be encoded because it is used in World Wide Web and in other
>>>   systems to delimit a URL from a fragment/anchor identifier that might
>>>   follow it.  The character "%" is unsafe because it is used for
>>>   encodings of other characters.  Other characters are unsafe because
>>>   gateways and other transport agents are known to sometimes modify
>>>   such characters. These characters are "{", "}", "|", "\", "^", "~",
>>>   "[", "]", and "`".
>>>
>>>   All unsafe characters must always be encoded within a URL. For
>>>   example, the character "#" must be encoded within URLs even in
>>>   systems that do not normally deal with fragment or anchor
>>>   identifiers, so that if the URL is copied into another system that
>>>   does use them, it will not be necessary to change the URL encoding."
>>>
>>> Also, reserved characters:
>>>
>>> Reserved:
>>>
>>>   Many URL schemes reserve certain characters for a special meaning:
>>>   their appearance in the scheme-specific part of the URL has a
>>>   designated semantics. If the character corresponding to an octet is
>>>   reserved in a scheme, the octet must be encoded.  The characters ";",
>>>   "/", "?", ":", "@", "=" and "&" are the characters which may be
>>>   reserved for special meaning within a scheme. No other characters may
>>>   be reserved within a scheme.
>>>
>>>   Usually a URL has the same interpretation when an octet is
>>>   represented by a character and when it encoded. However, this is not
>>>   true for reserved characters: encoding a character reserved for a
>>>   particular scheme may change the semantics of a URL.
>>>
>>>   Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
>>>   reserved characters used for their reserved purposes may be used
>>>   unencoded within a URL.
>>>
>>>   On the other hand, characters that are not required to be encoded
>>>   (including alphanumerics) may be encoded within the scheme-specific
>>>   part of a URL, as long as they are not being used for a reserved
>>>   purpose.
>>>
>>>> FTR wouldn't have seen your post Dave.
>>>>
>>>> (ACW group added)
>>>>
>>>> It doesn't explain how the movie found its way onto my iCloud Drive
>>>> though!
>>
>> Can YOU explain how the videos of Savageduck found their way onto my
>> iCloud Drive?
>
> Unless he sat next to you the entire time, right up until it happened,
> how could he explain it? Notably, you glossed over an actual
> conversation in order to 'do what you do'. Why?

FTR was replying to WhiskyDave, not to me.

> No, this is not an "attack", it's a logical question based on you 'doing
> what you do' when, in this case, your question is one that can't be
> answered any better than it already has.

I'm just curious. I'm positive that *I* didn't put the Savageduck videos
onto my iCloud Drive. Having wiped my computer clean and reinstalled -
and having opened Savageduck's links once more, they have not appeared
in my iCloud Drive again.

FTR has a vast amount of computer knowledge. Although he's not an Apple
man of long-standing, he may have been able to suggest what may have
occurred.

Please don't remove rec.photo.digital - that's where WhiskyDave reads
and posts. He's a technician in a London University computer laboratory
and knows much about Apple devices.

On 13/10/2022 17:51, Steve Carroll wrote:
> On 2022-10-13, David Brooks <BDB@not.on.your.life> wrote:
>> On 13/10/2022 16:37, Steve Carroll wrote:
>>> On 2022-10-13, David Brooks <BDB@not.on.your.life> wrote:
>>>> On 13/10/2022 16:22, FromTheRafters wrote:
>>>>> David Brooks presented the following explanation :
>>>>>> On 12/09/2022 13:26, Whisky-dave wrote:
>>>>>>> On Saturday, 10 September 2022 at 23:45:30 UTC+1, FromTheRafters wrote:
>>>>>>>> HunterBD laid this down on his screen :
>>>>>>>>> On 10/09/2022 20:12, HunterBD wrote:
>>>>>>>>>> On 10/09/2022 20:03, sobriquet wrote:
>>>>>>>>>>> On Saturday, September 10, 2022 at 6:09:00 PM UTC+2, HunterBD wrote:
>>>>>>>>>>>> On 10/09/2022 17:03, HunterBD wrote:
>>>>>>>>>>>>> On 17/08/2022 11:50, David Brooks wrote:
>>>>>>>>>>>>>> On 05/04/2022 18:27, Savageduck wrote:
>>>>>>>>>>>>>>> It has been a while since I last posted a drone video, so
>>>>>>>>>>>>>>> here is a
>>>>>>>>>>>>>>> great
>>>>>>>>>>>>>>> spring day flying the DJI Air 2S around Morro Bay.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <https://photos.smugmug.com/Air-2S-Work-2022/Air2S-Work-2022/i-k47h46J/0/7ad54298/1920/MB-4-4-2022-1920.mp4>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I've just watched this again. It's a very special place.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Some of us are truly blessed! ❤️
>>>>>>>>>>>>>
>>>>>>>>>>>>> Reposting the link to check again.
>>>>>>>>>>>> The video at the link above now plays perfectly using Safari! :-D
>>>>>>>>>>>>
>>>>>>>>>>>> Does it play for you?
>>>>>>>>>>>
>>>>>>>>>>> https://i.imgur.com/cjploXD.png
>>>>>>>>>>>
>>>>>>>>>>> I've noticed this before.. can be fixed though:
>>>>>>>>>>>
>>>>>>>>>>> https://groups.google.com/g/rec.photo.digital/c/dGqvklBCeQM/m/jeVoYrr-BAAJ
>>>>>>>>>>
>>>>>>>>>> THANK YOU :-D
>>>>>>>>>
>>>>>>>>> For Apd - and anyone else who may be curious - in a fresh install of
>>>>>>>>> Firefox the link now works perfectly and gives an excellent
>>>>>>>>> presentation,
>>>>>>>>> filling my screen, clearly and crisply. Odd!
>>>>>>>> Does Chrome work now too?
>>>>>>>>
>>>>>>>> I just tested in Edge, both worked fine. I used the URLs from your
>>>>>>>> original post (offering the second video) and just copy/paste to the
>>>>>>>> address bar, that is not by clicking a blue URL. Buffering took some
>>>>>>>> time but it played automatically at almost full screen size.
>>>>>>>>
>>>>>>>> Why would a modern browser accept unsafe characters in a URL and reject
>>>>>>>> properly encoded ones?
>>>>>>>
>>>>>>>   I wonder why it's considered unsafe ? as I've not heard that before.
>>>>>
>>>>> Some characters have meaning to the systems that they pass through, they
>>>>> cause actions rather than just being interpreted as characters passing
>>>>> through. The same sort of thing that makes content transfer encoding
>>>>> necessary for NNTP.
>>>>>
>>>>> For URI/URL in particular:
>>>>>
>>>>> https://www.ietf.org/rfc/rfc1738.txt
>>>>>
>>>>> " Unsafe:
>>>>>
>>>>>   Characters can be unsafe for a number of reasons.  The space
>>>>>   character is unsafe because significant spaces may disappear and
>>>>>   insignificant spaces may be introduced when URLs are transcribed or
>>>>>   typeset or subjected to the treatment of word-processing programs.
>>>>>   The characters "<" and ">" are unsafe because they are used as the
>>>>>   delimiters around URLs in free text; the quote mark (""") is used to
>>>>>   delimit URLs in some systems.  The character "#" is unsafe and should
>>>>>   always be encoded because it is used in World Wide Web and in other
>>>>>   systems to delimit a URL from a fragment/anchor identifier that might
>>>>>   follow it.  The character "%" is unsafe because it is used for
>>>>>   encodings of other characters.  Other characters are unsafe because
>>>>>   gateways and other transport agents are known to sometimes modify
>>>>>   such characters. These characters are "{", "}", "|", "\", "^", "~",
>>>>>   "[", "]", and "`".
>>>>>
>>>>>   All unsafe characters must always be encoded within a URL. For
>>>>>   example, the character "#" must be encoded within URLs even in
>>>>>   systems that do not normally deal with fragment or anchor
>>>>>   identifiers, so that if the URL is copied into another system that
>>>>>   does use them, it will not be necessary to change the URL encoding."
>>>>>
>>>>> Also, reserved characters:
>>>>>
>>>>> Reserved:
>>>>>
>>>>>   Many URL schemes reserve certain characters for a special meaning:
>>>>>   their appearance in the scheme-specific part of the URL has a
>>>>>   designated semantics. If the character corresponding to an octet is
>>>>>   reserved in a scheme, the octet must be encoded.  The characters ";",
>>>>>   "/", "?", ":", "@", "=" and "&" are the characters which may be
>>>>>   reserved for special meaning within a scheme. No other characters may
>>>>>   be reserved within a scheme.
>>>>>
>>>>>   Usually a URL has the same interpretation when an octet is
>>>>>   represented by a character and when it encoded. However, this is not
>>>>>   true for reserved characters: encoding a character reserved for a
>>>>>   particular scheme may change the semantics of a URL.
>>>>>
>>>>>   Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
>>>>>   reserved characters used for their reserved purposes may be used
>>>>>   unencoded within a URL.
>>>>>
>>>>>   On the other hand, characters that are not required to be encoded
>>>>>   (including alphanumerics) may be encoded within the scheme-specific
>>>>>   part of a URL, as long as they are not being used for a reserved
>>>>>   purpose.
>>>>>
>>>>>> FTR wouldn't have seen your post Dave.
>>>>>>
>>>>>> (ACW group added)
>>>>>>
>>>>>> It doesn't explain how the movie found its way onto my iCloud Drive
>>>>>> though!
>>>>
>>>> Can YOU explain how the videos of Savageduck found their way onto my
>>>> iCloud Drive?
>>>
>>> Unless he sat next to you the entire time, right up until it happened,
>>> how could he explain it? Notably, you glossed over an actual
>>> conversation in order to 'do what you do'. Why?
>>
>> FTR was replying to WhiskyDave, not to me.
>
> I saw... I also saw you ignore public conversation in lieu of your
> paranoia... AGAIN.
>
>>> No, this is not an "attack", it's a logical question based on you 'doing
>>> what you do' when, in this case, your question is one that can't be
>>> answered any better than it already has.
>>
>> I'm just curious. I'm positive that *I* didn't put the Savageduck videos
>> onto my iCloud Drive.
>
> It's been explained how that would take place.
>
>> Having wiped my computer clean and reinstalled -
>> and having opened Savageduck's links once more, they have not appeared
>> in my iCloud Drive again.
>
> What are you suggesting, that you, and you alone, have an iCloud setting
> bug? Contact Apple if you believe that's so.
>
>> FTR has a vast amount of computer knowledge.
>
> Didn't he say he wasn't 'up' on the 'iCloud thing'? In any event, beyond
> what has already been explained, unless he sat with you (and saw you
> inadvertently do it) he's not going to be able to help you.
>
>> Although he's not an Apple man of long-standing, he may have been able
>> to suggest what may have occurred.
>>
>> Please don't remove rec.photo.digital - that's where WhiskyDave reads
>> and posts. He's a technician in a London University computer laboratory
>> and knows much about Apple devices.
>
> If it contains you 'doing what you do' I'll confine it to ACW.
>
> Why don't you just ask WD directly? But then, even after you get
> essentially the same response you've already been given you'll ignore it
> because it's not conducive to you 'doing what you do' <shrug>.

On 13/10/2022 17:17, nospam wrote:
> In article <Q8W1L.766423$qD%2.269032@fx08.ams1>, David Brooks
> <BDB@not.on.your.life> wrote:
>
>>
>> Can YOU explain how the videos of Savageduck found their way onto my
>> iCloud Drive?
>
> you put them there.

*HOW* do you think I did that?

Can YOU put Savageduck's videos onto YOUR iCloud Drive?

If so, please explain how that is achievable.