I have updated the last iteration of my beginner's setup guide for slrn
and slrnpull just today:
https://help.ubuntu.com/community/slrn
This little document started on my own personal web space,
lived briefly on the Ubuntu Forums and has now had its final
polish on the Ubuntu Community Wiki. That covers a time period
of about 20 years I think; perhaps it should be a little better
by now :).
Although I am quite happy with it in its current state I open
it to the slrn community to have a look and make any
suggestions for small improvements. Given the current state of
Usenet I will not really add any major changes. I am happy that
it all hangs together and has been comprehensively tested on
the latest release of Ubuntu.
Let me know...
I have updated the last iteration of my beginner's setup guide for slrn
and slrnpull just today:
https://help.ubuntu.com/community/slrn
This little document started on my own personal web space, lived briefly
on the Ubuntu Forums and has now had its final polish on the Ubuntu
Community Wiki. That covers a time period of about 20 years I think;
perhaps it should be a little better by now :).
Although I am quite happy with it in its current state I open it to the
slrn community to have a look and make any suggestions for small improvements. Given the current state of Usenet I will not really add
any major changes. I am happy that it all hangs together and has been comprehensively tested on the latest release of Ubuntu.
I have updated the last iteration of my beginner's setup guide for slrn
and slrnpull just today:
https://help.ubuntu.com/community/slrn
This little document started on my own personal web space, lived briefly
on the Ubuntu Forums and has now had its final polish on the Ubuntu
Community Wiki. That covers a time period of about 20 years I think;
perhaps it should be a little better by now :).
Although I am quite happy with it in its current state I open it to the
slrn community to have a look and make any suggestions for small improvements. Given the current state of Usenet I will not really add
any major changes. I am happy that it all hangs together and has been comprehensively tested on the latest release of Ubuntu.
Let me know...
Andrew
Eternal-september and a paid Usenet provider I use has no need for
FQDNs.
meff wrote:
Eternal-september and a paid Usenet provider I use has no need for
FQDNs.
we all might have use for FQDNs
On 2022-05-25, issdr <p_u_n_k_i_n_d@yahoo.it> wrote:
meff wrote:
Eternal-september and a paid Usenet provider I use has no need for
FQDNs.
we all might have use for FQDNs
An IPv6 address is good enough for everyone! 🙃
It might be worth talking about how you can configure slrn to omit
Message IDs if your newsserver adds IDs for you on article
injection. This removes the need for a user to have an
FQDN. Eternal-september and a paid Usenet provider I use has no need
for FQDNs.
meff <email@example.com> wrote:
It might be worth talking about how you can configure slrn to omit
Message IDs if your newsserver adds IDs for you on article
injection. This removes the need for a user to have an
FQDN. Eternal-september and a paid Usenet provider I use has no need
for FQDNs.
At least for e-s, it has no *need*, but it could have some uses.
For example, some of us filter replies to our messages, which requires keeping our FQDN in the original Message-ID to then look for it in the References. Thankfully, e-s doesn't overwrite the message-ID if your
client happens to generate one.
Phil
FQDNs almost all require some, albeit often trivial (in developed
countries), amount of money.
Right, there are uses, I just mean in an introductory wiki article it
might be nice to offer users an easy path to reading/writing articles
without having to own an FQDN. Usenet is a bit "odd" these days
anyway, and requiring an FQDN is an additional barrier, and a paid one
at that. I for one remember, many years ago now, being a kid and not
being able to spend money on the internet. FQDNs almost all require
some, albeit often trivial (in developed countries), amount of money.
[...]
https://help.ubuntu.com/community/slrn
I don't believe you have to 'own' anything to provide a FQDN to slrn
for messsage-id generation. I do not publish records for my internal
zones in the public views on my resolvers and I post just fine.
---
imladris@19:22:00 ~ >dig +short imladris.colo.ub3rgeek.net @4.2.2.2 imladris@19:22:06 ~ >dig +short imladris.colo.ub3rgeek.net @4.2.2.1 imladris@19:22:11 ~ >
---
In the "Set a FQDN" section an additional "your" should be removed:
On 2022-06-02, Matthew Ernisse <matt@going-flying.com> wrote:
I don't believe you have to 'own' anything to provide a FQDN to slrn
for messsage-id generation. I do not publish records for my internal
zones in the public views on my resolvers and I post just fine.
---
imladris@19:22:00 ~ >dig +short imladris.colo.ub3rgeek.net @4.2.2.2
imladris@19:22:06 ~ >dig +short imladris.colo.ub3rgeek.net @4.2.2.1
imladris@19:22:11 ~ >
---
This is true, then maybe a discussion on just providing a unique FQDN,
not necessarily one you own, would belong in the FAQ?
On Tue, 07 Jun 2022 06:51:02 GMT, meff wrote:[...]
On 2022-06-02, Matthew Ernisse <matt@going-flying.com> wrote:
I don't believe you have to 'own' anything to provide a FQDN to slrn
for messsage-id generation. I do not publish records for my internal
zones in the public views on my resolvers and I post just fine.
---
imladris@19:22:00 ~ >dig +short imladris.colo.ub3rgeek.net @4.2.2.2
imladris@19:22:06 ~ >dig +short imladris.colo.ub3rgeek.net @4.2.2.1
imladris@19:22:11 ~ >
---
This is true, then maybe a discussion on just providing a unique FQDN,
not necessarily one you own, would belong in the FAQ?
I am starting to feel that the section in the wiki article is unnecessary.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 422 |
Nodes: | 16 (2 / 14) |
Uptime: | 184:06:24 |
Calls: | 8,947 |
Calls today: | 14 |
Files: | 13,352 |
Messages: | 5,991,295 |