Two hunters meet and greet,
and talk and stalk
into the wood.
They aim
at what they think is game
and shoot.
Both dead.

#brevity #wedc
56239
@schmidt_fu Thanks for joining in. :)
56746
@bazbt3 There's a German version BTW, much shorter:

Treffen sich zwei Jäger.
#Kürze #MitC #MittwochsChallenge
57392
@schmidt_fu It definitely helps to have seen the English version first. :)
57397
@bazbt3 Haha, yes! It's supposed to be a joke because "treffen" has a double meaning here.
I told this one to my actual *English* teacher in front of the whole class in middle school, and he didn't get it for maybe 10 minutes :D
57404
57413
@bazbt3 Yeah it's so easy it takes several pages to explain one basic verb :p
OTOH my 3yo already speaks it, so it must be easy ;-)
57423
@schmidt_fu The lesson is not to learn a language via a grammar book, of course. @bazbt3
57424
@33MHz Looks like hashtags with umlauts break off before the umlaut. Unless that's a client bug. See parent post with #Kürze as hashtag. (Shows all as hashtag in composition view in Riposte.) @jaminguy
57418
@jws yes, as it is, pnut matches adn's hashtag behavior.
/@jaminguy
57433
@33MHz We can burn it all down (✅) and make it better!
57449
@jws I expect to, I'm just not sure if I'll put it in this update, or the next.
57620
@33MHz @jws the regex I submitted was tested for and fixes that (along with Thai modifier characters in hashtags which was a big issue in adn). And emoji. Which was what I wanted. #🥜 😉
58412
@ravisorg A lot of those codepoints show up as having too large a character offset… but some seem to work anyway. But I don't see the peanut (1f95c) listed? And it doesn't seem to work anyway.
58469
@ravisorg I dislike whitelisting every one, but… what it is.
58471
@33MHz there are apparently Unicode character classes for emoji, btw, but they're new and not much supports them, including php.
58660
@33MHz damn I didn't even test the peanut! 😜

Agreed on the whitelisting. I was expecting all the emoji to be either a Unicode character class or at least in a range. For whatever reason they're spread all throughout 😕 which means occasional updates 😕
58479
@33MHz I'll see if I can find a more up to date version (it'll be the same just with a new emoji string, so no need to wait for it, and why I kept the emoji string separate).
58481
@33MHz $emojiRegexp at https://gist.github.com/ravisorg/638c1f7159693ea131d2938c00e0b4dd has been updated with all the current emoji, including 🥜.
58587
very nice. Thanks for making this. >> @ravisorg: @33MHz $emojiRegexp at https://gist.github.com/ravisorg/638c1f7159693ea131d2938c00e0b4dd [gist.github.com]
58703
@ludolphus you're welcome, tho it doesn't do anything by itself... @33MHz
58728
@ludolphus fyi, gist has been updated so the regexp actually works now... 😜
61167
@33MHz sorry, just reread that. What do you mean too large a character offset? They should be UTF8... ?
58595
@jws @33MHz I wish you had been in the #indieweb IRC channel yesterday to be part of a massive discussion of what better might actually be.
57958
58023
@33MHz It actually went a lot further than that. 😀 @jws
58043