mastodon/app/javascript/flavours/glitch/features/compose/util/counter.js

import { urlRegex } from './url_regex';

const urlPlaceholder = '$2xxxxxxxxxxxxxxxxxxxxxxx';

export function countableText(inputText) {
  return inputText
    .replace(urlRegex, urlPlaceholder)
    .replace(/(^|[^\/\w])@(([a-z0-9_]+)@[a-z0-9\.\-]+[a-z0-9]+)/ig, '$1@$3');
}
correct URL pattern used in text length counter in WebUI (#4968) 2017-09-16 13:01:15 +00:00			`import { urlRegex } from './url_regex';`

[Glitch] Update twitter-text from 1.14 to 3.1.0 and fix toot character counting Port 65db2625508c220fd3c0a1f37cdd2e13b6e02987 to glitch-soc Signed-off-by: Claire <claire.github-309c@sitedethib.com> 2021-03-02 11:02:56 +00:00			`const urlPlaceholder = '$2xxxxxxxxxxxxxxxxxxxxxxx';`
Count all URLs in text as 23 characters flat, do not count domain part of usernames (#4427) * Count all URLs in text as 23 characters flat, do not count domain part of usernames * Add new status text counting logic to web UI 2017-07-28 22:06:29 +00:00
			`export function countableText(inputText) {`
			`return inputText`
correct URL pattern used in text length counter in WebUI (#4968) 2017-09-16 13:01:15 +00:00			`.replace(urlRegex, urlPlaceholder)`
Twidere mention workaround (#5552) * Work around Twidere and Tootdon bug Tootdon and Twidere construct @user@domain handles from mentions in toots based solely on the mention text and account URI's domain without performing any webfinger call or retrieving account info from the Mastodon server. As a result, when a remote user has WEB_DOMAIN ≠ LOCAL_DOMAIN, Twidere and Tootdon will construct the mention as @user@WEB_DOMAIN. Now, this will usually resolve to the correct account (since the recommended configuration is to have WEB_DOMAIN perform webfinger redirections to LOCAL_DOMAIN) when processing mentions, but won't do so when displaying them (as it does not go through the whole account resolution at that time). This change rewrites mentions to the resolved account, so that displaying the mentions will work. * Use lookbehind instead of non-capturing group in MENTION_RE Indeed, substitutions with the previous regexp would erroneously eat any preceding whitespace, which would lead to concatenated mentions in the previous commit. Note that users will “lose” up to one character space per mention for their toots, as that regexp is also used to remove the domain-part of mentioned users for character counting purposes, and it also erroneously removed the preceding character if it was a space. 2017-11-07 18:08:14 +00:00			`.replace(/(^\|[^\/\w])@(([a-z0-9_]+)@[a-z0-9\.\-]+[a-z0-9]+)/ig, '$1@$3');`
[Glitch] Run eslint --fix I don't like it changing files this way, but it's basically what c49213f0ea311daba590db1d7a14a641cbd9fe93 and a few others did. 2023-02-03 19:52:07 +00:00			`}`