1
Fork 0
Documentation for using git.LMAO.ch and your webroot.
Go to file
2024-04-01 03:19:13 +00:00
LICENSE Add License 2024-03-08 05:47:57 +00:00
README.md Update README.md 2024-04-01 03:19:13 +00:00

Table of contents

Content policy

There are very few restrictions on what you can put on a webroot or have in a Git repository. You can see the full acceptable use policy here, but here's an excerpt for restricted content :

  • pornography of any kind (if you are concerned about art, please err on the side of caution and ask)
  • real-life gore or similar graphic content
  • statements inciting violence or harm to people and/or property
  • sale of illegal products or services, such as drugs, firearms, products of human remains, et al.
  • any kind of proxy or traffic-relaying server
  • any kind of gambling or lottery services
  • distribution of any malicious software
  • use of cryptocurrency miners, both on servers or on clients
  • any kind of third-party tracking or adverts, such as Google Ads or Analytics, Adobe Campaign, et al.
  • any other content not allowed on the Internet by Icelandic, U.S./American, or your local authorities.

Getting help

Please make sure you have read through this and any other relevant documentation before reaching out. Odds are an answer to your question may already be found.

There are two main ways that you can get help with this code forge and its services. The main, preferred method is e-mailing wtf [AT] lmao.ch with an e-mail address that's on your git.LMAO.ch account. It's very easy to validate a user's identity by asking questions that are only visible to authenticated users this way, as well as allowing quicker methods of trust through GPG keys or S/MIME certificates that you may possess. The alternative is to contact an administrator directly. Administrators always are public members of the @lmao organisation. The only reason this isn't preferred to e-mail is that administrators may not be familiar with every user, despite this forge's size.

Getting rid of an old organisation

To keep code accessible, you should remove all members of the organisation except yourself, then add @phantom as the sole owner. After, you should be able to leave the organisation and have it persist. @phantom is an official account managed by administrators of this instance.

Ideally, you should keep this code public (or at the least, unlisted) and under a OSS licence. If neither are possible, skip this and simply delete the repositories within the organisation and the organisation to leave the name free for others.

Inviting others

Anyone can use LMAO.ch — both a webroot (https://lmao.ch/~username) and unlimited public and private Git repositories here on git.LMAO.ch. Simply ask someone you know. Public Git migrations can be done for you in advance, if you'd like.

Supporting LMAO.ch

There is no tips system in place at this time ; however, the cost to operate the services offered remain non-zero. This may change in the future to allow greater archives/mirrors and allow for more users/codebases.

Using your LMAO.ch userpage

Users who add ed25519 keys to their account can use rsync to push changes to git@lmao.ch:lmao.ch/~username where username is their Forgejo username. Keys are not automatically added or updated — if changes need to be made or you want it to be updated sooner, please reach out.