Sharing Lain's Information

Why is knowledge gathered and shared on Lainchan and other forums not contributed to a wiki? This would make a lot of sense. Good aspects: - good opensource projects could get more attention and thus more contributers/supporters/maintainers - it could be an easy to place to link to people when telling them about the techno-industrial complex and big data - more knowledgable anons - feels good to contribute to the interwebs in a meaningful way Recently the InstallGentoo Wiki has been rebooted, (if that's the right word to use). https://igwiki.lyci.de/wiki.

More good aspects: - easily accessible knowledge inspires anon to contribute to software meta - convert more normal people into lain lovers - resist against big tech monopoly and normal person pc masterace tech culture - record of culture I have been contributing somewhat to the wiki for a long time, but it's more or less just added links to project websites. I am not well versed enough in these hacker topics to contribute heavily in explaining concepts.

>>83224 bumping for interest, there's a thread for alternative frontends and it would be nice if there was a more permanent way to list all of them.

All knowledge of lainchan could be put in a bunch of blog posts. Maintaining a whole wiki is too time consuming.

>>84114 >Maintaining a whole wiki is too time consuming. Yeah I'm curious about what it takes to actually run a wiki and maintain one. I know Heyuri hosts and maintain a wiki of their own. We could take example from them.

did they lose admin access? i dont understand the motivation for a reboot. the new one has far fewer pages and doesnt seem to have any substantial edits yet. curious about this since i browse it a few times a year. and no, i dont think we need one here. "theirs" covers much of the same domain and is freely editable

>Recently the InstallGentoo Wiki has been rebooted, (if that's the right word to use). https://igwiki.lyci.de/wiki. What was wrong with the old Wiki? I remember contributing to that old one a while back. This reboot seems to be based on an older copy of the wiki, because I checked for an article that I wrote and it's not there.

>>84116 >>84123 Site went down for a while and the admin's acquaintances couldn't get in touch with him (it's been going on before this happened) the original installgentoo wiki has since went back on but the admins already replaced the sticky with the new one. I'm only quoting what the supposed wiki maintainer said in the thread that he announced the wiki (the guy hosting https://igwiki.lyci.de/wiki) but we're all Anonymous (or whatever the algorithmic Gods will name me on lainchan) so it's hard to check the integrity of the claim. >>84114 >Maintaining a whole wiki is too time consuming. You're over estimating the time people actually spent on those pages lol. Most of the pages are just babble combined with stereotypical 4chan slang

>>84115 realistically a wiki is just a website. hayuri's wiki is mediawiki https://idroot.us/install-mediawiki-rocky-linux-9/ youd get just about any random computer. youre not serving thousands of concurrent users, maybe 10-100 max. any spare office computer will be fine to start. id recommend two harddrives so you can install with software raid 1 so you can deal with having disks die after a few years but its not super important. you can invest in a zfs truenas with redundant disks to run this as a container on later. install rocky9, follow that guide and there's a wiki. then you portforward it and buy a domain name (porkbun is good). some apartment complexes do not allow portforwarding, then you have to pay for another service to forward traffic. whatever. beware DSL internet and doublenat (portforward twice) setup certbot for https. or just use the https cert from porkbun. https is free and doesnt take too long to setup. then your monthly costs are power, internet, and the domainname (~$10-20 /year). plug it in, slide it under your bed and have fun. you dont need fast internet since its just text and some images. no video streaming or anything. its fine. operating and maintenance look like removing bot/spam posts, theming etc. regular security and maintenance is a good idea: no default usernames or passwords, install dnf-automatic to autoupdate the server. a rocky server will just sit there and run basically forever with minimal attention. you might have to reinstall mediawiki every few years as they update it. if you have actual money to invest you can look at renting a VM hosted on some company's server, but the server setup is mostly the same. stay away from aws unless you have big money. thats how id do it anyway. its a fun hobby

>>84128 What about hosting an email server on it? So you can set up email notifications, 2FA stuff and so on.

>>84163 thats a good idea. email would also allow user self registration, password resets. however i've never set those up before. you could definitely set it up without those and get something working first, then go back and set up email and integration later.

>>84128 people sometimes obsess about 100% uptime but for this type of thing 99% uptime is just as good and much cheaper. yes, if something bad happens the site may go offline for one or two days but that's ok. I don't really understand why everyone has to spend so much money to cover that potential 1% downtime

>>84114 >maintaining a wiki is too time consuming how so? the entire point of a wiki is that there are multiple people contributing. someone writes the general outline of an article, the flow, the content etc. someone else contributes with proper citations, someone else adds humor and refines the wording, and whenever an anon learns something new, they go write it in the wiki (if it's not already mentioned). with a blog it would be only you that has to maintain it, rather than just trust that some other anon would fix any mistakes. i don't know if that's what you meant but that's what >>84125 seems to think the only problem i can think about is conflicts between different writers, but i'm sure we could solve that by having separate pages with different views on the topic. the page on text editors would link to both'the emacs argument' and 'the vim argument' for views favoring each (just an example). >>84115 >>84128 >>84168 we wouldn't even have to do that. see > https://miraheze.org/ >>84115 >>88116 >>84123 >>84125 i used to contribute to the old wiki ever since 2022 or something. half the pages were spam. they were empty pages, scheduled for deletion, but couldn't be deleted as the head guy went silent. some general threads still reference the old wiki by mistake. >>84109 https://igwiki.lyci.de/wiki/Privacy_friendly_frontends contribute to this for now

>>84195 >https://igwiki.lyci.de/wiki/Privacy_friendly_frontends I got bored and finished one of the todo thingies "add simple wojak/pepe infographic about how frontends work"

>>84200 Nice list, but it seems you need an account to edit it. Can anyone add PixivFE (https://codeberg.org/PixivFE/PixivFE) as a pixiv frontend?

>>83224 How valid is the countries section? Is it up to date any expansion plans?

>>83224 instead of a wiki, i think something less structured would work best, and even better if it can display some pseudo recreation of replies to threads (basically a div subdivided into name, img, and post text) would work best (you really don't wanna keep only images because that really limits a site. screenies are not only heavy but impossible to search in most cases, reason why preservation of the content in actual text must always be favored. this ofc doesn't include picrels, those must be preserved somehow but generally in most cases the real goodness of a post is in the text). sometimes there are gems on this site, great threads where at least 50% is cool or useful info you don't find anywhere else, or at least not presented in that particular way, but because the other 50% is soykaf appelman decides to delete the whole thread and all those nice replies get lost forever (because yes, sometimes some threads get a lot of traction the day they're posted and then after maybe 12 hours get deleted). i've been here for years and it really hurts every single time i wasn't quick enough to save a post, since i feel like this is one of the last places with real human interactions, and i don't like any other imageboard really.

>>84276 forgot to mention, continuing with the idea of posts getting a lot of traction and being deleted quickly afterwards... they aren't really scraped on time by wayback machine so we don't even get that. in general, it would be interesting to assemble a team of people keeping an eye on the site and saving anything cool, on a unified place ofc to avoid data duplicity, maybe a git repo would be a good start since it's both "centralized" and can be quickly cloned with a single command, and the commit history is always great to know who uploaded what, and when they did so . flood detected, sanity discarded .