fix some typos and warnings

pull/53/head
Ben Harris 9 months ago
parent 9afc78c636
commit d28b51fa6a
Signed by untrusted user: ben
GPG Key ID: 4E0AF802FFF7960C
  1. 19
      badges/badge.php
  2. 6
      badges/index.php
  3. 7
      badges/shieldsio.php
  4. 7
      composer.json
  5. 2
      index.php
  6. 28
      wiki/pages/badger.md
  7. 2
      wiki/pages/botamusique.md
  8. 6
      wiki/pages/bots.md
  9. 2
      wiki/pages/channels.md
  10. 8
      wiki/pages/chaos.md
  11. 10
      wiki/pages/etiquette.md
  12. 6
      wiki/pages/nicks.md
  13. 26
      wiki/pages/servers.md
  14. 8
      wiki/pages/user_accountability.md

@ -1,11 +1,10 @@
<?php
include 'shieldsio.php';
if (!isset($_GET["channel"])) {
$badge = get_badge();
header("Location: {$badge}");
} else {
$badge = get_badge($_GET["channel"]);
header("Location: {$badge}");
}
die();
?>
include 'shieldsio.php';
if (!isset($_GET["channel"])) {
$badge = get_badge();
} else {
$badge = get_badge($_GET["channel"]);
}
header("Location: $badge");
die();

@ -12,13 +12,13 @@
</tr>
</thead>
<tr>
<td>Network user count</td><td>https://tilde.chat/badges/badge.php</td><td><img src="badge.php"></td>
<td>Network user count</td><td>https://tilde.chat/badges/badge.php</td><td><img src="badge.php" alt="user count badge"></td>
</tr>
<tr>
<td>User count for #meta</td><td>https://tilde.chat/badges/badge.php?channel=%23meta</td><td><img src="badge.php?channel=%23meta"></td>
<td>User count for #meta</td><td>https://tilde.chat/badges/badge.php?channel=%23meta</td><td><img src="badge.php?channel=%23meta" alt="#meta badge"></td>
</tr>
<tr>
<td>Invalid channel name (error handling)</td><td>https://tilde.chat/badges/badge.php?channel=invalid</td><td><img src="badge.php?channel=invalid"></td>
<td>Invalid channel name (error handling)</td><td>https://tilde.chat/badges/badge.php?channel=invalid</td><td><img src="badge.php?channel=invalid" alt="invalid badge"></td>
</tr>
</table>
<?php include '../footer.php'; ?>

