Overboard Index

issa gem

Arische

Good

smiler.png
[Hide] (65.2KB, 750x750) Reverse

>/a/ - Specific

sage

USER WAS BANNED FOR THIS POST test ban

tnd

>>24
kys

>>24
lys

60a8075b-62a0-40a3-a036-17c2694a9531.png
[Hide] (744KB, 640x800) Reverse

test

Interesting, I also don't fully understand but I guess this helps trim down the amount of querying you have to do by a lot?

>>72
1.5 hours, no red cross emojis anymore but still no images. Now I can see debian's messages at whonix, those sent 1.5h ago and 25 minutes ago. Also now I can see whonix's messages at debian. Weird.

Thanks for the logs and info.
>{"level":40,"time":1710924428820,"pid":14354,"hostname":"host","module":"lazysub","msg":"Recieved message that did not verify PubSubData"}

I've encountered a similar issue with windows:
https://github.com/dao-xyz/peerbit/issues/283
Still not sure what causes it but there seems to be some (temporary or conditional?) inability to verify database entries on some systems. Like you experienced, it didn't work on windows but then some time later after rebooting the node it worked. It's puzzling but hopefully we can get to the bottom of it soon.

>>73
So if you don't see the red crosses, that means the files are "present" but the chunks aren't being streamed to you properly. I wonder if it's something to do with the buffer size on your Whonix setup. If you don't mind, could you please experiment with  reducing this bufferSize variable to a lower value?

https://gitgud.io/threshold862543/gladden/-/blob/master/dist/server.js?ref_type=heads#L214

Or perhaps data streaming in the way it's implemented here in generally isn't working with your setup.

Is there always a prett

brokenimage.jpg
[Hide] (21.2KB, 707x801) Reverse

>>73
>>74
One thing also. Do you have "broken image" icons or does the page simply just keep "loading" without end?

>>74
>>75
Oh also, if you post an image on the Whonix system, are you able to see it locally?

>>76
>>75
>>74
As of now, gladden works on whonix vm. It even syncs new posts in seconds rather than hours, images working etc. So to replicate, I'd had to install it fresh, maybe later. Imo this could be non-whonix-specific issue

I think I may do the in-browser interface with a different style than the jschan interface shared by peerchan and peerchan-peer.

really impressive work so far, keep it up!
for what it's worth, every time i load a page, my browser offers to remember the pre-filled password in this dialog box
i'm not sure why it's pre-filled, or if it can be replaced with a hidden form element until clicked

>>53
Thanks! Though I should mention I've pivoted to working on project gladden rather than the peerchan software itself recently.

The main reason for the password is that jschan (that peerchan is forked from) generates a randomized password for post deletion. On firefox especially this can be annoying, but it might be possible to do "Never Remember" or something like that, or perhaps "Remember"?

There are still features that should be added but I decided to release this project for now anyway:

https://gitgud.io/threshold862543/gladden

IMAGINE-THE-SMELLE.jpg
[Hide] (46.4KB, 600x450) Reverse

jesus what type of shitty forced content is this
heres your (you) you earned it maki

>>8
Someone isn't smelling anything nice today.

e6f3bd7bdea4d7ea0e50fee3bc66168788c4e9cbac4f3ed68b01d40cfe272627.jpg
[Hide] (214.7KB, 1920x1014) Reverse

Taking a detour to port the accounts database over to peerbit. This should allow us to do things like spam control and banning in a more P2P fashion. See here for more info:
https://gitgud.io/threshold862543/peerchan/-/issues/9

mucha-the-four-season_u-L-F7HV8Q0.jpg
[Hide] (114KB, 900x599) Reverse

I changed how files are stored so they can be stored in a way where any peer can check their validity and a mediator isn't required to do so. So now when uploading files via the peerchan-peer client (or another client) you simply start seeding them. The next step is doing this when you post via peerchan-peer and also adding file references to the post submitted to the mediator. What kind of validation checks (for the post itself) should be performed the files uploaded, if any, is something I'm still considering. Maybe we will let people upload broken files and not check them, as hopefully the access control logic for opening files will protect the attack surfaces decently and just lead to someone uploading broken files.

