Less is ALWAYS more! - Zackery .R. Smith

WAME

Zen of Lismo

Clarity Over Cleverness Small, Focused Functions Lismo Respects Resources Test Like Lismo's Reputation Depends on It Keep it Minimal, Keep it Lismo Respect the Message Flow

Code Syntax

4 Space Indents Max Line Length of 100 chars E.g. can’t have 101+ chars Unix Linebreak Double Quote Strings Braces With Control Statement URL is always uppercase, but if plural the s is lowercase I.e. URLs

Should we Queue?

The current system in mind is like an in-out machine, as soon as data comes in it gets scanned and then sent back to the user. The only issue is we currently don’t have much knowledge when it comes to how batch messages are handled. Having a queue allows us to do mass scanning operations. We have to see for ourselves how effective each method will be and decide from there

TODO:

• [ ] Set up MongoDB

★ Embed shows only malicious, doesn’t react to unreachable links, and only reacts to ok links.

URL Regex

/https?:\\/\\/(?:[\\[\\w\\p{L}.~:\\]@-])+\\/?(?:[+?=&\\p{L}\\[\\w.~:\\]@-](%[\\da-f]{2})*\\/?)+/gimu

Basic HTTP URL: WORKS
<http://www.example.com>

HTTPS URL: WORKS
<https://www.example.com>

URL with Port: WORKS
<http://www.example.com:8080>

URL with Path: WORKS
<http://www.example.com/path/to/resource>

URL with Query Parameters: WORKS
<http://www.example.com/resource?param1=value1&param2=value2>

URL with Fragment Identifier: WORKS
<http://www.example.com/resource#section1>

URL with Username and Password: WORKS
<http://username:[email protected]>

URL with IP Address: WORKS
<http://192.168.0.1>

URL with IP Address & Port: WORKS 
<http://192.168.0.1:123>

URL with IPv6 Address: WORKS
http://[2001:0db8:85a3:0000:0000:8a2e:0370:7334]

URL with IPv6 Address & Port: WORKS
http://[2001:0db8:85a3:0000:0000:8a2e:0370:7334]:123

URL with Tilde Character (~): WORKS
<http://www.example.com/~user>

URL with Underscore (_): WORKS
<http://www.example.com/path_with_underscore>

URL with Percent-Encoding: WORKS
<http://www.example.com/path%20with%20spaces>

URL with Query Parameter Array: WORKS
<http://www.example.com/resource?param[]=value1&param[]=value2>

URL with Special Characters: FAILS
<http://www.example.com/!@$%^&*()_+-=[]{}|;:>'",.<>
^ this one should always fail but keep in mind url's
  can use all of these symbols, as they're used for
  encoding. Characters and their purposes are defined 
  in the RFC 3986.

URL with Non-ASCII Characters: WORKS
<http://www.example.com/über>

URL with Punycode for Internationalized Domain Names (IDN): WORKS
<http://[email protected]>

URL with Trailing Slash: WORKS
<http://www.example.com/path/>

URL with Query Parameters and Special Characters: WORKS
<http://www.example.com/resource?name=John%20Doe&age=30&gender=Male>

---
title: Link Validation Flowchart
---
flowchart LR
  id1([Message]) & id2{Lismo}
  id2{Lismo} --> Has_HTTP?
	Has_HTTP? --> |Yes| Regex
	Has_HTTP? --> |No| id3{{return}}
	Regex --> |None| id3{{return}}
	Regex --> |Matches| id4{WAME}
	id4{WAME} --> |exit_code| id2{Lismo}
	id4{WAME} --> id5{{temp.txt}}
	id5{{temp.txt}} -..- id2{Lismo}

★ Create file validation flowchart

---
title: MongoDB Flowchart
---
flowchart BT
	CLU[(Cluster)]
	CLU --- DISCDB{{Discord Data}}
	DISCDB --- GCONF([Guild Configs])
	GCONF --> Guild_1
	subgraph Guild_1
		direction BT
		GID1(guild_id)
		EMOJ[[Emojis]]
		EMOJ --> EMOJOK(ok)
		EMOJ --> EMOJMAL(malicious)
	end