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 #Cdrama

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

#YourOnlyOne #T2pub #fedi22

  • 28 Posts
  • 24 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) { }  
    

    ^_~


















  • @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?














  • @RookieNerd @fediverse

    Hmm… There is a misconception on what the #Fediverse is and what is the goal, which unfortunately is what the press are telling people.

    1. The Fediverse is about bringing down the walls (silos / walled-garden).

    2. It never had the goal or objective or vision to replace Twitter, Facebook, Tumblr, Instagram, Flickr, Blogspot.

    The Fediverse software available today are the materialised ideas of developers who believe in a federated SocialWeb, which by the way, is the original #Web3 (not crypto). It goes all the way back to 2005 (probably earlier, I don’t have my notes).

    The goal was to get existing silos to open up and federate.

    It just that, there are more developers who are excited about it, so we started to see serious projects related to the Fediverse. If I remember correctly, Misskey was not a Fediverse project when it first started. So, one would say Misskey was the first non-federation project that joined the fediverse network.

    If these silos don’t federate, it’s fine too, because there are existing software and instances available.

    And it has always been about choice.

    If users want to stay with silo #SNS by all means. The fediverse is not here to replace them, the fediverse is here as an option and as a solution to the issues plaguing silo networks (like ads, privacy, content license, to mention a few).

    That’s what the fediverse is about and always have been to this day. It is never about replacing this and that, or recruiting people to switch over and encourage them to delete their silo SNS accounts. These other things were simply the passion and convictions of the users who migrated and some of the developers who developed fediverse software, it’s not part of the fediverse itself.

    It’s just a protocol. Again, I’ll use email here. If you have a server, you can choose to install your own email software. The protocol is there. Various email software are there. OR, you can just use Yandex or Gmail or Zoho and use the custom domain feature (or use their email hosting services).

    If Twitter and Facebook implement the protocol, hooray! Mission accomplished. If they don’t, that’s fine either.

    So, yeah, people are hating that Instagram will implement the #ActivityPub protocol and join the #Fediverse network. They have valid reasons and it is understandable. However, the fediverse started to be a #WebStandard protocol to allow federation and bring back the #SocialWeb as it was intended to be.

    For us who were there in 2005 already, and when the first Fediverse software and instance came online in 2008, that is still our vision and goal, to bring down the walls of silo SNS.