@ -1,5 +1,6 @@
<?php
function get_badge($channel_name=FALSE) {
function get_badge($channel_name=FALSE): string
{
if ($channel_name==FALSE) {
return "https://img.shields.io/badge/dynamic/json.svg?url=https://tilde.chat/stats.json&label=~chat&query=$.usercount&suffix=%20online&link=https:%2F%2Ftilde.chat&link=https:%2F%2Ftilde.chat%2Fkiwi%2F&colorB=%2300cc00";
}
@ -8,9 +9,9 @@
$stats = json_decode(file_get_contents("https://tilde.chat/stats.json")) ?? array("channels"=>[]);
foreach ($stats->channels as $key=>$channel) {
if ($channel->name==$channel_name) {
return "https://img.shields.io/badge/dynamic/json.svg?url=https://tilde.chat/stats.json&label=~chat&query=$.channels[$key].usercount&suffix=%20online%20on%20{$name_url}&link=https:%2F%2Ftilde.chat&link=https:%2F%2Ftilde.chat%2Fkiwi%2F{$name_link}&colorB=%2300cc00";
return "https://img.shields.io/badge/dynamic/json.svg?url=https://tilde.chat/stats.json&label=~chat&query=$.channels[$key].usercount&suffix=%20online%20on%20$name_url&link=https:%2F%2Ftilde.chat&link=https:%2F%2Ftilde.chat%2Fkiwi%2F$name_link&colorB=%2300cc00";
}
}
return "https://img.shields.io/badge/~chat-invalid%20channel-red.svg";
}
?>

@ -1,5 +1,6 @@
{
"require": {
"tildeteam/wiki": "^1.0.0"
}
"require": {
"tildeteam/wiki": "^1.0.0",
"ext-json": "*"
}
}

@ -1,5 +1,5 @@
<?php include 'header.php'; ?>
<h1>tilde.chat <img src="/badges/badge.php"></h1>
<h1>tilde.chat <img src="/badges/badge.php" alt="tilde user badge"></h1>
<hr>
<p>hey hi</p>

@ -2,29 +2,29 @@
author: ~khuxkm
published: true
title: "badger bot"
description: Twitch Plays Pokemon badge system
description: Twitch Plays Pokémon badge system
category:
- main
---
# badger
The Twitch Plays Pokemon badge system, ported to tildeverse IRC!
The Twitch Plays Pokémon badge system, ported to tildeverse IRC!
## How it works
Every 20 to 50 messages in #meta, the person talking will recieve a random badge. These badges have a distribution like so:
Every 20 to 50 messages in #meta, the person talking will receive a random badge. These badges have a distribution like so:
|Badge Name |Chance of pull|
|-----------|--------------|
|Berrybadge |65.00% |
|Firebadge |15.00% |
|Rockbadge |10.00% |
|Waterbadge |5.00% |
|Shadybadge |2.00% |
|Musicbadge |1.90% |
|Sportsbadge|1.00% |
|Tildebadge |0.10% |
| Badge Name | Chance of pull |
|-------------|----------------|
| Berrybadge | 65.00% |
| Firebadge | 15.00% |
| Rockbadge | 10.00% |
| Waterbadge | 5.00% |
| Shadybadge | 2.00% |
| Musicbadge | 1.90% |
| Sportsbadge | 1.00% |
| Tildebadge | 0.10% |
You can transmute 3 or more badges. When you do this, it will create one, hopefully rarer badge and take the badges you put in away.
@ -50,4 +50,4 @@ Opts you out of the badge game entirely. You will not be able to participate aga
### `+optin`
Opts you back into the game, allowing you to participate again.
Opts you back into the game, allowing you to participate again.

@ -7,7 +7,7 @@ category:
- main
---
***NOTE***: botamusique is back in business! after the files for it mysteriously disappeared, I reinstalled everything and it should be back in working condition!
***NOTE***: botamusique is back in business! after the files for it mysteriously disappeared, I reinstalled everything, and it should be back in working condition!
botamusique is our new mumble bot. (RIP MumbleDJ 2018-2020, you will be missed.) Here are some commands you can use:

@ -11,7 +11,7 @@ category:
you might have seen some bots lurking about in chat. this page is intended to be a common place for documentation.
bots should be well behaved and efficient with system resources. if you see a bot that is not, please remind the botmaster about this and/or notify an admin. naughty bots can make the system less enjoyable for everyone, and we all have to work together to police them.
bots should be well-behaved and efficient with system resources. if you see a bot that is not, please remind the botmaster about this and/or notify an admin. naughty bots can make the system less enjoyable for everyone, and we all have to work together to police them.
## rules and etiquette for tilde.chat irc bots
@ -29,7 +29,7 @@ if your bot's code is not yet stable, keep it in the #bots channel and do testin
don't join #chaos or unless you want your bot to be spammed to hell and back.
all of the bots should also adhere to the following RFC specification: [RFC 2: Standardising IRC Bot Behavior](https://rfc.tildeverse.org/rfcs/2).
all bots should also adhere to the following RFC specification: [RFC 2: Standardising IRC Bot Behavior](https://rfc.tildeverse.org/rfcs/2).
## tilde.team bot starter kit
@ -93,7 +93,7 @@ follow the example of sedbot when you add your bot in a PR to the wiki
- [source](https://tildegit.org/lickthecheese/circles)
* [badger](./badger)
- botmaster: [~khuxkm](https://khuxkm.tilde.team)
- short description: the Twitch Plays Pokemon badge system, ported to tildeverse IRC?
- short description: the Twitch Plays Pokémon badge system, ported to tildeverse IRC?
- list of functions:
- `+listbadges` - List the badges in your possession.
- `+transmute <badge> <badge> <badge> [badge...]` - Transmute 3 or more badges into one, hopefully rarer badge.

@ -40,7 +40,7 @@ you can only register if you already have +o (chanops). this is automatically
granted when you are the first person to join a channel.
note that you need to be identified to NickServ for this to work. the channel
will be registered to your account and you will automatically be granted +q and +o.
will be registered to your account, and you will automatically be granted +q and +o.
## setting persistent modes in your own channels with chanserv

@ -13,14 +13,14 @@ Our journey begins a few short days after aewens entered the IRC realm of ~team.
As with all worlds, it became with only it's sole inhabitor and very little chaos can be done with only an individual. To rectify this, the gates to the kingdom of #chaos were opened forth to the world (or at the very least, the forum of #meta) and from which two new entities joined the kingom, ben and jan6. As being a new denizen to the IRC realms, aewens began with a slow start laying down the ground works for the kingdom as he figured out the nuances of how this world worked. It was suggested by ben to grant all users with the ability to harness the same power as the king of the kingdom to allow for the maximum amount of chaos to perpetuate throughout the kingdom, and so it was established. However, construction came to an abrupt halt when jan6 took the opportunity to usurp the kingdom as their own to become the new vengeful dictator.
Distraught to see his kingdom so quickly lost, aewens set out to reclaim his crown. It began with diplomatic negotiations, but jan6 would not relinquish the kingdom back to it's rightful heir. And so without any peaceful means to obtain what was rightfully his, aewens began to plot how retake the throne. The beginnings of the plan was simple, pleading through propoganda to the deities of the realm and creating something valuable enough to warrant a trade for the crown. Without anything of value to exchange for the crown initially, aewens began working on what would be an instrumental piece to this story: the bot of Babili.
Distraught to see his kingdom so quickly lost, aewens set out to reclaim his crown. It began with diplomatic negotiations, but jan6 would not relinquish the kingdom back to its rightful heir. And so without any peaceful means to obtain what was rightfully his, aewens began to plot how retake the throne. The beginnings of the plan was simple, pleading through propoganda to the deities of the realm and creating something valuable enough to warrant a trade for the crown. Without anything of value to exchange for the crown initially, aewens began working on what would be an instrumental piece to this story: the bot of Babili.
The concept of using the bot was to provide value to the community, but to banish jan6 from utilizing its resources until the kingdom is returned back to its rightful heir to the throne. During this time, jan6 transitioned from being a vengeful dictator to a false prophet of chaos by attempting to instill rules and order upon the kingdom of chaos. Horrified to see what has become of the once pure chaos of his creation, aewens continued to plead to the deities to hear his prayers and right the wrongs being made. And so the IRC deity, khuxkm, entered the realm to see what was running amok only to continually be cast out by the false prophet. While awaiting for the deities to lay down judgement, aewens was hard at work to provide more functionality and uses to the bot to both appease the deities and to apply further restrictions to jan6.
The concept of using the bot was to provide value to the community, but to banish jan6 from utilizing its resources until the kingdom is returned to its rightful heir to the throne. During this time, jan6 transitioned from being a vengeful dictator to a false prophet of chaos by attempting to instill rules and order upon the kingdom of chaos. Horrified to see what has become of the once pure chaos of his creation, aewens continued to plead to the deities to hear his prayers and right the wrongs being made. And so the IRC deity, khuxkm, entered the realm to see what was running amok only to continually be cast out by the false prophet. While awaiting the deities to lay down judgement, aewens was hard at work to provide more functionality and uses to the bot to both appease the deities and to apply further restrictions to jan6.
However, aewens did not need to wait for jan6's resolve to break to return as the king of #chaos. A fortnight had passed since the initial betrayal and his prayers were heard, khuxkm both enraged by being cast out of the kingdom and from the sin of bringing order into the realm of chaos he dethroned the false prophet, jan6, and set aewens back upon the throne. Outraged by the meddling of the gods in the affairs of mere mortals, jan6 cursed the deities for their acts of foul play but heard nothing but the chortles of joy as the kingdom's one and true heir had returned. It was a time for celebration as chaos was restored and there was a brief period of what passes for peace throughout the realm.
While peace was returned to the kingdom of #chaos, it was not to stay. As the days went by, jan6 continued to curse the deities and demand for the actions to be undone. While his demands fell upon deaf ears as he lost favor from the deities, aewens listened with consideration and was struck with inspiration. While once his enemy, aewens was willing to set aside his rivalry in the name of chaos, and so he brought forth a proposal to the deities. To adhere to the maximum amount of chaos in the kingdom of #chaos, there would be a random event where the crown becomes a free-for-all to whoever could retrieve it first. The deities enjoyed this proposal and so it became law that at the whim of the deities they can initiate the race for the crown.
Once this law came to pass, the crown passed hands back and forth between jan6 and aewens for control over #chaos. But much like many wars, one side will change the game by introducing a new element that shifts the balance of the scales. The shift in power being when aewens trained the bot of Babili to wait until it hears the declaration that the race for the crown has begun and to snatch up the crown to bestow to it's maker. However, much like when aewens was previously crowned by another, jan6 cried out in frustration to this and declared it must be the workings of the deities rather than to accept the bot as the source of crown's bestowal. While funny at first, aewens took pride in his creation and set forth to make the workings of the bot made public for all to see, so that when the next race to the crown begins, jan6 and all else who wishes to take the crown from it's rightful heir will know exactly who they are messing with.
Once this law came to pass, the crown passed hands back and forth between jan6 and aewens for control over #chaos. But much like many wars, one side will change the game by introducing a new element that shifts the balance of the scales. The shift in power being when aewens trained the bot of Babili to wait until it hears the declaration that the race for the crown has begun and to snatch up the crown to bestow to its maker. However, much like when aewens was previously crowned by another, jan6 cried out in frustration to this and declared it must be the workings of the deities rather than to accept the bot as the source of crown's bestowal. While funny at first, aewens took pride in his creation and set forth to make the workings of the bot made public for all to see, so that when the next race to the crown begins, jan6 and all else who wishes to take the crown from its rightful heir will know exactly who they are messing with.
Long live the king!
Long live the king!

@ -20,10 +20,10 @@ this includes ascii art and/or figlet output. please be considerate.
bot commands belong in #bots. please limit yourself to 2 or 3 commands at a time. spamming commands is unacceptable and subject to the consequences below.
## don't be lazy - read the documentation
if people tell you to read the documentation then you should do so. never say: "i'm too lazy. come on. you all know what i need to do. just tell me what i need to do." this will get you ignored for all eternity. however you can expect to be told where to find the documentation. but if you get an url then get it and read it. if the documentation is too technical or you don't understand certain sections then say: "i have now read chapter 3.1 of the url you gave me and i understand how virtual domains work in general. but how would i use both virtual and non-virtual domains together?"
if people tell you to read the documentation then you should do so. never say: "i'm too lazy. come on. you all know what i need to do. just tell me what i need to do." this will get you ignored for all eternity. however, you can expect to be told where to find the documentation. but if you get an url then get it and read it. if the documentation is too technical, or you don't understand certain sections then say: "i have now read chapter 3.1 of the url you gave me and i understand how virtual domains work in general. but how would i use both virtual and non-virtual domains together?"
## unintended rudeness
sometimes you may feel that others are rude. you may get a response like "reinstall the package. restart the service. read the /usr/share/doc/mysoftware/readme." although this is a very brief reply it is likely not meant to be rude. irc is often like human interaction without all the friendly bits. other people have probably answered your question a dozen of times today and they just want to help you solve the problem - not become close friends with you. don't be offended by it. the people don't mean it.
sometimes you may feel that others are rude. you may get a response like "reinstall the package. restart the service. read the /usr/share/doc/mysoftware/readme." although this is a very brief reply it is likely not meant to be rude. irc is often like human interaction without all the friendly bits. other people have probably answered your question a dozen of times today, and they just want to help you solve the problem - not become close friends with you. don't be offended by it. the people don't mean it.
## try to not repeat yourself
asking the same question every minute is annoying. if anyone in the channel isn't paying attention then they will neither read you the second and third time. and those who came back from lunch or sleep will likely see in their "lastlog" what has happened lately. this is too demanding.
@ -49,11 +49,11 @@ be considerate to your fellow tildizens, take [accountability](user_accountabili
# consequences
* first offenses will be handled with a kick from the channel with an explanation of the undesirable behavior. at this point, it's acceptable to rejoin.
* second offenses will be handled with a 1 hour tempban. following the tempban, an irc/chan op will check in and let you know what kinds of behaviors to avoid.
* third offenses will be the same as second, but with a 24 hour tempban period.
* third offenses will be the same as second, but with a 24-hour tempban period.
if the undesirable behavior continues, further methods (up to and including a permanent ban) will be discussed among the oper team.
if you have something that requires oper attention, please send an email to opers at tilde dot chat.
if you have something that requires oper attention, please email opers at tilde dot chat.
# Shared Strike Policy
@ -63,7 +63,7 @@ Users' continuing problematic behavior that has been previously addressed will s
This means that:
* User warned about bad behavior in one chan
* User can be kicked in chan two when continuing behavior there
* User received a 1 hour ban in one chan
* User received a 1-hour ban in one chan
* User can earn an increased ban (say 2hr) in chan two when repeating said behavior there
* A user is permabanned (ex. harassment, continual arguing, persistent trolling, etc.)
* When continuing behavior in a second chan, they can be permabanned there also

@ -25,13 +25,13 @@ You will get sent a confirmation email, which will have a code in it. You must t
## Logging in
Once connected to IRC, you can then login using the following:
Once connected to IRC, you can then log in using the following:
/msg nickserv identify MySuperAwesomePassword
## automatic signin with sasl and certfp
we support authenticating to services via sasl and certfp:
we support authenticating via sasl and certfp:
see the libera.chat [guide](https://libera.chat/guides/sasl) for your
specific client. the basic idea is that you will want to set your sasl username
@ -51,7 +51,7 @@ If you've forgotten your password, you can use the RESETPASS command to send you
/msg nickserv help resetpass
If you still know you password and just want to change it, you can use the SET command:
If you still know your password and just want to change it, you can use the SET command:
/msg nickserv help set password

@ -25,17 +25,17 @@ plaintext to localhost port 6667 from there.
once you're connected, try `/map` to see the servers listed fully.
| server | location | hoster | notes |
|---|---|---|---|
| aussie.tilde.chat | australia | [aussies.space](https://aussies.space/) | |
| bsd.tilde.chat | germany | [bsd.tilde.team](https://bsd.tilde.team/) | |
| club.tilde.chat | quebec | [tilde.club](https://tilde.club/) | |
| cosmic.tilde.chat | london | [cosmic.voyage](https://cosmic.voyage/) | |
| ctrl-c.tilde.chat | new york | [ctrl-c.club](http://ctrl-c.club) | |
| hub.tilde.chat | quebec | [ben](https://tilde.team/~ben/) | services, [website](https://tilde.chat), and [mumble](mumble://tilde.chat) live here |
| institute.tilde.chat | germany | [tilde.institute](https://tilde.institute/) | not available on localhost currently |
| team.tilde.chat | quebec | [tilde.team](https://tilde.team/) | |
| texto-plano.tilde.chat | chile | [texto-plano.xyz](https://texto-plano.xyz/) | |
| thunix.tilde.chat | germany | [thunix](https://thunix.net) | |
| town.tilde.chat | toronto | [tilde.town](https://tilde.town/) | only accessible from localhost on port 7766; no external connections |
| server | location | hoster | notes |
|------------------------|-----------|---------------------------------------------|--------------------------------------------------------------------------------------|
| aussie.tilde.chat | australia | [aussies.space](https://aussies.space/) | |
| bsd.tilde.chat | germany | [bsd.tilde.team](https://bsd.tilde.team/) | |
| club.tilde.chat | quebec | [tilde.club](https://tilde.club/) | |
| cosmic.tilde.chat | london | [cosmic.voyage](https://cosmic.voyage/) | |
| ctrl-c.tilde.chat | new york | [ctrl-c.club](http://ctrl-c.club) | |
| hub.tilde.chat | quebec | [ben](https://tilde.team/~ben/) | services, [website](https://tilde.chat), and [mumble](mumble://tilde.chat) live here |
| institute.tilde.chat | germany | [tilde.institute](https://tilde.institute/) | not available on localhost currently |
| team.tilde.chat | quebec | [tilde.team](https://tilde.team/) | |
| texto-plano.tilde.chat | chile | [texto-plano.xyz](https://texto-plano.xyz/) | |
| thunix.tilde.chat | germany | [thunix](https://thunix.net) | |
| town.tilde.chat | toronto | [tilde.town](https://tilde.town/) | only accessible from localhost on port 7766; no external connections |

@ -2,7 +2,7 @@
author: ~demure
published: true
title: Self Accountability
descripion: A User Guide to help with Self Accountability
description: A User Guide to help with Self Accountability
category:
- main
---
@ -58,18 +58,18 @@ There are a few key points related to Self Accountability. While cases will vary
5. Apologize for the issue
When we take Ownership of an issue by stating the above points, they don't necessarily need to be individual sentences.
ie: its fairly simple to acknowledge our involvement while identify what happened.
ie: it's fairly simple to acknowledge our involvement while identify what happened.
## Accepting Responsibility
Once we have taken time to reflect on what has happened, we need to tell our fellow community members.
Using the above [outline](#outline), make a statement and take Ownership of the issue.
If this issue is somewhat personal, it is quite appropriate to to have one-on-one discussion(s) with those impacted.
If this issue is somewhat personal, it is quite appropriate to have one-on-one discussion(s) with those impacted.
If the issue was public, do try to make a short statement publicly anyway, so that others are aware that the issue is being worked on.
### Small Stuff
Sometimes we can do Small Stuff. It's pretty quick an painless to say:
Sometimes we can do Small Stuff. It's pretty quick and painless to say:
"Oops, I'm sorry."

Loading…
Cancel
Save