No Stupid Questions
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
iirc You “pin” content to access, which means you’re also then hosting it. You wouldn’t need to necessarily store the entirety of wiki for example unless its held in like, data files rather than page per content.
Im not fully up to scratch of the intricacies on IPFS, just thought it sounded like a possible solution to your use-case
As far as I know, but I might be wrong. IPFS is great for static content. But wikis are dynamic but slow.
Every change must be stored as duplicate file. For low bandwidth text based content it could probably work.
The 6h news cycle of web 2.0 would be incompatible with IPFS but web 3.0 and fediverse could be made more static, (more users see the same article so it could work)
Very good call! That had totally slipped my mind, thanks for pointing it out. It does look like theres a mutable file system solution that works with IPFS? Like you’ve mentioned though, this might be slow.
https://docs.ipfs.tech/concepts/file-systems/
So someone above mentioned Git, would that be comparable to how IPFS works?
Completely different solution but that would also work.
git is a version control system (vcs), github is a git host (repository).
It allows you to “check in” files, and if you share it / make a public repository others can check it out. You can also allow others to request changes (pull requests).
You add files to a git vcs. Github provides public repositories. For documentation example, you could create a set of HTML changes and check them in. Whenever you then make changes to existing files, or add/delete files, the repository will track the changes (so you get a history of changes timeline).
You can selfhost a git repository using gitlab for example. Or you could use github/gitlab as a centralised provider. Github has been around for a long time, I don’t see it going anywhere but in the worst case its trivial to push that same repository and history etc to a different provider.
Documentation may talk about code/programming as thats its main use but its not a requirement and doesn’t require any programming knowledge.
Github also provides a document/web page hosting thing I believe?
https://docs.github.com/en/get-started/quickstart
https://www.gitbook.com/
https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis
https://about.gitlab.com/install/
https://support.atlassian.com/bitbucket-cloud/docs/get-started-with-bitbucket-cloud/
ed - git would be far simpler than IPFS but isn’t decentralised like IPFS. But like I say, migrating or self hosting is pretty trivial
Thanks for your detailed explanation. The IPFS seems to be run by one guy also involved in something cryptocurrency, that looks a bit fishy to me. (Just a personal first impression by me, who has no clue and might be all wrong). From quickly looking into both I would probably prefer sth like git, as it has been around for longer. How is git not decentralized - as I understand, with git the files are stored on several machines and everyone can make and commit changes? I might still be struggling to understand the whole concept of decentralized here. Github is owned by Microsoft apparently and I won't touch their stuff unless I really have to.