search

majestrate / srndv2

some random news daemon (version 2)
MIT License
19 stars 6 forks source link

>>fffffffff ImageBoard links for NNTP transfer. #35

Closed Anoncheg1 closed 7 years ago

Anoncheg1 commented 8 years ago

Hello. I am working at diploma about your nntpchan. It is Java implementation.

We have problem with links in messages, like this: >>fc346a235 We need NNTP format for links => convertation from your local articles:message_id_hash ... to ... global message-id of NNTP. When you feed(peering) with NNTP.

I will public my full work when it will be completed. See you.

Anoncheg1 commented 8 years ago

1) About convertation. I guess it require very careful replacement in message body (articles:message). OR maybe:

>>1
>>2

NNTP: Links-in-message: pmc8xpmgyf2@foo.bar, pmc8xpmgyf2@foo.bar

2) About keeping. Keep local links in database (articles:message). OR keep >>pmc8xpmgyf2@foo.bar NNTP global links in database.

Do not rush. Let's think together.

majestrate commented 8 years ago

I like the >>blahblah@something.tld style links idea. A problem I see with the >>1 >>2 style is that not all messages will propagate fully so the order will be not be sequential.

Anoncheg1 commented 8 years ago

I suggest convertation >>local .... to .... <blahblah@something.tld> and from <blahblah@something.tld> to >>local. If no message was found for >>local then it will be <null>. It is about regex performance we need to check it.

<null> to anything - for implementation suggestion.

majestrate commented 8 years ago

if >>local does not match to an existing message it should probably not be rewritten

can you elaborate on what >>local is? do you mean >>1 >>2 >>3 etc?

Anoncheg1 commented 8 years ago

>>local - short link in certain server for Web-frontend. Links in NNTP message body - global <asdasdasd@serv.org> or >>asdasdasd@serv.org links.

majestrate commented 8 years ago

How would this work with signed posts?

Anoncheg1 commented 8 years ago

I think

>>asdasdasd@serv.org[(SPACE|TAB)]

Is good format for in-body links. MUST be between 3 and 250 bytes

majestrate commented 8 years ago

so given messageid@server.tld the back link would be

messageid@server.tld ? On Apr 22, 2016 2:40 PM, "Anoncheg1" notifications@github.com wrote:

I think

asdasdasd@serv.orgSPACE is good format for in-body links.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/majestrate/srndv2/issues/35#issuecomment-213548027

majestrate commented 8 years ago

messageid@server.tld