I’ve been using coomer for a while and love what it offers. The way it organizes pages and posts is incredibly useful. But lately downloads have been painfully slow and connection timeouts are making it nearly impossible to get through larger sets of files

Name
EmailY7m⚵5$☎ub♿@<IykeJg }#9⛒l⚊V`Mahv&Xs☫\GZS0☃2wrE)F61(T⚾⛝>BDd4';Np\|.cU%n♓[,/x q-WK^z3H{*Rf!L?=tCA~j]_o	rW16P#3msv%H]c♲`TS?qN!=QpZ☖fhJ$l~\|0w^4oB&CGt;⛈iXK*7/⛭ xbOFy☷[D>jYa<d
Subject
Comment4xnIZruG-Y^/
Verification
File
Password	(For file deletion.)

Offload Pressure by Decentralizing / Distributing Data nosnake 08/01/25 (Fri) 19:18:04 No.6201

I’ve been using coomer for a while and love what it offers. The way it organizes pages and posts is incredibly useful. But lately downloads have been painfully slow and connection timeouts are making it nearly impossible to get through larger sets of files. I imagine the coomer servers are under a lot of pressure as the site scales. I’d like to propose an idea to help share that load.

Instead of having every user pull every file directly from coomer’s servers, we could create a lightweight client that connects users together. Once someone downloads a file from coomer, they could optionally share it with others and help reduce the demand on the site's resources. Coomer would still act as the master of file lists, checksums, and metadata.

The main site stays the same, but users who opt in could:

Run a small desktop client that connects to other peers
Download new files from Party only if no peers have them yet
Share previously downloaded files with others in the background

Is this a new protocol? Maybe but not exactly.. It’s more like combining a few existing ideas:

The distribution model of BitTorrent
The update/feed structure of RSS
The control of Syncthing, where Coomer is the source of new content, and users are read-only peers

I haven’t seen an off-the-shelf tool that does exactly this, but the core concept is simple. I'm not a programmer so the best i can do is pitch this idea but probably like most of you, i have extra storage and bandwidth to spare and tired of feeling like a leech

Anonymous 08/03/25 (Sun) 19:20:19 No.6222

nobody likes an armchair tech support agent

Anonymous 08/04/25 (Mon) 04:20:22 No.6230

>>6222
shut up faggot

two problems: 1) you assume the people running this site have any clue what they're doing besides the bare minimum of keeping the lights on and 2) that any of coomer's users are going to willingly allow access to downloaded files on their local machines through P2P

this site was meant to archive, not be a download hub. it has turned into a download hub because the majority of us who have been around long enough know this place is a ticking timebomb, and there's going to be a day when it either gets taken down, or functionality completely fails from some script kiddie admin dicking with the source code

nosnake 08/04/25 (Mon) 12:11:42 No.6231

>>6222
I literally told you I'm not a programmer.. Did you struggle to find a valid issue on your own and decide to rearrange my words into derogatory comment? Do you feel better now or still having that tantrum?

>>6230
1. This wasn't an idea to be tasked solely by the admins here. What i proposed can be done by anyone. the larger the amount of people that participate, the more we can offload from their servers.
2. Never seeded a torrent yourself i suppose. It's only been a thing for the last 24 years. Crazy how it's been around for so long when no one allows P2P to their computers.

Nothing is forever and discussing what or how it may happen isn't relevant to this topic. This thread is about giving the coomer nipple a break and instead getting a copy of the same milk from your neighbor.

BitTorrent already solves the majority of what i suggested but it's not the right tool for the job. The issues faced are not unique to coomer either. GitHub is full of proof of concepts that seem to solve individual problems here and there (https://github.com/publiusfederalist/federalist). But again i have not found a off-the-shelf solution which is the purpose of creating this thread.