Heads Up! 4/25/16

[Byker]

[No Name]

Would you be so kind to post directly in normal format (eg JPG, MP4)
It will not take more space or bandwith.

[Byker]

wrote in message ...
>
> Would you be so kind to post directly in normal format (eg JPG, MP4)

Those were MP4s, along with one JPG.

[Savageduck[_3_]]

On Apr 26, 2016, Byker wrote
(in >):

> wrote in message ...
> >
> > Would you be so kind to post directly in normal format (eg JPG, MP4)
>
> Those were MP4s, along with one JPG.

I think the big problem is the extra step one has to take to view your posts
when you use non-standard file label punctuation.

Files labeled such as the following are not easily decoded as JPG or MP4:
f4852f56ce93cccaecfe97641974921ca2856920_144p (1).3gp, 1.3 MB
or
a 10 extremely low pass.mp4, 1 MB
or
F1 Mirage Ultra Low High Speed Fly By.mp4, 1.5 MB

In those cases of the xxx.mp4 and the xxx.3gp the placement of a “,�
without a separating space corrupts the file name.
Either omit the “,� or insert a space after the file type.

Otherwise always, interesting and entertaining stuff.

--

Regards,
Savageduck

[Charles Lindbergh[_2_]]

On Tue, 26 Apr 2016 14:07:04 -0700, Savageduck > wrote:

>On Apr 26, 2016, Byker wrote
>(in >):
>
>> wrote in message ...
>> >
>> > Would you be so kind to post directly in normal format (eg JPG, MP4)
>>
>> Those were MP4s, along with one JPG.
>
>I think the big problem is the extra step one has to take to view your posts
>when you use non-standard file label punctuation.
>
>Files labeled such as the following are not easily decoded as JPG or MP4:
>f4852f56ce93cccaecfe97641974921ca2856920_144p (1).3gp, 1.3 MB
>or
>a 10 extremely low pass.mp4, 1 MB
>or
>F1 Mirage Ultra Low High Speed Fly By.mp4, 1.5 MB
>
>In those cases of the xxx.mp4 and the xxx.3gp the placement of a “,”
>without a separating space corrupts the file name.
>Either omit the “,” or insert a space after the file type.
>
>Otherwise always, interesting and entertaining stuff.

His file names do not include the comma. This must be a function of your news reader, Hogwasher, or the Mac
OS itself.

[Savageduck[_3_]]

On 2016-04-27 00:06:24 +0000, Charles Lindbergh > said:

> On Tue, 26 Apr 2016 14:07:04 -0700, Savageduck
> > wrote:
>
>> On Apr 26, 2016, Byker wrote
>> (in >):
>>
>>> wrote in message ...
>>>>
>>>> Would you be so kind to post directly in normal format (eg JPG, MP4)
>>>
>>> Those were MP4s, along with one JPG.
>>
>> I think the big problem is the extra step one has to take to view your posts
>> when you use non-standard file label punctuation.
>>
>> Files labeled such as the following are not easily decoded as JPG or MP4:
>> f4852f56ce93cccaecfe97641974921ca2856920_144p (1).3gp, 1.3 MB
>> or
>> a 10 extremely low pass.mp4, 1 MB
>> or
>> F1 Mirage Ultra Low High Speed Fly By.mp4, 1.5 MB
>>
>> In those cases of the xxx.mp4 and the xxx.3gp the placement of a “,”
>> without a separating space corrupts the file name.
>> Either omit the “,” or insert a space after the file type.
>>
>> Otherwise always, interesting and entertaining stuff.
>
> His file names do not include the comma. This must be a function of
> your news reader, Hogwasher, or the Mac
> OS itself.

I have the same issue with Unison and Hogwasher when it comes to many
of Byker's files. In the posts the comma is present and to render the
file it has to be downloaded.
Other binaries such as those posted by Joseph Testagrose, and posted by
folks in alt.binaries.photos.original don't exhibit the same behaviour.
I ca oly conclude that there is something in the method Byker is using
when it comes to posting his image and video files with MS Windows Live
Mail, which is not a dedicted Usenet client.

I am pretty sure that you have no trouble viewing images I post with
either Unison or Hogwasher.



--
Regards,

Savageduck

[Byker]

"Savageduck" wrote in message
news:201604261754244598-savageduck1@REMOVESPAMmecom...
>
> I ca oly conclude that there is something in the method Byker is using
> when it comes to posting his image and video files with MS Windows Live
> Mail

Yup

> which is not a dedicted Usenet client.

"Dedicated" Usenet client? Never heard of it

[Savageduck[_3_]]

On 2016-04-27 02:19:14 +0000, "Byker" > said:

> "Savageduck" wrote in message
> news:201604261754244598-savageduck1@REMOVESPAMmecom...
>>
>> I ca oly conclude that there is something in the method Byker is using
>> when it comes to posting his image and video files with MS Windows Live
>> Mail
>
> Yup
>
>> which is not a dedicated Usenet client.
>
> "Dedicated" Usenet client? Never heard of it

Usenet clients, like email clients are apps/software for accessing
Usenet or email (sometimes both). Some are better than others.

Take a look, there are several dedicated Usenet clients available for
Windows users, OSX users and Linix users. They are much better suited
for dealing with Newsgroups and associated binaries than mail apps,
such as Live Mail and Thunderbird roped into Newsgroup use. Take a look
at Forte Agent, Unison, Hogwasher, slrn, Giganews has Mimo, and there
are many others, some free some not.

Since you are a Windows user, I suggest you check out Forte Agent.
<http://www.forteinc.com/main/homepage.php>

I use Giganews, but I am not a fan of Mimo, but it is a dedicted Usenet client.
<http://www.mimousenet.com>

--
Regards,

Savageduck

[Charles Lindbergh[_2_]]

On Tue, 26 Apr 2016 17:54:24 -0700, Savageduck > wrote:

>I ca oly conclude that there is something in the method Byker is using
>when it comes to posting his image and video files with MS Windows Live
>Mail, which is not a dedicted Usenet client.

When I download bykers video binaries using Forte Agent, the file names do not contain the comma after the
file extension and they play normally. When I download his still image files, they are displayed in a fashion
identical to Testagrose's postings.

The difference between the two is; byker is posting using base64 encoding and Testagrose is using uuencode.