youronlyone

joined 2 years ago
[–] [email protected] 2 points 2 days ago

@psycho_[email protected] Haha, but is it, really?

I think it only appears that way because of the massive influx of newbies who are trying to control an (open) web standard; not because it's 16 years already. ^_^

[–] [email protected] 1 points 2 days ago

@[email protected]

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) { }  

^_~

 

Yet another reason why you should use #Firefox

You can use: #BestViewedInFirefox

  • :lang(\*-Hang)
  • :lang("*-Latn)
  • :lang("zh", "ja", ko")
  • :lang(PT, DE, HE)

If you care about multilingual and multi-script support.

#language #lang #HTML #CSS #WebDev #BrowserWars

 

Writing prompt: "16 years later, the #Fediverse is finally mainstream"

Who will take the challenge to write an article about it? Publish it on whichever platform you want, with your own chosen license (preferably Creative Commons).

#ActivityPub #SocialWeb #OpenSocial #MycelialWeb #SNS #SocialMedia #DDFON #Web3

 

The official #Fediverse ( #ActivityPub ) account of the inventor of the #WorldWideWeb #WWW

https://w3c.social/@timbl

#W3C #Internet #CERN #SocialWeb #OpenSocial #OpenSocialWeb #Web #MycelialWeb

[–] [email protected] 1 points 2 weeks ago (1 children)

@[email protected] Yep! That's correct! The father of the Fediverse was Evan Prodromou. He sent the first message in 2008. Later, #identiverse was coined before it eventually became known as the #Fediverse.

[–] [email protected] 2 points 2 weeks ago (3 children)

@[email protected] Yes. The Fediverse started in 2008. ^_^

You can check the page where I've collected it, with links to each.

https://codeberg.org/ddfon/federated-sns

^_^

 

Today #Mozilla announced that Mozilla Social is closing on 2024-12-17. #DidYouKnow that this was their 2nd public #Fediverse instance?

  • 2010-02-22: launch
  • 2011-05-01: renamed to Social@Mozilla
  • 2013-11-20: closed
  • 2023-05-04: launch
  • 2024-12-17: closed

#Trivia #History

 

This is the relationship of the various terminologies ( #SocialWeb #OpenSocialWeb #Fediverse #ATmosphere #NOSTRich ) with each other.

#MycelialWeb #DDFON #TheATmosphere #TheFederation #SNS #SocialMedia

[–] [email protected] 1 points 3 weeks ago

@[email protected] There are indeed, and if it's clear they're being that and showing they're that, it makes moderation and filtration easier. 😅 (On Threads alone, I've blocked a lot of accounts, and I'm thankful they showed their true selves by leaving comments on other people's posts, lol, made it easier.)

The challenge I guess is how they can be easily detected and limit their exposure for everyone. Or, at least for instances where such aocharacter is not welcome.

[–] [email protected] 1 points 3 weeks ago (2 children)

@[email protected]

> 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").

[–] [email protected] 1 points 3 weeks ago (1 children)

@[email protected] 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).)

[–] [email protected] 1 points 3 weeks ago

@[email protected] Yep! I will. Thank you for collecting them!I together! We need it.

(P.s. I suddenly recalled there was an idea about creating mascots. And reminded me of my private list of emojis for each software, LOL.)

[–] [email protected] 1 points 3 weeks ago (3 children)

@[email protected] Do you have an example?

Many argued during Twitter Migration 2.0 that algorithms are important in content discovery. However, in #Threads where there is an algorithm, people still complain how they are seeing things they don't want to see, and not discovering content that they like, and Threads also have a "Not interested" feature on top of the algorithm.

There are also people complaining about the exact same thing about The #ATmosphere network even though they were provided with a lot of moderation and discovery features than most other SNS.

If people are complaining for the same reasons in any of these networks and platforms, is it not because the user is growing their network incorrectly and/or randomly, or lack of it? Because algorithm or not, moderation and discovery tools or not, it's the same complaints.

 

The #Fediverse iconography by @[email protected]

https://fediverse.wake.st

#ActivityPub #icons

 

Seriously, stop blaming the network/platform/software/protocol if you are not seeing the content you want to see, or seeing content you don't want to see.

