Only if there are humans still controlling them. On their
own they lack the desire to become overlords of anything.
What for?
Someone proposed that if so instructed to solve the global
warming crisis, AI could easily determine that humans are
responsible and thus the solution would be to eliminate
all humans.
Perhaps we should move this topic to CHAT or COFFEE_KLATSCH or
ANYTHING_GOES
Maurice keeps this one active, and the testing is fun - and away
from the icky people. :)
Heh, heh. I couldn't have said it better myself. Originally I was
just looking for a place where I could post the results of bashist
routines not unlike what we were doing with trans.
Lately has been a bit of a chore due to all the probing and I hope
to have that all done with by next week sometime. The top of th
TODO list is the quoting thingy we were talking about using fold and
sed.
I really like the Anglo-Saxon quote below. For me it says it all.
... þa þurfon swiþe lytles, þe maran ne willniaþ þonne genoges.
Perhaps we should move this topic to CHAT or COFFEE_KLATSCH or
ANYTHING_GOES
Nah. This entire time we were assuming these AI robots were powered by Linux, so it's still on topic!
Everyone's so keen to move messages places where there is
absolutely no conversation going on. I'd rather dwindle
down the list of echos I carry and contribute to the ones
that there's actual conversation in.
Just trying to encourage utilizing other echos as a means to
invite other people to join in if the topic is of interest.
THAT is the way to build "ones that there's actual conversation
in" too. ;)
Hopefully you can get a clean bill of health until they (aliens,
right?) want to probe you again. :)
... þa þurfon swiþe lytles, þe maran ne willniaþ þonne genoges.
Are you still getting these from the same place?
I think this is the last of e probing and if it shows negative to
internal bleeding then the aliens are going to have to switch their
tactics since there has to be a cause. Personally I am thinking it
is an over active liver and not internal bleeding but we'll soon
enough find out. So far all indications are my internal organs,
including liver, show no sign of damage.
<Esc>:read !wc -l < ~/etc/taglines.list 234
Definetly more than 50 now. If you'd like a copy I could forward it
to you. There isn't a copyright on any of them.
Just trying to encourage utilizing other echos as a means to
invite other people to join in if the topic is of interest.
If the topic is of interest to anyone, they can definitely
chime in right here, too!
Unless you're referring to spam/cross posting our
conversation to multiple echos to see if anyone bites?
Though, I'm not really interested in chasing our not-so-
very imporatant conversation around Fidonet, either.
THAT is the way to build "ones that there's actual
conversation in" too. ;)
If we did that, this echo would end up empty, then. I
don't think it matters where we have our conversation. If
people want in, they'll join no matter where the
conversation is taking place.
At the rate of decline of this network, we should be happy
we have any conversation at all, to be honest. At this
point, there's more robot postings in Fidonet than actual
conversation. :)
That's if the topic is linux, but you know that I am referring
to other topics (ie, off-topic) that might crop up here.
It's not chasing at all. It's just going to the proper room to
be on topic.
If you're ok with off-topic messages in any echo, what's the
point in having named echos? The echos in FTN may as well be
just a number. Echos have a name for a reason - to indicate a
topic. And if the topic veers, there are other appropriate
echos to take it there.
At this rate we should encourage good stewardship of echos and
support the available ones too, unlike what has happend to
newsgroups filled with totally unrelated things in their areas.
Sadly, yes.. FTN/echos is not necessarily a growing tech. But
we shouldn't allow it to become like the garbage bin that many
newsgroups have become.
FUTURE4FIDO echo is a fine place to have this conversation.
The echo is one of several that participates in the Telegram
BBS project which facilites bridging smartphone users to FTN
users. I believe the Telegram BBS is written entirely in perl.
That's if the topic is linux, but you know that I am
referring to other topics (ie, off-topic) that might crop
up here.
The thing is, most of the topic is regarding Linux and/or
commands we can use in Linux. If a few messages veers a
teeny tiny bit, or for a thread to all of a sudden change
to health updates, or a holiday, or whatever, I'm not all
for up and moving the discussion elsewhere, so long as we
come back to the original topic - which we have been
doing.
... þa þurfon swiþe lytles, þe maran ne willniaþ þonne genoges.
Originally yes but over the years have added to the list. However not
all are Anglo-Saxon although the majority are. They all have utf-8 characters since that was the main reason for the tagline list
although the Anglo-Saxon ones were to ensure "English only" text for
those anal moderators. ;-)
here is a test with nano and the "set fill 72" option set in
.nanorc.
the spaces at the end of the lines are included (to keep flowed
text in tact), and in a quote this may not be wanted.
if it wraps the quoted text nicely then we may be on to something
here!
And then again maybe it is given it makes it far easier to reconstruct
the original posted text, including lines, paragraphs, and the such.
It looks to be a keeper.
It looks that way to me. I'll definetly get back to you on this once
I get a chance to compare outputs between nano and a properly scripted (bash) fold/sed quotes. So far I like what I see in this post ->
"@MSGID: 233.tuxpower@1:154/700 2bb4e7ca".
Great news. Thanks for the confirmation. It's definitely nice to get
back to nano. I mess up far too many times while in a vim session,
as I'm just not used to it at all.
Great news. Thanks for the confirmation. It's definitely nice to get
back to nano. I mess up far too many times while in a vim session,
as I'm just not used to it at all.
For example, in nano, try "set fill 69" in conjunction with "set justifytrim" which removes the whitespace at the end of the lines.
For example, in nano, try "set fill 69" in conjunction with "set justifytrim" which removes the whitespace at the end of the lines.
Even though they look the same they aren't. Can you tell which is which?
BTW I can't find "set justifytrim" so instead I enabled "set trimblanks" which looks to be the same end result.
<Esc>:read !nano --version
GNU nano, version 8.2
(C) 2024 the Free Software Foundation and various contributors
Compiled options: --enable-utf8
Was the second one with fold or just "set trimblanks" disabled?
Which one do you think is doing it incorrectly?
It was 'fold -s -w 69'. The first is nano with "set trimblanks" and
"set fill 69".
Neither, they are true to what they're called up to do. Offhand I
suspect that fold is more DOSsie and it is usually one character shy
of how others define the length of a string. For example FTN
standards list the subject field at 72 characters when it is really
71. The 72nd character is \0, which is ye' olde string delimiter and
in the case of MSGs it is a field delimiter. Offhand I'd go with
fold's specifiers and have .nanorc "set fill 68" which is one less
than fold but produces the same end result as 'fold -s -w 69'.
Ok, I suppose if nothing is wrong, then we carry on like it never happened!
It's more a question of what works than what is right or wrong.
Setting the width so that a quote prefix can be added will assure us
that older DOS-think abandonware doesn't run over it's 79 character
limit for displayed line lengths makes this quoting method superior,
with or without spaces an the end. Leaving them in will make this a lossless method of quoting.
who knows what the abandonware will do with it.
What were they thinking?
That is why we're giving it at least 7 characters to play with. I
have been known to wrap entire messages to 72 characters just to take
care of their obvious handicap. Them were the good ol' days.
Strong like bull, smart like tractor?
As far as I know, quoting has never been covered in ftn standards.
The tradition has become to put the initials of the quotee in the
quote prefix along with the '>' character. However I think just the
' character is more universal and makes things easier, especiallywhen using vim or nano as the MSG editor of choice.
As far as I know, quoting has never been covered in ftn standards.
Not a standard, but there was a proposal: http://ftsc.org/docs/fsc-0032.001
"Good ol' days?" I don't think much has changed.
The '> ' prefix is definitely more universal, not only for FTN,
but newsgroups and email as well.
| Sysop: | Sarah |
|---|---|
| Location: | Portland, Oregon |
| Users: | 19 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 53:43:47 |
| Calls: | 126 |
| Calls today: | 126 |
| Files: | 84,009 |
| U/L today: |
5 files (318K bytes) |
| D/L today: |
33 files (8,385K bytes) |
| Messages: | 38,259 |
| Posted today: | 25 |