Hey nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku your posts always appear on my feed like this 👇 you got a clue why? Probably a client bug, but weirdly it's only your posts.
Anyone else got a clue why?
#asknostr #nostr #nostrdevs
He's using Unicode characters to change the appearance of the text.
𝐋𝐨𝐭𝐬 𝒐𝒇 𝘀𝘁𝘆𝗹𝗲𝘀 𝘢𝘳𝘦 𝕡𝕠𝕤𝕤𝕚𝕓𝕝𝕖.
Your client doesn't render them properly. You may be using a font that doesn't support them.
Cheers man, I get the first bit, but how come my client (yakihonne) doesn't render certain ones? Is it a NIP thing?
That I'm not sure. This has nothing to do with Nostr specifically, Unicode is a much older and broadly used thing. nostr:nprofile1qqs2jwlflvpwgmzqga4gfatfwhd4sd0latv33lajh5pzjpyed5lacrqpr4mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mf0qywhwumn8ghj7mn0wd68ytfsxgh8jcttd95x7mnwv5hxxmmd9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcnq0l4y would be better able to figure out what's happening.
I can see your unicodes characters normally not sure whats happening with the other note, we will investigate this and see how it goes, thanks for the feedback fellas 🙏
seems fine from my end, u r sure u have the latest version installed ?
Seems like an Android issue, we are looking into it, thanks for the feedback
nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku just replied
👍👍👍 thanks again man
Right image this time 🤦♂️
Cheers nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku nostr:npub1m64hnkh6rs47fd9x6wk2zdtmdj4qkazt734d22d94ery9zzhne5qw9uaks
It's likely your font just doesn't support the right characters. Does your phone let you change fonts? What phone is it?
I can see these messages on both my android devices, one stock and one running GrapheneOS.
because of automatic translation. it's not in another language, it's using alternative, latin characters in the utf-8 unicode blocks for visual effects
Ah, is this an android thing then, nowt to do with the client? Guessing I can update/install a wider variety of characters somehow?
i haven't been able to get vitor's attention about this issue, and idk where the automatic translation settings are, if they are anywhere at all.
you might say that this is my counter-attack against the idiotic policy promoted by people like fiatjaf and others saying that kind 1 notes should not contain markdown. they absolutely should, and markdown is readable text, as plaintext, even if the client does not render it, the header prefixes, the asterisk and underscore and other style markers, all make sense in plaintext and have been used for decades in this way in pure plaintext media, like in the days before rich text email.
fix the clients. jumble doesn't break it, some clients like coracle have fonts with inconsistent ascender/descender/body heights that make it look a bit wonky, but with proper chosen fonts there is a visual effect that i am aiming for. i use the smallcaps to spit venom, i use the unicial to speak my thoughts and offer help, and i use the fraktur block to be cryptic, or to quote old texts, conveying the vibe of antiquity.
Man, I love that last paragraph, nice little approach is that. I'll not be adopting it as my brain would fry, but appreciate it ntl.
Re kind 1 note, I don't understand tbh, but from a UX/UI pov, these kind of visual errors shouldn't happen, so I agree, markdown should be included.
If newbs run in to this and don't ask, they'll simply think it's a pile of shite. Not to mention they won't experience your style vibe fonts. Double lose.
ɪ ᴅon'ᴛ reaʟʟʏ mɪnᴅ ɪꜰ ᴘeoᴘʟe mɪss some ᴛʜɪnɢs ʙecause oꜰ cʟɪenᴛs ᴅoɪnɢ ᴛʜɪnɢs auᴛomaᴛɪcaʟʟʏ ᴛʜaᴛ sʜouʟᴅ ʙe oᴘᴛɪonaʟ or sʜouʟᴅ cʟearʟʏ noᴛ aᴘᴘʟʏ. nɪᴘ-01 cʟearʟʏ sᴛaᴛes ᴛʜaᴛ ᴛʜe encoᴅɪnɢ ꜰormaᴛ ɪs sᴛanᴅarᴅ uᴛꜰ-8, wɪᴛʜ ᴛʜe ᴘrɪmarʏ ᴛʏᴘe oꜰ escaᴘɪnɢ ꜰor conᴛroʟ cʜaracᴛers ʟɪᴋe \n \ᴛ \r eᴛc. anʏᴛʜɪnɢ eʟse sʜouʟᴅ ʙe encoᴅeᴅ as \uxxxx or wʜaᴛever ᴛʜe cʟɪenᴛ ᴅev ɪs more comꜰorᴛaʙʟe wɪᴛʜ ʙuᴛ ᴛwo ʜex cʜaracᴛer anᴅ ᴛʜe ꜰunnʏ \xxx ocᴛaʟ ꜰormaᴛ ᴘroʙaʙʟʏ sʜouʟᴅ ʙe exᴘʟɪcɪᴛʟʏ unrecommenᴅeᴅ, ᴛʜe ʟaᴛᴛer esᴘecɪaʟʟʏ ʙecause ɪᴛ's noᴛ weʟʟ suᴘᴘorᴛeᴅ anʏwaʏ (anᴅ mosᴛ ᴘeoᴘʟe ᴅon'ᴛ unᴅersᴛanᴅ wʜaᴛ ocᴛaʟ ɪs unʟess ᴛʜʏ are unɪx ɢeeᴋs, as ᴛʜeʏ are common wɪᴛʜ ꜰɪʟesʏsᴛem ᴘermɪsɪons coᴅes, eɢ 0700 or 650 or sɪmɪʟar coᴅes ꜰor reaᴅ/wrɪᴛe ꜰor ᴅɪrecᴛorɪes anᴅ ꜰɪʟes.
as ꜰor n00ʙs, ᴛʜaᴛ's ᴛʜe ᴛʜɪnɢ, ɪ ᴘroʙaʙʟʏ ᴅon'ᴛ wanᴛ ᴛo ᴛaʟᴋ ᴛo ᴛʜem anʏwaʏ ɪꜰ ᴛʜeʏ ᴅon'ᴛ ɢo "ʜeʏ wᴛꜰ ɪs ᴛʜɪs?" ʙecause ᴘeoᴘʟe wʜo ᴅon'ᴛ wanᴛ ᴛo ᴛaᴋe oᴘᴘorᴛunɪᴛɪes ᴛo ʟearn ᴛenᴅ ᴛo noᴛ ʙe ɪnᴛeresᴛɪnɢ ᴘeoᴘʟe anʏwaʏ.
anʏwaʏ, ꜰor ᴛʜe cʟɪenᴛ ᴅevs wʜo care, ʙecause ɪ'm noᴛ ᴛʜe ꜰɪrsᴛ ᴛo use uᴛꜰ-8 coᴅes ᴛo ᴅo sɪʟʟʏ ᴛʜɪnɢs (ᴘʟenᴛʏ oꜰ ᴘeoᴘʟe use ᴛʜem ꜰor ᴅɪsᴘʟaʏ names), ɪ'm ᴊusᴛ aᴅᴅɪnɢ ᴛo ᴛʜe ᴘɪʟe oꜰ users wʜo use uᴛꜰ-8, anᴅ ᴛʜere ɪs more ᴘurᴘoses ꜰor uᴛꜰ-8 ᴛʜan ᴊusᴛ cʜɪnese/ᴋorean/ᴊaᴘanese/ᴋannaᴅa/cʜeroᴋee/eᴛc wʜɪcʜ are aʟso ᴘarᴛ oꜰ ᴛʜe coᴅe ʙʟocᴋs, wɪᴛʜ non-ʟaᴛɪn cʜaracᴛers. ᴛʜere ɪs aʟso maᴛʜemaᴛɪcaʟ noᴛaᴛɪons ʟɪᴋe ᴛʜe cʟassɪc cursɪve x anᴅ muʟᴛɪᴘʟʏ/ᴅɪvɪᴅe sʏmʙoʟs anᴅ manʏ oᴛʜers.
ɪᴛ's mʏ oᴘɪnɪon ᴛʜaᴛ ᴛʜe converɢence on naᴛɪonaʟ ᴋeʏʙoarᴅ ʟaʏouᴛs anᴅ ᴛʜe usʙ sᴛanᴅarᴅ ᴛʜaᴛ ᴅoesn'ᴛ naᴛɪveʟʏ ʜanᴅʟe uᴛꜰ-8/unɪcoᴅe anᴅ ᴛʜe ʟacᴋ oꜰ ᴅrɪvers, maᴋes ɪᴛ verʏ cʜaʟʟenɢɪnɢ ᴛo ᴅeveʟoᴘ cusᴛom ᴋeʏʙoarᴅs, anᴅ ᴛʜeʏ aɪn'ᴛ exacᴛʟʏ ᴅɪꜰꜰɪcuʟᴛ ᴛo ꜰɪnᴅ or ʙuɪʟᴅ anᴅ cusᴛomɪzɪnɢ ᴛʜem, ɪsn'ᴛ ᴛʜaᴛ ᴛecʜnɪcaʟ, ᴛʜe http://qmk.fm weʙsɪᴛe, anᴅ ᴅevɪces ᴛʜaᴛ ᴛʜe ǫuanᴛum mecʜanɪcaʟ ᴋeʏʙoarᴅ ꜰrameworᴋ suᴘᴘorᴛ, are noᴛ exacᴛʟʏ uncommon anʏmore. wʜaᴛ ɪs uncommon ɪs mʏ orᴛʜoʟɪnear ʟaʏouᴛ, wʜɪcʜ ɪ mucʜ ᴘreꜰer ʙecause ɪ've aʟwaʏs ꜰounᴅ ᴛʜaᴛ ᴛʜe sᴛaɢɢereᴅ sᴛanᴅarᴅ ʟaʏouᴛ (ʟɪᴋe ǫwerᴛʏ, ᴅesɪɢneᴅ ꜰor oʟᴅ ʜammer-anᴅ-ᴛaᴘe ᴛʏᴘewrɪᴛers ꜰrom over 120 ʏears aɢo) neeᴅs ᴛo ᴅɪe, as ɪᴛ causes rsɪ anᴅ ᴊusᴛ ʙecause ᴛʜe maᴊorɪᴛʏ oꜰ ᴘeoᴘʟe ʜunᴛ anᴅ ᴘecᴋ, or use ᴛoucʜscreen ᴋeʏʙoarᴅs, ᴅoesn'ᴛ mean ᴛʜaᴛ ᴛʜere ɪsn'ᴛ a vaʟɪᴅ case ꜰor acᴛuaʟ ᴛoucʜ-ᴛʏᴘɪsᴛ ᴋeʏʙoarᴅs, anᴅ ɪ ᴅon'ᴛ ᴛʜɪnᴋ ᴛʜaᴛ voɪce recoɢnɪᴛɪon ɪs so ɢreaᴛ ᴛʜaᴛ ɪᴛ ɪs worᴛʜ mʏ ᴛɪme ꜰɪᴅᴅʟɪnɢ ᴛo ɢeᴛ ᴛʜaᴛ seᴛ uᴘ, ɪᴛ's aᴛ ʟeasᴛ as comᴘʟex as ᴘroɢrammɪnɢ a ᴋeʏʙoarᴅ anᴅ ᴛraɪnɪnɢ ᴛo ᴛʏᴘe ɪᴛ. ɪe, 2-3 monᴛʜs oꜰ uncomꜰorᴛaʙʟe worᴋ.
I'm definitely in the "ʜeʏ wᴛꜰ ɪs ᴛʜɪs?" group.
A lot of that went over my head tbh, except to say, we do just stick with "things" simply because they are mass adopted, when there's clearly better alternatives.
Also, if its any use to the conversation, nostr:npub1m64hnkh6rs47fd9x6wk2zdtmdj4qkazt734d22d94ery9zzhne5qw9uaks and nostr:npub14ya7n7czu3kyq3m2sn6kjawmtq6ll6kerrlm90gz9yzfjmflmsxq8dsn39, this latest note is all gobbledegook again, whereas the previous was fully readable.
So I pasted it in to an email and its fully readable (lovely quirky font btw).
So I now assume its the client not my android phone.
i know i'm pushing the boundaries with this but it all started with the notion of "death" as in transformation and "death" as in terry pratchett's comical, dry and wry characterization of death, which as i remember when reading the book, felt very resonant with my own personality.
so, i am glad for support in this. it may well be that few can easily set up an input method to make such text, and i have always loved the irish unicial that is the original, and still largely used format used in signage and memorial texts, deserves to be more visible.
i've always hated capitalization because of it depending on me using my weakest fingers, and both of them, thus why you see in ordinary ascii output i generally only use capitals for acronyms and proper names, i've always felt like this was a severe deficiency in modern computer keyboards. i made a custom layout that puts all the important navigation and input keys, arrows, pgup/dn/home/end/bkspc/del/enter/esc but i just could not see myself putting shift there because of my hostility to germanic style all caps, and my preference for unicial.
ɪᴛ'ꜱ ᴘʀᴇᴛᴛɪᴇʀ, ᴀɴᴅ ᴘʀᴇᴛᴛɪᴇʀ ɪꜱ ᴀʟᴡᴀʏꜱ ᴀ ɢᴏᴏᴅ ᴛʜɪɴɢ ꜰᴏʀ ɪᴍᴘʀᴏᴠɪɴɢ ʀᴇᴀᴅᴇʀ'ꜱ ᴇɴᴊᴏʏᴍᴇɴᴛ, ɪɴ ᴍʏ ᴏᴘɪɴɪᴏɴ, ᴛʜᴀᴛ'ꜱ ᴡʜʏ ɪ ᴜꜱᴇ ᴛʜɪꜱ ᴜɴɪᴄɪᴀʟ ʜᴀᴄᴋ ᴛᴏ ᴘᴜᴛ ꜱᴛᴜꜰꜰ ɪɴ ᴛʜᴀᴛ ɪꜱ ᴍᴏꜱᴛ ᴘᴇʀꜱᴏɴᴀʟ ᴀɴᴅ ʜᴇʟᴘꜰᴜʟ.
This user is also using a entirely different app, yakihonne.
It's not because of automatic translation, it would say the message was translated underneath it that were the case. I see your messages fine in Amethyst anyways.
If you want to disable translation either use the fdroid build which doesn't have translation as a feature, or look under "User Settings" in the gplay version. It's been there for months.
i already looked. "don't translate from" ... no options.
1.04.2-play is the version, is that current?
also, amethyst doesn't mangle it.
ok, Vitor is totally off the hook :)
Click it and pick the language to not translate from.
no options for that, but it's not auto-translating anything for me actually.
also, just sayin, but yakihonne absolutely spams the extension signer, something around 50 requests... i had to add a heap of bad client mitigations to stop that, it batches, groups, and blocks more than 100 requests now.
lol, whoever is making yakihonne. middling grade quality for my taste
Ah my bad. You turn off translations directly in the translated note. That setting page let's you re-enable them.
