Support pseudonitro (even if just parsing) #61

New issue

Closed

opened 2020-05-17 01:13:43 +00:00 by mary · 1 comment

mary commented

2020-05-17 01:13:43 +00:00

Presumably this is just a regex change to support parsing.
E.g.:

<:owo:425350333544267786> => <&:owo:425350333544267786>
<a:owo:425350333544267786> => <&a:owo:425350333544267786>

Presumably this is just a regex change to support parsing. E.g.: ``` <:owo:425350333544267786> => <&:owo:425350333544267786> <a:owo:425350333544267786> => <&a:owo:425350333544267786> ```

a referenced this issue from a commit

2020-05-28 12:26:58 +00:00

pseudonitro-viewer: Add patch Closes #61

a closed this issue

2020-05-28 12:26:59 +00:00

a commented

2020-05-28 12:30:10 +00:00

Owner

I'm not 100% interested in implementing the sending counterpart at this point, however I will consider it at a future date.

For future Ave:

Rename isavailable or isusable, whichever is used to determine if we can send it, put a func of same name that returns true all the time
Just go to the point where it is converting the emoji to send, call the renamed actual isavailable/isusable, if not, convert as pseudonitro

I'm not 100% interested in implementing the sending counterpart at this point, however I will consider it at a future date. For future Ave: ![](https://lasagna.cat/i/38bmapn4.png) 1) Rename isavailable or isusable, whichever is used to determine if we can send it, put a func of same name that returns true all the time 2) Just go to the point where it is converting the emoji to send, call the renamed actual isavailable/isusable, if not, convert as pseudonitro

This repo is archived. You cannot comment on issues.