Hi All...

hey John..
https://brorabbit.g0x.ru/pic/65bc6418.jpg


--
/|ug
https://t.me/aabolins

--- Want fido for iOS/MacOS/Android/Win/Linux? https://shrtco.de/tpJ9yV
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Yeah. Deleted from his database. Doesn't bother me much

--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

John Dovey Firecat wrote to All <=-

Yeah. Deleted from his database. Doesn't bother me much

What was deleted? No context given, nothing quoted. Nobody knows what
you're referring to. At least it doesn't bother you though.



... Can you tell me how to get, how to get to Sesame Street?
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

John Dovey Firecat wrote to All <=-

Yeah. Deleted from his database. Doesn't bother me much

What was deleted? No context given, nothing quoted. Nobody knows what you're referring to. At least it doesn't bother you though.
... Can you tell me how to get, how to get to Sesame Street?
=== MultiMail/Linux v0.52

Interestingly, I replied to a message from August on Telegram and he knew exactly what I was referring to.

--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

John Dovey Firecat wrote to All <=-

Yeah. Deleted from his database. Doesn't bother me much

What was deleted? No context given, nothing quoted. Nobody knows what you're referring to. At least it doesn't bother you though.
... Can you tell me how to get, how to get to Sesame Street?
=== MultiMail/Linux v0.52

If you reply via Telegram to a message that has an image attached, on the Telegram group it looks fine, but on the Fido side the reply is posted as a message to "All" without the image URL and no quoted text.

The @REPLY kludge is ok, however, so if your editor supports thread linking you can find the replied-to message.

Stas said he would fix this, but it seems he hasn't been able to do it yet.

When replying to normal text-only messages tg_BBS does a good work.

--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

If you reply via Telegram to a message that has an image attached, on the Telegram group it looks fine, but on the Fido side the reply is posted as a message to "All" without the image URL and no quoted text.
The @REPLY kludge is ok, however, so if your editor supports thread linking you can find the replied-to message.
Stas said he would fix this, but it seems he hasn't been able to do it yet.
When replying to normal text-only messages tg_BBS does a good work.

Thanks Carlos. I simply don't have the desire or energy to argue with people about the effectiveness of software as compensation for poor design. Stas has done a great job. It works pretty well as it is as long as the software you're using isn't completely braindead

--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Yeah. Deleted from his database. Doesn't bother me much

What was deleted? No context given, nothing quoted. Nobody knows what you're referring to. At least it doesn't bother you though.

I figured it out because I saw it posted in the ELIST echo. The ELIST is
about to delist this echo.

Mike


* SLMR 2.1a * Sheesh! You start havin' fun, and they send the lawyers!
--- SBBSecho 3.14-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

John Dovey Firecat wrote to Dan Clough <=-

Yeah. Deleted from his database. Doesn't bother me much

What was deleted? No context given, nothing quoted. Nobody knows what you're referring to. At least it doesn't bother you though.

Interestingly, I replied to a message from August on Telegram and
he knew exactly what I was referring to.

Yeah well, I'm reading this on FidoNet. Not some garbage interface "app"
that doesn't work properly. There was no context or quoting in what you posted.



... Error reading REALITY.SYS - Solar System halted.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Carlos Navarro wrote to Dan Clough <=-

Yeah. Deleted from his database. Doesn't bother me much

What was deleted? No context given, nothing quoted. Nobody knows what you're referring to. At least it doesn't bother you though.

If you reply via Telegram to a message that has an image
attached, on the Telegram group it looks fine, but on the Fido
side the reply is posted as a message to "All" without the image
URL and no quoted text.

Yes. What's the percentage of people reading it on Telegram vs FidoNet?
A pretty small number, I'd wager.

The @REPLY kludge is ok, however, so if your editor supports
thread linking you can find the replied-to message.

Even that kludge doesn't help if you're reading FidoNet messages with an offline mail reader.

Stas said he would fix this, but it seems he hasn't been able to
do it yet.

When replying to normal text-only messages tg_BBS does a good
work.

That's debate-able too. It's pretty much a garbage/broken interface, from what I can see.



... Chuck Norris can divide by zero.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Mike Powell wrote to DAN CLOUGH <=-

Yeah. Deleted from his database. Doesn't bother me much

What was deleted? No context given, nothing quoted. Nobody knows what you're referring to. At least it doesn't bother you though.

I figured it out because I saw it posted in the ELIST echo. The
ELIST is about to delist this echo.

Thanks. I hope it does get deleted.

Reminds me of trying to read and follow threads on Usenet, in olden days. People that don't know how to quote or properly use the interface.



... If it's not on fire, it's a software problem.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

John Dovey Firecat wrote to Carlos Navarro <=-

If you reply via Telegram to a message that has an image attached, on the

T

elegram group it looks fine, but on the Fido side the reply is
posted as a message to "All" without the image URL and no quoted
text.

