Yohan Yukiya Sese Cuneta 사요한🦣

Yohan Yukiya Sese Cunetaㆍ사요한・謝雪矢(ゆきや)・謝約翰ㆍיהוחנן

♾️ #ActuallyAutistic 🐬
✨ Appeared: Sports Seoul; The Daily Report Arirang

©️ #CCBySA4
❗ only represent myself

🇵🇭 #Philippines #Filipino
#Bibliophile

🦋 @youronly.one
🧵 @youronly.one.ofcl
🔗 @im.youronly.one

Interests
* #FreeCulture #OpenKnowledge
* #Kosher #Torah
* #Archery #Running
* #Violin #Flute #Ppop #Kpop #Jpop #Cpop
* #Games #Anime #Pdrama #Kdrama #Jdrama

#YourOnlyOne #fedi22

  • 37 Posts
  • 45 Comments
Joined 3 years ago
cake
Cake day: April 29th, 2022

help-circle
















  • @lil5@fosstodon.org

    It’s not “Firefox-only” per se, it’s CSS. Firefox is fast when it comes to implementing updates that benefits multilingual and Asian support, and Chromium is either slow, implements a small part only, or just ignores it completely.

    (aside: Another good example is Ruby annotation. Firefox’s implementation of Ruby is up-to-date while Chromium’s stuck in 2010.

    And this is very very annoying, you have to design for Chromium when it comes to Ruby annotations; or use JavaScript to serve different Ruby codes per browser. Chromium is practically the “modern IE6”.)

    It’s the same with :lang().

    In Chromium, you still have to do it like this:

    :lang(en-GB), :lang(en-US), :lang(en-AU), :lang(en-NZ), :lang(en-PH) { }  
    

    In Firefox you can do it this way:

    :lang(en-GB, en-US, en-AU, en-NZ, en-PH) { }  
    

    or

    :lang("en-GB", "en-US", "en-AU", "en-NZ", "en-PH") { }  
    

    Another example, in Chromium:

    :lang(ceb-Tglg), :lang(pam-Tglg), :lang(fil-Tglg) { }
    
    :lang(ceb-Hano), :lang(pam-Hano), :lang(fil-Hano) { }  
    

    In Firefox:

    :lang(\*-Tglg) { }  
    :lang(\*-Hano) { }  
    

    or

    :lang("*-Tglg) { }  
    :lang("*-Hano) { }  
    

    ^_~










  • @dansup@mastodon.social

    > Let’s agree to disagree respectfully and with common sense.

    Hear hear!

    To add to that, never forget to factor in CCL:

    1. Context
    2. Culture
    3. Language

    Often times, the reports we receive were taken out-of-context. Or, there’s a cultural factor the reporter did not consider. Worse is, language. People forget that even though we speak the same language, English in this case, it does not mean we understand words similarly nor we form sentences and understand these sentences the same way.

    If we combine two or all of these (context, culture, language), it is when we start to understand each other. But failure to do so, we end up taking offense when it never was the intention of the other person (often the “reported”).


  • @Rentlar@lemmy.ca Ahh, yeah, on Lemmy it is the reversed, you get far too much content from the highly active groups, drowing everything else.

    On the microblogging side, that’s the thing, the “Local” / “For You” feed was just meant to see what’s going on. On platforms without an algorithm, it shows everything. But on platforms like Threads, it controls it (but still, if there is barely any data the algorithm can work on, it’s as good as not having any algorithm). So in the end, it goes back to being an end-user effort (or issue) why they see what they don’t want to see, and don’t find what they want to consume.

    For platforms with an algorithm, they have to help the algorithm by providing it data. They need to like, follow, comment, on content they like to see more, instead of randomly interacting. If they don’t change their method, the data will be built upon their random liking/commenting, and then complain about it.

    For platforms without an algorithm, if they kept on following accounts that talks about tech, of course most of what they’ll see are tech. Hence the complaints about “the Fediverse is for developers only” or “the Fediverse is all about politics”.

    Some claim the Fediverse lack moderation tools, yet, people complain about the same things over in The ATmosphere network. How they kept seeing politics or tech mumbo jumbo.

    So, at the end of the day, it’s an end-user effort/issue. The platform developers can only provide so much assistance and tools, but if the end-user doesn’t grow their “observable network” properly, then it won’t work for them regardless which platform they use.

    The “Local”/“For You” feed is just for finding new content, for expanding our network. And yes, if some groups or topics are filling this feed, the server admins should have tools to throttle certain groups or topics, so as not to defeat it’s purpose as a discovery tool. Otherwise, what you shared will indeed happen. (And I guess this is where an algorithm works best, like how it is in Threads (if there is enough data of course).)