| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 27 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 46:01:08 |
| Calls: | 632 |
| Calls today: | 3 |
| Files: | 1,187 |
| D/L today: |
24 files (29,813K bytes) |
| Messages: | 176,480 |
Hey!=20I=00=00=00m=20trying=20to=20use=20tin=20for=20reading=20new= >s.=20I=00=00=00ve=20successfully=20authenticated=20with=20my=20pro= >vider=20and=20can=20retrieve=20article=20headers.=20However,=20whe= >never=20I=20try=20to=20open=20an=20article,=20tin=20says=20"Articl= >e=20unavailable."=20The=20same=20articles=20open=20just=20fine=20i= >n=20other=20readers.
Has=20anyone=20else=20faced=20this=20issue?
On 07.09.2025 08:44 Uhr plaintexter wrote:You're right, it works with Paganini (I didn't know it existed - thanks for pointing it out!). So I suspect it's a provider issue.
'm trying to use tin for reading news. I've successfully
authenticated with my provider and can retrieve article headers.
However, whenever I try to open an article, tin says "Article
unavailable." The same articles open just fine in other readers.
Is this the same article number?
Does this happen on other servers too, e.g paganini.bofh.team?
plaintexter <plain@texter.invalid> wrote:I accidentally used a non-ASCII character, realized it right away, and posted a follow-up. Still, no need for f-words toward someone new to Usenet. A bit of patience goes a long way.
That's entirely plain text, all 7 bit ASCII. You managed to encode From, Subject, and the article itself.
Nice fucking troll.