The @REPLY kludge is ok, however, so if your editor supports thread

linking

you can find the replied-to message.

Stas said he would fix this, but it seems he hasn't been able to do it

yet.

When replying to normal text-only messages tg_BBS does a good work.

Thanks Carlos. I simply don't have the desire or energy to argue
with people about the effectiveness of software as compensation
for poor design. Stas has done a great job. It works pretty well
as it is as long as the software you're using isn't completely
braindead

The braindead software in this discussion is the Telegram garbage.
Regular methods of writing/reading to/from FidoNet echos work just fine,
as they always have.

You remind me of an "eternal-September" type of Usenet poster. Pfffftttt.



... This MSG written by pouring warm tea on an Ouija board.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

John Dovey Firecat wrote to Carlos Navarro <=-

If you reply via Telegram to a message that has an image attached, on the

T

elegram group it looks fine, but on the Fido side the reply is
posted as a message to "All" without the image URL and no quoted
text.

The @REPLY kludge is ok, however, so if your editor supports thread

linking

you can find the replied-to message.

Stas said he would fix this, but it seems he hasn't been able to do it

yet.

When replying to normal text-only messages tg_BBS does a good work.

Thanks Carlos. I simply don't have the desire or energy to argue
with people about the effectiveness of software as compensation
for poor design. Stas has done a great job. It works pretty well
as it is as long as the software you're using isn't completely
braindead

The braindead software in this discussion is the Telegram garbage. Regular methods of writing/reading to/from FidoNet echos work just fine, as they always have.
You remind me of an "eternal-September" type of Usenet poster. Pfffftttt. ... This MSG written by pouring warm tea on an Ouija board.
=== MultiMail/Linux v0.52

And you remind me why Fido is essentially dead.

--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Hello Dan Clough!

Quoting is not always necessary.

--
../|ug

--- OpenXP 5.0.58
* Origin: (2:221/1.58)

Hello Dan Clough!

** On Friday 02.02.24 - 21:53, Dan Clough wrote to John Dovey Firecat:

<something not worth quoting>

I can follow the thread very easily.. no quoting required.
REPLY id does its job in readers that support it.

--
../|ug

--- OpenXP 5.0.58
* Origin: (2:221/1.58)

John Dovey Firecat wrote to Dan Clough <=-

John Dovey Firecat wrote to Carlos Navarro <=-

If you reply via Telegram to a message that has an image attached, on the

T

elegram group it looks fine, but on the Fido side the reply is
posted as a message to "All" without the image URL and no quoted
text.

The @REPLY kludge is ok, however, so if your editor supports thread

linking

you can find the replied-to message.

Stas said he would fix this, but it seems he hasn't been able to do it

yet.

When replying to normal text-only messages tg_BBS does a good work.

Thanks Carlos. I simply don't have the desire or energy to argue
with people about the effectiveness of software as compensation
for poor design. Stas has done a great job. It works pretty well
as it is as long as the software you're using isn't completely
braindead

The braindead software in this discussion is the Telegram garbage.
Regular methods of writing/reading to/from FidoNet echos work just fine, as they always have.
You remind me of an "eternal-September" type of Usenet poster. Pfffftttt. ... This MSG written by pouring warm tea on an Ouija board.
=== MultiMail/Linux v0.52

And you remind me why Fido is essentially dead.

Well, see there above? It *IS* possible (apparently) for the braindead
"app" to quote context. I guess it must just be braindead *people* who *choose* to not quote. Right? I mean, there it is, right there above, although quite sloppy/messy looking.

As for Fido, yes, it's *popularity / usage* has declined, which is not unexpected with the changes over the years (i.e. - Internet access). That wasn't the point, though. The *mechanisms* for exchanging messages
continues to work just fine, unlike this kludge/garbage "app" junk that
you think is an enhancement or something. It isn't. It's crap.



... Do you know where you are?
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

John Dovey Firecat wrote to Dan Clough <=-

T
linking
yet.
The braindead software in this discussion is the Telegram garbage.
Regular methods of writing/reading to/from FidoNet echos work just fine,
as they always have.
You remind me of an "eternal-September" type of Usenet poster. Pfffftttt.
... This MSG written by pouring warm tea on an Ouija board.
=== MultiMail/Linux v0.52

And you remind me why Fido is essentially dead.

Well, see there above? It *IS* possible (apparently) for the braindead "app" to quote context. I guess it must just be braindead *people* who *choose* to not quote. Right? I mean, there it is, right there above, although quite sloppy/messy looking.
As for Fido, yes, it's *popularity / usage* has declined, which is not unexpected with the changes over the years (i.e. - Internet access). That
wasn't the point, though. The *mechanisms* for exchanging messages continues to work just fine, unlike this kludge/garbage "app" junk that you think is an enhancement or something. It isn't. It's crap.
... Do you know where you are?
=== MultiMail/Linux v0.52

Clearly you can't read with comprehension.

--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)