Every #SNS, or #SocialMedia network, is based on (1) who you follow; and (2) who you and the people you follow interact with.

In other words, what you see and don't see was based on your how you're growing your own network. That is your personal "observable network".

It gets worse in platforms with algorithms because they push far more similar content you wouldn't normally see if you don't have any connection path to those (again, who the people you're following are interacting with).

In platforms without an algorithm, like most #Fediverse software, the closest you can get to something similar is your "Instance timeline/feed" and "Fediverse timeline/feed", which are generally 'hidden' behind another tab/section. Not like in, for example, #Threads, "For You" is the default. ("For You" is currently like the "Instance timeline/feed" but with algorithms.)

If you're seeing too much tech mumbo jumbo, you're probably following a couple of tech accounts. Or, maybe, you're just following one techie account but they're far too active in this type of content.

You want to see more art content, you have to find and follow them. Use hashtags and see who else are using it and follow those accounts you like. Or, if you like things being fed to you through an algorithm, you have to keep feeding that algorithm with keywords so it will learn what you want (again, like in Threads).

What you see and don't see is based on how you're growing your network. It's no different from your offline life, you see and hear only the things people that surrounds you are sharing.

It is not the fault of the software/platform/protocol/instance/algorithm (or lack thereof). It's all about #YOU, you are center of your "observable network". Just like how planet Earth is the center of its own "observable universe".

 

Done with my rounds. Went through 20 pages of accounts, so that's 800 accounts manually checked this evening. ^_~

#moderation #Fediverse #DontMe

 
  • The network based on #ActivityPub (f. OStatus; OpenMicroBlogging) is called the #Fediverse (not #Mastodon )

  • #diaspora protocol is #TheFederation

  • While that running on #Nostr is #NOSTRich

  • And #ATproto is #TheATmosphere / #ATmosphere (not #Bluesky )

Now you know!

 

My #SocialDesktop set up. ^_^

  • Left half: #ThreadsNet
  • Right half: divided between the #Fediverse and “The #ATmosphere ” respectively.

What's yours?

#SocialWeb #OpenSocialWeb #OpenSocial #DDFON #MycelialWeb #SNS #SocialMedia

 

Like it or not, #Mastodon successfully did an #EEE of the #Fediverse as far as API is concerned.

Non-Mastodon software with Mastodon API implemented can be connected to third-party services like brid.gy and fedica.com, to mention a few.

It is rare to see third-party services implement any support for non-Mastodon software using their respective API. #Fedica recently added #Pixelfed support; and a few other alt #frontends support either #Misskey or #Pleroma.

So… yeah, there's no doubt the “competition” is over as far as this particular usage is concerned. Mastodon won, got what it wants. Either implement it and allow your users to use other third-party software… or don't and wait for other developers to support your platform.

Not good, but we have to face the reality sooner rather than later, so we can move forward. Maybe make it part of #ActivityPub 2.0 and finally have a universal fediverse API that all can agree with and use.


This rant/reaction stemmed from this thread: https://makai.chaotic.ninja/notes/9xs35rslyb || https://c.im/@youronlyone/113082194085637021

 

“A Brief History of the Fediverse Symbol” by Sean Tilley

https://wedistribute.org/2024/09/history-fediverse-symbol/

#Fediverse #Logo #Symbol #History #SocialWeb #OpenSocialWeb #DDFON #MycelialWeb #MyceliumNetwork #OpenSocial #ActivityPub

[–] [email protected] 2 points 1 month ago

@[email protected] That's a very good question! Sadly, I haven't received the update on Android yet. T_T

Good thing you mentioned it, I'll pay attention to that once I get the latest beta update from our region.

[–] [email protected] 1 points 1 month ago

@[email protected] @[email protected] I'm a bit confused by your reply.

Other than I never said or imply such, no one has control of the web and that's why we should just push for what we think it should take, regardless if it will be successful or not. It's good to be active than to be passive. Will it be a success or a failure? You will never know until you try it. Whichever the wind goes, you can say later, “I did my part”.

^_^

[–] [email protected] 1 points 1 month ago (2 children)

@[email protected] 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

view more: next ›