Effective: [ August 13th, 2025 ] | Last Updated: [ August 13th, 2025 ]
don't be annoying. this means:
IPs/tripcodes may be banned for:
updates posted here.
Effective: August 13th, 2025 | Last Updated: August 13th, 2025
k3y.co is the personal art/project archive of latchk3y (that's me).
Data Type | Purpose | Retention |
---|---|---|
Hashed IP | rate-limiting and blocking abuse | 30 days |
Tripcodes | pseudonymous identity for comments/DMs | never deleted* |
Likes | counting post engagement | indefinitely |
Messages | comments/DMs/commissions | 30 days** |
Banned IP Hashes | blocking abusive users | indefinitely |
* generated by users, irreversible. i don't store your passcode.
** comments stay forever; DMs/commissions purged after 30 days unless needed for ongoing or completed work.
updates posted here.
this list contains a comprehensive guide on how to work with the tags and filters.
most, if not all, of the "specific" parameters are basically carbon copies of the in-built filter functions of pocketbase, so if you're familiar with that, you'll be able to pick up this stuff pretty quickly.
searches are done primarily using tags in most cases, however, there are several different search fields, each of which behave slightly differently, but with a few shared characteristics.
two tags, seperated by a space. will return posts that are tagged both "raccoon" and "fox".
two words that are part of the same tag are seperated by an underscore.
two tags inside of a set of (parenthesis), seperated by a space. all results inside of () must all be true. conversely, if you put your values inside of -(), all results must be false.
returns every post tagged "frog", regardless of any other searches.
return posts that don't have the "anaconda" tag.
so, to put all of that into a compiled form:
this would return all posts tagged "evie_almond" and "butt", while also returning all posts that have "frog" tagged. any post that comes from this group that has the "anaconda" tag is automatically retracted from the final results. the first query set is treated as priority, followed by the second, the third, and so on.
certain keywords have been reserved to help aid in searching. in the "fancy" search, they are accessed simply in the advanced option under the menu, however all options are operational from the search itself.
filters are applied as additional rules to follow when searching for tags, and are applied as absolutes -- this means that every filter value must be met in order for results to appear. i may add the ability in the future to make certain filters optional, but i do not have the intention to do so at this time.
most of the following has been copied directly from the pocketbase documentation on list searching.
the syntax basically follows the format
FIELD
OPERATOR
VALUE,
where:
FIELD :: the field to conduct your query. valid fields are listed further below.
OPERATOR :: the operation to perform on your query. these include:
returns all posts that contain source files.
returns any posts that contains the phrase "tails has such a fat, fuckable asshole" in the description or title.
returns all posts that have more than 2 files connected to it.
the following are valid fields, and which searches they are valid for.
field | description | valid searches |
---|---|---|
id | ID value of the record. | all |
created | date of creation | all |
updated | date of last edit | all |
title | title value of the record. | posts, projects, queue |
description | description value of the record. | posts, projects |
ask | related ask record ID. | posts |
rating | record's rating, defined as either "everyone", "mature", or "adult". | posts, projects, queue |
files | related files by filename. can also be queried for length via files:length. | posts |
updates | related files by filename. can also be queried for length via files:length. | projects, queue |
srcfile | related source file by filename. | posts |
tags | related tags by tag ID. it's usually easier to use tagged for this, as you can use the actual word with that. | posts, projects, queue |
message | message value of record | comments |
author | related author ID | posts, comments |
tripfag | related tripfag by name. this must be an exact match. | comments |
name | related name | comments |
by default, certain tags are hidden. to see these tags in your results, you must either edit your blacklist (found in the ADVANCED OPTIONS menu), which will be saved as a cookie, or add ~ to the front of any of the tags listed below.
CUSTOM NAME | set a specific name to display with your comment. defaults to "LocalFailure". |
---|---|
TRIPCODE | generate a consistent unique name and color by entering a code. if used with Custom Name, tripcode color is applied. |
*text* | text |
---|---|
**text** | text |
[text](https://k3y.co/) (site links) |
text |
[text](https://x.com/latchk3y) (external links) |
text |
 |
![]() |
>text | >text |
>>17 or [reply:17] |

- item placed at the start of the line becomes:
name | evan almond |
---|---|
age | 28 |
~h | header blocks. |
---|---|
~cN | how much space should be used for a block, where N is the number of columns. |