Discourse.APK
-
To be fair, the JSON bit has been fairly stable from what I've seen. Which makes sense, any major changes would require changing all the templates that use that particular bit of JSON.
-
Since you are all useless I decided to create a
BasicUserclass and inheritUserfrom that. It will be aQObjectas a consequence.Well, ok, @riking inspired me to do that. And @Buddy gave me that list of tags. And @tar opened this topic I hijacked. But other than that you are all useless!
Filed under: If I ever run into memory problems due to QObject overhead I can always rewrite it in EFL later on
-
But other than that you are all useless!
Hey, I selflessly gave you a topic to discuss this in—that's got to count for something!
-
Fixed. I humbly present my apology to you, oh great and wonderful one.
-
I'd love to know how sanitized the ‘censorship character’ field is—it's admin only, so I figure it could potentially be on the honor system—it'd be cool if, instead of a single character, we could replace each letter with a script that inserts a random character from
{!,@,#,$,%,^,&,*}at its location.
-
I'd probably be willing to work with the Java side of things if you need some help with that. I develop for Android on my free time...
This is supposed to be in reply to @onyx, but I failed to click the right reply button...
-
It's literally the string [spoiler]"belgium|elgiu"[/spoiler]
-
Yeah, what is elgiu?
-
No, I'm talking about how the ‘■’ character is admin-choosable (wait, or did I imagine that? Too lazy to look it up).
-
If it is, it isn't anywhere in the json file this thread is about.
-
Nope, it isn't.
-
This thread is about an .apk file, not a .json file...
-
Um, I thought this thread was about the official Discourse app for Android?
-
<aww> :'(
-
But no! It was a fake official Discourse app!
(Seriously, I need a better
:scare_chord:than:fa_music:...)
-
But is it officially a fake official Discourse app?
-
-
But is it officially a fake official Discourse app?
Is @sam's pronouncement official enough? I thought so.
-
it'd be cool if, instead of a single character, we could replace each letter with a script that inserts a random character from
{!,@,#,$,%,^,&,*}at its location.No, I'm talking about how the ‘■’ character is admin-choosable (wait, or did I imagine that? Too lazy to look it up).
No. It's not - at least I've not seen anything that makes that customisable.
-
No. It's not - at least I've not seen anything that makes that customisable.
-
Whoa, does that mean if a forum censors "..." and a user posts something with "..." in it, the forum will censor every 3-letter word in the post?
-
Not... quite. The top one will mangle that part of the regex, so you need to find some way to get it to match.
-
Censoring
...would match a literal...and then do as/\b...\b/■■■/g
-
Oh, so it seems that
RegExp.escapedoesn't exist in JS. Of course.
-
We could test it by adding
b.....m(or[bB].....[mM]) to the censored words list...
-
It passes the
iflag, so those would be identical, except that the second would be harder to trigger accidentally.
-
Just repeat the same thing you did on line 9 on line 17. It'll be fine.
-
We could test it by adding b.....m (or [bB].....[mM]) to the censored words list...
But that's an admin thang, not really considered abuse, more like failure to RTFM...
Ah - I see.
Irregardless it's not doing what's expected:
We had a baptism in the bedroom of my house in Belgium, where the trees in the garden were in blossom. I almost died of boredom.
Then again, preview while editing:
-
Advance warning - that third censorious word won't be staying there that long.
-
that third censorious word won't be staying there that long.
Aww... that would be fun...
:(Although it'd be more fun if it actually worked...
b.....m
Edit: Hmm, it presented as censored for a split second, then revealed itself...
-
b.....m? Boredom? They block out in preview. Guess we identified the bug in the JS version and it's not in the ruby version of the censoring code?
-
Actually, them not working at all in ruby-baked suggests there's a different bug in the ruby code...
-
bedroom b.....m
Yup, definitely a client/server side sync issue. Maybe different JS regex libraries?
-
different JS regex libraries
But... JS supports regex natively? What smegging libraries? o.O
-
-
I thought of a new censor regex which might be fun:
[CDEIORSUcdeiorsu][CDEIORSUcdeiorsu][CDEIORSUcdeiorsu][CDEIORSUcdeiorsu][CDEIORSUcdeiorsu][CDEIORSUcdeiorsu][CDEIORSUcdeiorsu][CDEIORSUcdeiorsu][CDEIORSUcdeiorsu]What it will censor is left as an exercise for the reader...
:D
-
What it will censor is left as an exercise for the reader...
“Sorceress”? I don't think I want this censored:
[spoiler]
[/spoiler]Well… not too much…
-
Sorceress? I don't think I want this censored:
I don't want this spoiler-tagged thing to be censored either...
