(untitled)

Is there an imageboard which has some form of authentication or login just to keep spam and other unwanted soykaf out?

Yes, #Mastodon^^

since you originally posted that thread in /lambda/ I wouldn't trust your judgement

No, imageboards are an obsolete form of communication that cannot be moderated anymore. The advent of AI and political or corporate (really, one in the same) astroturfing means any imageboard that gathers even a medium-sized crowd will get compromised and manipulated to advance political agendas that serve whoever's running the bots.

tsukichan has an imageboard that requires registration to post on

Reddit

>>9447 >No, imageboards are an obsolete form of communication that cannot be moderated anymore. Not true. The communities around image boards fell a lot more uncensored and authentic compared to any place that requires registration. If you have an account, you wouldn't like it to be derezzed.

>>9440 Can't you use filters?

>>9447 Imageboards suck, but when the alternative is social media where the worth of what you say is based solely on how influential you are and not what you're actually saying, I'd rather deal with imageboards. An influential person can lie as much as they want, and even if someone calls them out on their bullsoykaf, it doesn't matter unless that person is even more influential. Here there is no identity, so you actually have to back your words up with something other than your follower base or "lol he likes (x) what a loser" or whatever. That being said, imageboards do have a lot of room for improvement. It's so easy to fake things, you can spam a belief you like to make it seem more popular than it really is, and you can false flag as a belief you dislike, doing an intentionally poor job defending it in order to discredit it. I can't see a way to combat this without introducing identity and all of its problems (or just overmoderating the hell out of the board), though.

>>9449 Hey this is really comfy , thanks.

>>9484 I take this back , what the fuarrrk is this schizoid mass larping all about ?

>>9440 4chan has captcha.

An alternative might be certificates issued individual users via some automated process. From that point on a given user has to post to the board using the certificate. It removes the need to remember user names and passwords. User names, passwords and certificates are useful as a filtering mechanism, anyway. One thing about communities is that they generally have some gateway requirement to ensure that people really interested in the community get in (because they'll make the effort to fulfill) the requirement and everyone else stays out. Chans tend to handle this by the use of chan culture which can drive people who can't handle it away.

>>9455 Underrated post

>>9503 4chan's captcha is more like trying to breathe, but with every breath you have to solve a 100 piece puzzle

currently writing an imageboard in rust which has invite tokens. Every user must have a token with every request or the server won't respond.

>>10237 I set my browser to clear cache and other things when I shut it down. How will this affect the token? Can the token be saved to a file? For example, when entering the site for the first time in a session, the user has to load in the token with the first request and thereafter a cookie or session ID handles things automatically.

>>10238 The token would be essentially a password and username in one. You log in, your browser sets an HTTP session cookie with your token, you can now make requests to the server and invite people. I have some tree-ban functionality written. It's intended to be a very lightweight onionsite.

I'm in one but aint telling

>>10240 Then why mention it?

>>10240 You wound me

>>9487 It was fun a year or two ago when people were at least pretending they were going to kill themselves. The culture was sort of like lainchan if lainchan had splintered off of /x/ instead of /g/.. It hasn't aged well though. The site went down at one point and people moved to a discord group which splintered into other discord groups and tsuki took forever to get the boards running again. When it finally came back up nobody who was in the first wave gave a soykaf any more and the people who remained spent most of their time bitching about getting "invaded" and harassing any new members who had the audacity of joining their sekret club without knowing all of the in-jokes and memes they had come up with over the past year. The new boards became an extension of this soykafty self-important discord culture that had evolved. That being said, early on the registration requirement plus tolerance for name/trip-fagging created an interesting and somewhat unique culture.

>>10237 I want to make something like this too, but I don't know how.

>>9440 enrive.org a.k.a. former "masterchan"

https://1chan.us/ https://bbs.anoma.ch/

>>10272 I think you described the death of many chans. The original kind of youthful spirit or energy dies and something much darker fills it's place. It becomes a downward spiral of a community with a cult like us vs them attitude. Even get out new user type stuff is usually fun and harmless at the start, eventually it has little to do with who is new and not new and more "do you agree with me on this this and this".

>>10237 this got me thinking: it would be interesting to do something like this with the tokens generated is pgp-like web of trust combined with elements of an SSL PKI hierarchy. users "invite" other users by signing their private key (i.e. token). these signatures can be revoked. maybe you decide on some minimum number of signatures to make a key 'valid' for the purposes of posting. maybe this number changes based on the users post count, sort of like seeding ratio requirements on a private tracker -- i.e. new users only require a single signature, but as they post more they will require more signatures. idk there's definitely some bugs to work out... some of this stuff wouldn't really work if everyone was always anonymous.

>>9440 Sadpanda.

>>10282 This is interesting but also enables network analysis that would de-anonymize people. Perhaps a crypto token (PostCoin) that limits number of posts.

>>9440 i once heard around some part of the internet( forget where) about an image board called gode you need a code or something to get in but i remember its really weird how you get the code. anyone know what im talking about?

>>9457 I realized pretty soon that all these freedom fighters are really all people whose hands are dirty with something or got derezzed from the mainstream. I would really love to say "hurrrr it's not true that if you have nothing to hide you have nothing to fear"because technically it's true, but in 99% of cases the person using this argument DOES have something to hide. I don't believe in internet privacy any more. I think it should be highly regulated. People had the chance to build decentralized communities but it's very clear what they really wanted to do with those "uncensored" platforms.

>>18570 if you have nothing to hide, please post your credit card numbers and a copy of your photo id. you have nothing to fear, right?

>>18570 Export your browser history and post the file in this thread. Btw, lack of censorship isn't intrinsically linked to anonymity and I'm not sure why you brought it up. They're often correlated because of the ideologies involved but you can certainly have a strictly moderated/censored anonymous space. In fact, I tend to prefer such spaces. Lainchan is a decent example.

>>9457 Sites that display your name with everything you say very quickly turn into hiveminds and sucking off more established members. Anonymity allows people to have truly free discourse and although you get some soykaf with it you get a far better overall quality than one where there is a social pecking order.

the only way to have an anonymous public site that doesn't turn into a soykafhole is to have very active mods who know how to recognize and eliminate corporate/state/religious/political/etc propaganda teams that use bots to find keywords and alert the assho... uh, i mean the team members to show up and spam copypasta talking points. that's what ruined a lot of good imageboards.

>>18573 >Sites that display your name with everything you say very quickly turn into hiveminds and sucking off more established members. I'm working on a Tor-friendly forum system, and I'm implementing something that I think will help avoid hivemind situations. Usernames aren't displayed in posts, and users' posting history is not available to other users. Instead, in each thread, each displayed "username" is actually a hash of the real username, the creation timestamp of the thread, and a secret salt. It's basically like an enforced tripcode that stays the same per-user within a thread, but changes between threads. People can be free to speak their minds in any given thread, knowing that other users can't tie their past posts in other threads, but it also prevents sockpuppeting.

>>18605 This is a good idea

>>18605 very good idea.

>>18605 The admin would still be able to tie all posts to a user though, would they not?

>>18610 Do you really think the Lainchan admins cannot see that either? Of course you're putting trust in the admins when you post.

>>18605 looks a lot like IDs on 4chan I think mechanics won't save the conversation. All you need is to focus on specific interests and keep it that way. The moment you allow porn or politics or vent threads the community becomes a formless blob. What the internet is missing right now is focused interest groups like there used to be in the 90s, only Reddit does that but it's astroturfed to hell.

>>18609 >>18610 Does it even matter if you're going to allow tor posting?

>>18610 This is why I'm designing the forum system to be as easy to install as possible - a single self-contained binary with a sane default config and built-in web server, using sqlite instead of relying on an external database server, etc. If an admin becomes untrusted, it would take about 5 minutes for someone else in the community to start up an alternative site. No technical experience required, just the ability to read a few paragraphs on how to start a Tor hidden service. I'm writing the documentation with an eye towards grassroots activists who have never even heard of what a "command line" is. >>18617 Not merely "allow", but the system is laser-focused on Tor-friendliness. Not a single line of javascript anywhere, very lightweight html templates that allow for fast page loading even over slower Tor links, etc. Right now I've got the post-less front page down to about 11KB. I could probably get than down to 8 or 9 if I used style tags everywhere in the templates instead of using regular CSS classes loaded from a linked stylesheet (so unused classes don't need to be transferred) but that makes customization for non-programmers difficult for a negligible performance gain. The signup process is designed around the concept of covert cell groups. Users can be added manually by the admin of course, but user self-signup requires a one-time-use token. The admin can give a bunch of those tokens to some "cell group leader" to pass on to others, which allows plausible deniability to the admin and other cell leaders regarding the identities of those signed up through one cell leader. Of course there's nothing preventing an unscrupulous cell leader from making a bunch of sockpuppet accounts instead, but 100% foolproof technical solutions to social problems are impossible. All I can do is provide tools to help non-technical people better protect themselves. Call me a pessimist, but I'm thinking this sort of tool is going to be useful in the near future.

