Yohan Yukiya Seseㆍ사요한・謝雪矢

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

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

©️ License: #CCBySA4
❗ only represent myself

🇵🇭 #Philippines
#Bibliophile #Writer #WebDev

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

🔏 https://youronly.one/p/verified/

#ATmosphere: @youronly.one

#YourOnlyOne #T2pub #fedi22

  • 29 Posts
  • 30 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) { }  
    

    ^_~





  • @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).)



















  • @BeAware@social.beaware.live At first, it’s expected. However, we have to try. If it won’t fly, then it means, at least as far as the “Decentralized, Distributed, Federated, Open, Network” ( #DDFON ) space is concerned, they don’t care if the “migrants” redefine things.

    It happened before… #Web3 was, and still is, about the #OpenSocialWeb but it was hijacked by #cryptocurrency people. And to solidify their control over what “Web3” means, these same people campaigned that OpenSocialWeb is actually Web3.0 (with the point-0 included). And voila, we lost control over “Web3”.

    It’s happening again, with the term “Fediverse” this time. Ironically, some who were being lumped under the “Fediverse” terminology are resisting (like #NOSTR and #ATproto, they prefer to use #NOSTRich and #ATmosphere respectively).

    But, again, like I said introducing a new term has its positives, like in the example I mentioned re: “Baybayin” vs “Surat”/“Suyat”. The latter became the commonly accepted umbrella term instead of the former.

    It’s all about the community. Remember, just a few years ago, the discussion about replacing the term “fediverse” were so common. Yet, when people suggested replacements, no one supported any. It was all complaints, and those who took steps eventually gave up.

    Maybe I will give up one day. Or, maybe not.

    LOL. “DDFON”, I’ve been using that since, I think 2012/2013? And it was only a year or two ago that someone said they like it better than all the other “proposals”. :p


  • @BeAware@social.beaware.live It does… but sometimes we have to, especially in this case when there are some attempts to redefine the word “fediverse” adding even more confusion to it.

    We either have to create a new term and arrange everything in order, or let things be more confusing for the newbies (and media for that matter).

    It’s similar to the native writing script of the Philippines called “Baybayin”. Because of a certain group of people successfully redefined the meaning of “Baybayin”, it became very confusing as an umbrella label, and even became political.

    The solution to appease both sides was to create another umbrella label, which was agreed upon by all parties as “Suyat”. And finally, the endless word war quieted. ^^

    It’s not exactly there to become common, rather, to give some order to things and keep it simple. We’ve tried explaining by using “email” and the “universe, galaxies”, but people still don’t understand. Add to that, those who want to redefine the “fediverse” adding to the confusion. _




  • @BrikoX

    > The ability to opt-out of quote posts is also currently planned, which makes it that Mastodon’s implementation will not be compatible with other fediverse implementations of quote posting.

    Not surprising. Even before ActivityPub was announced, when the #fediverse was still powered by #OStatus, Mastodon was already breaking compatibility. There were countless of heated debates about almost every Mastodon-only “feature” they implemented that all other Fediverse devs were _forced_ to implement.

    And here we are with yet another.

    I wonder what will supporters of opt-out or anti-quotepost camp will do if the other Fediverse devs ignore this Mastodon-only “feature”, and just continue with the common implementation of quote posts? Are we going to see a new reason for “fediblock”, and finally fragment the Fediverse network?