Just handling the thumbnailing/other metadata processing for file posting and once this is working nicely, I'll prepare to upgrade peerchan.net to allow for P2P posting through peerchan-peer.

imgboard7.png
[Hide] (242.4KB, 1335x1859) Reverse

Things are in a decently functional state now. I'm going to prepare to upgrade peerchan.net so you can browse as well as post via the peerchan-peer client.

See here for more info:
https://gitgud.io/threshold862543/peerchan/-/issues/6

Pic related is a python based imageboard prototype I was messing with before deciding to fork jschan.

>>30
Have you heard of antiflood tokens?
https://docs.freenet.org/examples/antiflood-tokens.html

>>41
You're welcome

>>43
WON

wtf did that post just disappear the second i replied to it

no logs either
50/50 on whether that was trannyjannying or the shitty software ate the post

>>46
Clients should make it clear when a post is deleted to prevent that kind of thing imo.
Maybe posts in a thread should form a hash chain / blockchain so its obvious when its broken

chunk chert

impressive

...
I was messing with something trying to fix a longstanding bug but it seems to have made it worse.. lol
Thanks I'll look into it.

Okay fixed it.

1693691865200-tegaki.png
[Hide] (5.8KB, 500x500) Reverse

>>17
Test

Test

Oh-ho-ho!

>>12
Nice

does this work?

Test post.

61lxgmrurUL.jpg
[Hide] (82.1KB, 1500x1500) Reverse

Test file.

Peerbit itself uses cryptographic identity on the client level so you have a keypair associated with the node you use to add database entries. This can be used for things like access control, and I'd like to use this for moderation-related things in the future. Good idea with ring signatures.

Though being able to post freely without registration is in my view an important aspect of imageboards, and I wouldn't want this to the case by default, it would certainly be nice to make things flexible enough to facilitate all sorts of vetting mechanism on a given site so people can experiment and find what works best for their community.

>>11
Ring signatures could also be used to identify a mod as being a mod (i.e. as the peerchan version of a capcode) or to sign mod actions, without identifying which mod specifically they are.
Was that what you were thinking of?

>>25
That'd be ideal. Right now there's two classes of users
"mediators" and "users". The mediator is responsible for actually adding posts to acess-controlled databases, like posts. Files on the other hand I am thinking will be open-access so you can add whatever files you want to the database freely. 

Some degree of access control is necessary for things like posts, as there are considerations for formatting, ban checks, spam checks, etc. that need to be performed before a post can be accepted. It may be possible to make some of this "automated" in the future where peers will perform these checks themselves as well. But for now I'm going with the simpler lower hanging fruit to make things more distributed step by step and then we can experiment more going forward

By the way, files will only be actually downloaded by peers if they call the getFile() function on the file document. The file document itself is just a reference to the actual file chunks. I'm going to have to modify this system a little bit going forward but overall the concept should be essentially the same.

Right now I'm working on this concept of performing actions via the mediator by making RPC calls to it. In this sense we use another node as an API into the database, the contents of which are then read-accessible freely by all peers. With this we can define specific actions that can be executed by specific identities, but will actually be ex

>>26
>Right now there's two classes of users
>"mediators" and "users".

But going forward we can also experiment with making this more granular and allow things like moderators being able to directly delete post documents in the database.

Something to consider is that in a system like this where there is not necessarily a canonical ordering of events by default, special considerations have to be made around concepts like... what happens if a moderator was stripped of their position, but, right after that, tried to delete a bunch of posts. If some nodes lacked information about the current state of the. Honestly this might not be such a big deal in practice, but could lead to some "canonic splintering" of the current state of the database depending on which peer is looking at it and what data they have available, which is an interesting situation.

>If some nodes lacked information about the current state of the

current state of the moderators permissions list*