>>18617 Not for the usability of the site itself but from an anonymity standpoint if the forum was to be targeted all it would take is one successful decloaking by an adversary and they would be able to correlate everything you ever said to your real world identity. You potentially don't even need to decloak them via tor, the admin could build a profile on a user and depending on how much they said figure out who they are in the real world.

>>18620 Sure, could happen. But that's not a problem that I can solve. The best I can do is make it a major pain in the butt for an adversary, and perhaps force adversaries with limited resources to give up. I can live with that limitation. There's a few other tricks going on under the hood. Stripping metadata from uploaded files, obsessive sanitizing of text inputs, no HTTP error details being disclosed on error pages, etc. One feature I'm particularly proud of is users' ability to set an optional autolockout time for their account. After N number of hours without a fresh login, the account is disabled such that only the admin can reactivate it. My "target market" for that feature is direction-action activists in countries like the UK where there are extremely severe penalties for refusing to hand over login credentials. If they're worried about arrest after an action, they can set an autolockout for, say, 12 hours. If they're safely at home the next morning, they can disable the lockout and resume using the account as normal. If they're stuck in a jail cell overnight and the next day some goon with a badge demands they hand over their login and password, they can freely obey the letter of the law, knowing that it'll be useless to the goon. The phrasing of the error message in the system is careful to not say that the admin had locked the account, not that the user had anything to do with it. Of course, the goon in question may retaliate, but again that's not a technical problem I can solve. It's a political and social one.

>imageboard >authentication or login Instagram

>>18618 if you want tor-friendliness, the most important thing is reducing the number of round-trip requests. Use CSS embedded in the HTML page. Banners and maybe also image previews should be base64-encoded.

>>18626 and/or use the Cache-Control HTTP header for anything that won't change

>>18628 aye, it depends on the tradeoffs(e.g. a tiny CSS file can be embedded in HTML, but a big one should probably be cached)

>>18626 All true. This is why the interface has no images, aside from thumbnails in posts. The HTML is generated by the backend on the fly and sent as a single document. Not counting thumbnails, exactly two files are sent on each request: the HTML and the CSS. The base64 image idea is fascinating. I've never heard about that capability before. I've just been reading about and it's something I'm immediately going to implement it. Thank you! It's a slight bandwidth hit, but definitely faster from a request-round-trip perspective.

>>12866 SadPanda is more a of a file sharing website -- it's main focus isn't discussion.

>>12866 People actually discuss things on sadpanda?