Would have been useful if voat was still around. But it's not worth the extra code.
Would have been useful if voat was still around. But it's not worth the extra code.
Just like with immigration, you need to learn to assimilate and not request special accommodations for your culture. If you can't assimilate, then perhaps you shouldn't be here.
Edit: a word.
Just like with immigration, you need to learn to assimilate and not request special accommodations for your culture. If you can't assimilate, then perhaps you shouldn't be here.
Edit: a word.
It always seemed like a sensible thing to me on voat, I thought it might be a good idea here too.
It always seemed like a sensible thing to me on voat, I thought it might be a good idea here too.
DANGER!!! lazy context free regex broke Poal code already! Proof:
Trying to use freestyle posting markup and trying this without using an "at sign" and works, but FAILS using an at sign:
WORKS :
https://worldtruthvideos.org/%40ChristIsKing
but FAILS with "@" due to lazy hack regex this post foolishly recommends :
https://worldtruthvideos.org/@ChristIsKing
No simple way to type this now :
https://worldtruthvideos.org/@ChristIsKing
even using source code block delimitation in markup becuase SOURCE CODE IS TAMPERED WITH (refer to my source code of this post) I did NOT type what you see in the source code block!!! Another second dire bug!
The complex solution :
A workaround would be to type a pedantic link in markup []()...
https://worldtruthvideos.org/@ChristIsKing (worldtruthvideos.org)
Poal is broken now today for links with @ signs in the URL and the URL standard allows that character.
https://tools.ietf.org/html/rfc3986#appendix-A
That shows proof that @ symbol is valid in URLS, and has many alternative purposes in URLs
Poal is broken now today for source code exerts that have things it ought not ever alter bracketed by ~~~
DANGER!!! QUIT BREAKING THE CODE with regex hacks out of context
**DANGER!!! lazy context free regex broke Poal code already! Proof:**
Trying to use freestyle posting markup and trying this without using an "at sign" and works, but FAILS using an at sign:
WORKS :
https://worldtruthvideos.org/%40ChristIsKing
but FAILS with "@" due to lazy hack regex this post foolishly recommends :
https://worldtruthvideos.org/@ChristIsKing
No simple way to type this now :
~~~
https://worldtruthvideos.org/@ChristIsKing
~~~
even using source code block delimitation in markup becuase SOURCE CODE IS TAMPERED WITH (refer to my source code of this post) I did NOT type what you see in the source code block!!! Another second dire bug!
The complex solution :
A workaround would be to type a pedantic link in markup []()...
[https://worldtruthvideos.org/@ChristIsKing](https://worldtruthvideos.org/@ChristIsKing)
Poal is broken now today for links with @ signs in the URL and the URL standard allows that character.
https://tools.ietf.org/html/rfc3986#appendix-A
That shows proof that @ symbol is valid in URLS, and has many alternative purposes in URLs
Poal is broken now today for source code exerts that have things it ought not ever alter bracketed by ~~~
**DANGER!!! QUIT BREAKING THE CODE with regex hacks out of context**
Hi,
Yeah, I found a similar bug where any variation of "bit do" would cause a post to fail.
I don't want to give the impression the above suggestion is an actual code commit or something. For all I know /*/ does horrible things with poals actual regex parser. I just know they had it on voat, it worked and it'd be handy if it were here. Every aggregator site seems to have it's own version of /v/ and it's a pain trying to remember them all.
Hi,
Yeah, I found a similar [bug](https://poal.co/s/Poaldev/252569) where any variation of "bit do" would cause a post to fail.
I don't want to give the impression the above suggestion is an actual code commit or something. For all I know /*/ does horrible things with poals actual regex parser. I just know they had it on voat, it worked and it'd be handy if it were here. Every aggregator site seems to have it's own version of /v/ and it's a pain trying to remember them all.
Every aggregator site seems to have it's own version of /v/
true, but the code of this site has proven fixes applied 4.5 years ago in voat so its code base it at least as recent as the fork they took from voat.co, I regression test probed some of the bugs from 4.5 years ago last night. It cannot survive a "gibberish attack" DDOS if the left or antifa makes it a target, so I think its allowed to live as a honeypot of sorts, despite having better ssl than voat.co
MY LAST POST, goodbye
> Every aggregator site seems to have it's own version of /v/
true, but the code of this site has proven fixes applied 4.5 years ago in voat so its code base it at least as recent as the fork they took from voat.co, I regression test probed some of the bugs from 4.5 years ago last night. It cannot survive a "gibberish attack" DDOS if the left or antifa makes it a target, so I think its allowed to live as a honeypot of sorts, despite having better ssl than voat.co
MY LAST POST, goodbye
Best of luck.
Best of luck.
I concur. It's a nuisance that there is no standard for links.
I concur. It's a nuisance that there is no standard for links.
Could take it a step further and change all "poal.co/*/" links to "poal.co/s/"
Could take it a step further and change all "poal.co/*/" links to "poal.co/s/"
(post is archived)