Patricia Ferreira <pferreira@example.com> writes:

Let me show you some basic computer skills. (Lol.) When you find an interesting web page, print it to a file. (The kids these days also say ``save it to a PDF''.)

Or first save it at archive.org, add a pointer to that copy wherever you
refer to it and only then start thinking about converted variants.

"The internet never forgets" has been proven wrong far too many times
already.

Then attach it here.

\o/ Let there be (NNTP-)life! \o/

(If the community won't punch you in the face for that.)

I'm reading more than only Usenet and other news servers via GNUS and
that includes mailing-lists and RSS/Atom stuff from code changes
(GitHub, Fossil, CVS, ...) to full articles in HTML with images
(Hackaday, Universetoday, ...).

Usenet is just one set of rules atop NNTP and other news servers may
have different rules. A place to experiment with distributing other
markup over NNTP would be nice to have. Currently I limit my
experiments needing more than UTF-8 to *.test groups.

Seriously, I think every NNTP-based community should also count with a
file bin and an image bin.

Putting stuff into your (pubnix's) HTTP, archive.org-ing it and using
those links often is ™good enough™. I used that for lots of images in forums that don't have own storage for pics and instead use strange
storage services that may not even exist any more in some years.

I don't think NNTP needs to display images like the web. I think it's perfectly fine---in fact preferable---to view images sort of
separately from the reading.

I'd prefer them inline and only be used where really necessary, but
once that door is open, it will be abused.

It's not clear to me the best way img and file bins with NNTP. I'm interested in hearing ideas.

First we need exact rules what which NNTP provider and especially ~news
allows. Then we can discuss why that's ™good enough™ or what we would
want to be different.

In Usenet you still find 7-bit extremists that would, if they could,
allow nothing else. Here I've never been yelled at for UTF-8. Playing
with braille-8 as pseudo-graphics somewhere else, someone complained
that this may confuse users of braille readers. But I think avoiding
that would disqualify ASCII art in posts too, so I did not completely
stop playing with that. IMO it should be ok to use that wherever UTF-8
is allowed.
--
⠀⠀⠀⠀⠀⠀⠀( Play pew-pew? )
⠀⠀⠀⠀⠀⠀⠀/
⠀⠀⢀⡧⣤⢼⡀
⠀⠀⠏⢟⠛⡻⠹
--- Synchronet 3.19a-Linux NewsLink 1.113