<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
I was specifically wondering about the experiment of backing newspools with IPFS - I'm pretty sure I read about this a while back - and was wondering if anybody had any more details.</div>
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
As a transport, that's a whole different matter. What we're talking about there is a single replicated spool file per newsgroup. And working out a way to post to it like a CRDT log file. That's a separate set of issues. But it does raise the question:
Is there a canonical URL format for https access to a news spool?</div>
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks,</div>
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
Miles</div>
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: "Times New Roman", Times, serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" id="Signature">
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<b><br>
</b></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
<br>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> inn-workers <inn-workers-bounces@lists.isc.org> on behalf of Martin Burmester <martin@burmester.org><br>
<b>Sent:</b> Sunday, December 15, 2024 7:58 AM<br>
<b>To:</b> inn-workers@lists.isc.org <inn-workers@lists.isc.org><br>
<b>Subject:</b> Re: INN over IPFS?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi,<br>
<br>
Am 06.12.2024 um 10:39 schrieb Jason Evans:<br>
> On 12/4/24 2:00 AM, Grant Taylor wrote:<br>
>> As has been discussed (at length) on other lists, IPFS is meant for <br>
>> FILES.<br>
>><br>
>> As such, just about anything and everything that has Protocol in it's <br>
>> name is not natively compatible with a file system as it's <br>
>> communications mechanism.<br>
>><br>
>> You could probably store a traditional news spool on IPFS, but it <br>
>> would almost certainly be inherently single point of update to avoid <br>
>> issues with overview databases and article numbers, etc.<br>
>><br>
>> But you probably could get traditional news clients that read from the <br>
>> raw news spool to read articles. I have no idea how the posting would <br>
>> go because that will almost certainly involve <something> Protocol <br>
>> <maybe something else>.<br>
> <br>
> I was thinking the same thing. I really like the idea of distributed <br>
> news articles but this would mean writing something from scratch. If you <br>
> were to go down this rabbit hole, I would suggest reading the main NNTP <br>
> RFCs to get a good understanding and then go from there. I think you <br>
> would definitely need to introduce a universal article identifier and I <br>
> don't know if the "message-id" could do that.<br>
<br>
What you can probably do is write out uucp batch files periodically and <br>
store them in ipfs, other systems could look regularly and import the <br>
batches via rnews. Wouldnt have to reinvent the wheel but start from <br>
send-uucp and adapt it. Its one way only though.<br>
<br>
Cheers,<br>
Martin<br>
<br>
-- <br>
inn-workers mailing list<br>
inn-workers@lists.isc.org<br>
<a href="https://lists.isc.org/mailman/listinfo/inn-workers">https://lists.isc.org/mailman/listinfo/inn-workers</a><br>
</div>
</span></font></div>
</body>
</html>