home.social

#identi-ca — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #identi-ca, aggregated by home.social.

fetched live
  1. Jupiter Rowland @[email protected] ·
    @Chao-c'
    The wiki reveals even different timeline:

    "The wiki" sounds funny to someone who has three wikis of his own on his Hubzilla channel. Anyway...

    To me, it seems, that Gargon simply was not as colossal nerd, as others, and somehow managed to create cult following of sufficient number of users, which were not really techies.

    Gargron simply was lucky.

    I think it was in 2016 already that German tech media got interested in decentralised alternatives to corporate silos. Mastodon caught their interest, being developed in Germany and all. Pleroma didn't, in spite of being developed in Germany, too, not to mention more feature-rich than Mastodon. Friendica was developed in Germany back then already, too, but it seemed like either tech media weren't interested in alternatives to something that needed alternatives much more than Twitter, or Friendica managed to continue to fly under the radar even then.

    Anyway, Mastodon got media coverage, and nothing else did.

    In 2017, right-wingers started attacking furries and queers on Twitter. They had to escape somewhere. Tumblr wasn't it, having been pretty much killed by being bought out and G-rated. But someone happened to know Mastodon due to the media coverage whereas nobody happened to know Pleroma due to no media coverage at all. So those furries and queers escaped to Mastodon. "Awoo" was briefly part of Mastodon's culture in the late 2010s due to the high furry-to-non-furry rate.

    From then on, Mastodon had the two advantages of past media coverage and more users. The rest was like a snowball, essentially. The more users something has, the more users something gains by inviting them.

    I guess Friendica and Hubzilla, both of which already existed back then, suffered from the same choice of mindsets: "If you build it, they will come," "We'll first need to get this and that fixed before we're ready for prime time," "Can't someone else take care of that? I'm bad at advertising stuff!" Plus, of course, people who really were bad at advertising stuff to anyone who's neither a developer nor a server admin.

    I was thinking about need for decentralized social media since at least 2009, as I was watching the old web to slowly loose any relevance. (My Facebook account was canceled without any explanations as soon as perhaps sometimes like 2010?).

    In 2009, there already was StatusNet. Granted, it was so obscure that vastly more people knew the "lighthouse server" Identi.ca than StatusNet itself. StatusNet supported the Twitter client API, but there were vastly more mobile apps that were hard-coded to Identi.ca than such where you could choose a StatusNet server because the huge majority of those who knew Identi.ca didn't even know it was part of a network. Identi.ca held some 90% of all StatusNet users.

    By the way, what killed StatusNet was when Identi.ca changed its backend from StatusNet to pump.io and its protocol from OStatus to ActivityPump, thus becoming incompatible with the rest of StatusNet. What remained was largely unable to stand alone. What kind of helped Identi.ca (OStatus as a profile sucked so badly that Evan and Erin themselves had to whip up ActivityPump) did the opposite to StatusNet. A bit later, the FSF scooped it up, forked it to GNU social and eventually merged what was left of StatusNet into GNU social. It got ActivityPub support later on, but it's gone now, too.

    Also, in 2010, Mistpark was around, and so was diaspora* (or what already existed of it at that time). diaspora* had tons of advance publicity due to its crowdfunding stunt, but then the four devs didn't manage to deliver before public interest had faded away, even with Mike's help on the protocol (not even kidding here). And speaking of Mike, he built Mistpark, but almost nobody came because he did nothing in terms of advertising. Even though Mistpark of May, 2010 was more powerful than diaspora* is today. Even though Mistpark took two months for a public alpha and four for a stable point release whereas it took diaspora* years to go beyond alpha, not to mention the entire development team being replaced.

    I guess you would have been a prime Friendica user candidate. Particularly, you would have been one of those who were happy on a Friendica node without the performance-hogging Facebook connector in times when everyone was seeking out and piling onto the nodes with that connector, just to see them close registration at not even 150 accounts.

    I was thinking about basing it on bunch of combined RSS feeds, the publicly compatible vs. the activity stream, which is not so different from from like ActivityPub is made today, except that signing of content with public keys is more advanced concept, that what I was able to imagine.

    Well, they say that ActivityPub is glorified RSS with a rubbery spec.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Pleroma #StatusNet #Identi.ca #GNUsocial #Friendica #Hubzilla #OStatus #ActivityPump #ActivityPub
    #cwfediversemeta #fediversemeta #activitypump #activitypub #cwlongpost #cwfedimeta
  2. Jupiter Rowland @[email protected] ·
    @Chao-c'
    The wiki reveals even different timeline:

    "The wiki" sounds funny to someone who has three wikis of his own on his Hubzilla channel. Anyway...

    To me, it seems, that Gargon simply was not as colossal nerd, as others, and somehow managed to create cult following of sufficient number of users, which were not really techies.

    Gargron simply was lucky.

    I think it was in 2016 already that German tech media got interested in decentralised alternatives to corporate silos. Mastodon caught their interest, being developed in Germany and all. Pleroma didn't, in spite of being developed in Germany, too, not to mention more feature-rich than Mastodon. Friendica was developed in Germany back then already, too, but it seemed like either tech media weren't interested in alternatives to something that needed alternatives much more than Twitter, or Friendica managed to continue to fly under the radar even then.

    Anyway, Mastodon got media coverage, and nothing else did.

    In 2017, right-wingers started attacking furries and queers on Twitter. They had to escape somewhere. Tumblr wasn't it, having been pretty much killed by being bought out and G-rated. But someone happened to know Mastodon due to the media coverage whereas nobody happened to know Pleroma due to no media coverage at all. So those furries and queers escaped to Mastodon. "Awoo" was briefly part of Mastodon's culture in the late 2010s due to the high furry-to-non-furry rate.

    From then on, Mastodon had the two advantages of past media coverage and more users. The rest was like a snowball, essentially. The more users something has, the more users something gains by inviting them.

    I guess Friendica and Hubzilla, both of which already existed back then, suffered from the same choice of mindsets: "If you build it, they will come," "We'll first need to get this and that fixed before we're ready for prime time," "Can't someone else take care of that? I'm bad at advertising stuff!" Plus, of course, people who really were bad at advertising stuff to anyone who's neither a developer nor a server admin.

    I was thinking about need for decentralized social media since at least 2009, as I was watching the old web to slowly loose any relevance. (My Facebook account was canceled without any explanations as soon as perhaps sometimes like 2010?).

    In 2009, there already was StatusNet. Granted, it was so obscure that vastly more people knew the "lighthouse server" Identi.ca than StatusNet itself. StatusNet supported the Twitter client API, but there were vastly more mobile apps that were hard-coded to Identi.ca than such where you could choose a StatusNet server because the huge majority of those who knew Identi.ca didn't even know it was part of a network. Identi.ca held some 90% of all StatusNet users.

    By the way, what killed StatusNet was when Identi.ca changed its backend from StatusNet to pump.io and its protocol from OStatus to ActivityPump, thus becoming incompatible with the rest of StatusNet. What remained was largely unable to stand alone. What kind of helped Identi.ca (OStatus as a profile sucked so badly that Evan and Erin themselves had to whip up ActivityPump) did the opposite to StatusNet. A bit later, the FSF scooped it up, forked it to GNU social and eventually merged what was left of StatusNet into GNU social. It got ActivityPub support later on, but it's gone now, too.

    Also, in 2010, Mistpark was around, and so was diaspora* (or what already existed of it at that time). diaspora* had tons of advance publicity due to its crowdfunding stunt, but then the four devs didn't manage to deliver before public interest had faded away, even with Mike's help on the protocol (not even kidding here). And speaking of Mike, he built Mistpark, but almost nobody came because he did nothing in terms of advertising. Even though Mistpark of May, 2010 was more powerful than diaspora* is today. Even though Mistpark took two months for a public alpha and four for a stable point release whereas it took diaspora* years to go beyond alpha, not to mention the entire development team being replaced.

    I guess you would have been a prime Friendica user candidate. Particularly, you would have been one of those who were happy on a Friendica node without the performance-hogging Facebook connector in times when everyone was seeking out and piling onto the nodes with that connector, just to see them close registration at not even 150 accounts.

    I was thinking about basing it on bunch of combined RSS feeds, the publicly compatible vs. the activity stream, which is not so different from from like ActivityPub is made today, except that signing of content with public keys is more advanced concept, that what I was able to imagine.

    Well, they say that ActivityPub is glorified RSS with a rubbery spec.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Pleroma #StatusNet #Identi.ca #GNUsocial #Friendica #Hubzilla #OStatus #ActivityPump #ActivityPub
    #cwfediversemeta #fediversemeta #activitypump #activitypub #cwlongpost #cwfedimeta
  3. Jupiter Rowland @[email protected] ·
    @Chao-c'
    The wiki reveals even different timeline:

    "The wiki" sounds funny to someone who has three wikis of his own on his Hubzilla channel. Anyway...

    To me, it seems, that Gargon simply was not as colossal nerd, as others, and somehow managed to create cult following of sufficient number of users, which were not really techies.

    Gargron simply was lucky.

    I think it was in 2016 already that German tech media got interested in decentralised alternatives to corporate silos. Mastodon caught their interest, being developed in Germany and all. Pleroma didn't, in spite of being developed in Germany, too, not to mention more feature-rich than Mastodon. Friendica was developed in Germany back then already, too, but it seemed like either tech media weren't interested in alternatives to something that needed alternatives much more than Twitter, or Friendica managed to continue to fly under the radar even then.

    Anyway, Mastodon got media coverage, and nothing else did.

    In 2017, right-wingers started attacking furries and queers on Twitter. They had to escape somewhere. Tumblr wasn't it, having been pretty much killed by being bought out and G-rated. But someone happened to know Mastodon due to the media coverage whereas nobody happened to know Pleroma due to no media coverage at all. So those furries and queers escaped to Mastodon. "Awoo" was briefly part of Mastodon's culture in the late 2010s due to the high furry-to-non-furry rate.

    From then on, Mastodon had the two advantages of past media coverage and more users. The rest was like a snowball, essentially. The more users something has, the more users something gains by inviting them.

    I guess Friendica and Hubzilla, both of which already existed back then, suffered from the same choice of mindsets: "If you build it, they will come," "We'll first need to get this and that fixed before we're ready for prime time," "Can't someone else take care of that? I'm bad at advertising stuff!" Plus, of course, people who really were bad at advertising stuff to anyone who's neither a developer nor a server admin.

    I was thinking about need for decentralized social media since at least 2009, as I was watching the old web to slowly loose any relevance. (My Facebook account was canceled without any explanations as soon as perhaps sometimes like 2010?).

    In 2009, there already was StatusNet. Granted, it was so obscure that vastly more people knew the "lighthouse server" Identi.ca than StatusNet itself. StatusNet supported the Twitter client API, but there were vastly more mobile apps that were hard-coded to Identi.ca than such where you could choose a StatusNet server because the huge majority of those who knew Identi.ca didn't even know it was part of a network. Identi.ca held some 90% of all StatusNet users.

    By the way, what killed StatusNet was when Identi.ca changed its backend from StatusNet to pump.io and its protocol from OStatus to ActivityPump, thus becoming incompatible with the rest of StatusNet. What remained was largely unable to stand alone. What kind of helped Identi.ca (OStatus as a profile sucked so badly that Evan and Erin themselves had to whip up ActivityPump) did the opposite to StatusNet. A bit later, the FSF scooped it up, forked it to GNU social and eventually merged what was left of StatusNet into GNU social. It got ActivityPub support later on, but it's gone now, too.

    Also, in 2010, Mistpark was around, and so was diaspora* (or what already existed of it at that time). diaspora* had tons of advance publicity due to its crowdfunding stunt, but then the four devs didn't manage to deliver before public interest had faded away, even with Mike's help on the protocol (not even kidding here). And speaking of Mike, he built Mistpark, but almost nobody came because he did nothing in terms of advertising. Even though Mistpark of May, 2010 was more powerful than diaspora* is today. Even though Mistpark took two months for a public alpha and four for a stable point release whereas it took diaspora* years to go beyond alpha, not to mention the entire development team being replaced.

    I guess you would have been a prime Friendica user candidate. Particularly, you would have been one of those who were happy on a Friendica node without the performance-hogging Facebook connector in times when everyone was seeking out and piling onto the nodes with that connector, just to see them close registration at not even 150 accounts.

    I was thinking about basing it on bunch of combined RSS feeds, the publicly compatible vs. the activity stream, which is not so different from from like ActivityPub is made today, except that signing of content with public keys is more advanced concept, that what I was able to imagine.

    Well, they say that ActivityPub is glorified RSS with a rubbery spec.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Pleroma #StatusNet #Identi.ca #GNUsocial #Friendica #Hubzilla #OStatus #ActivityPump #ActivityPub
    #cwfediversemeta #fediversemeta #activitypump #activitypub #cwlongpost #cwfedimeta
  4. Jupiter Rowland @[email protected] ·
    @Chao-c'
    The wiki reveals even different timeline:

    "The wiki" sounds funny to someone who has three wikis of his own on his Hubzilla channel. Anyway...

    To me, it seems, that Gargon simply was not as colossal nerd, as others, and somehow managed to create cult following of sufficient number of users, which were not really techies.

    Gargron simply was lucky.

    I think it was in 2016 already that German tech media got interested in decentralised alternatives to corporate silos. Mastodon caught their interest, being developed in Germany and all. Pleroma didn't, in spite of being developed in Germany, too, not to mention more feature-rich than Mastodon. Friendica was developed in Germany back then already, too, but it seemed like either tech media weren't interested in alternatives to something that needed alternatives much more than Twitter, or Friendica managed to continue to fly under the radar even then.

    Anyway, Mastodon got media coverage, and nothing else did.

    In 2017, right-wingers started attacking furries and queers on Twitter. They had to escape somewhere. Tumblr wasn't it, having been pretty much killed by being bought out and G-rated. But someone happened to know Mastodon due to the media coverage whereas nobody happened to know Pleroma due to no media coverage at all. So those furries and queers escaped to Mastodon. "Awoo" was briefly part of Mastodon's culture in the late 2010s due to the high furry-to-non-furry rate.

    From then on, Mastodon had the two advantages of past media coverage and more users. The rest was like a snowball, essentially. The more users something has, the more users something gains by inviting them.

    I guess Friendica and Hubzilla, both of which already existed back then, suffered from the same choice of mindsets: "If you build it, they will come," "We'll first need to get this and that fixed before we're ready for prime time," "Can't someone else take care of that? I'm bad at advertising stuff!" Plus, of course, people who really were bad at advertising stuff to anyone who's neither a developer nor a server admin.

    I was thinking about need for decentralized social media since at least 2009, as I was watching the old web to slowly loose any relevance. (My Facebook account was canceled without any explanations as soon as perhaps sometimes like 2010?).

    In 2009, there already was StatusNet. Granted, it was so obscure that vastly more people knew the "lighthouse server" Identi.ca than StatusNet itself. StatusNet supported the Twitter client API, but there were vastly more mobile apps that were hard-coded to Identi.ca than such where you could choose a StatusNet server because the huge majority of those who knew Identi.ca didn't even know it was part of a network. Identi.ca held some 90% of all StatusNet users.

    By the way, what killed StatusNet was when Identi.ca changed its backend from StatusNet to pump.io and its protocol from OStatus to ActivityPump, thus becoming incompatible with the rest of StatusNet. What remained was largely unable to stand alone. What kind of helped Identi.ca (OStatus as a profile sucked so badly that Evan and Erin themselves had to whip up ActivityPump) did the opposite to StatusNet. A bit later, the FSF scooped it up, forked it to GNU social and eventually merged what was left of StatusNet into GNU social. It got ActivityPub support later on, but it's gone now, too.

    Also, in 2010, Mistpark was around, and so was diaspora* (or what already existed of it at that time). diaspora* had tons of advance publicity due to its crowdfunding stunt, but then the four devs didn't manage to deliver before public interest had faded away, even with Mike's help on the protocol (not even kidding here). And speaking of Mike, he built Mistpark, but almost nobody came because he did nothing in terms of advertising. Even though Mistpark of May, 2010 was more powerful than diaspora* is today. Even though Mistpark took two months for a public alpha and four for a stable point release whereas it took diaspora* years to go beyond alpha, not to mention the entire development team being replaced.

    I guess you would have been a prime Friendica user candidate. Particularly, you would have been one of those who were happy on a Friendica node without the performance-hogging Facebook connector in times when everyone was seeking out and piling onto the nodes with that connector, just to see them close registration at not even 150 accounts.

    I was thinking about basing it on bunch of combined RSS feeds, the publicly compatible vs. the activity stream, which is not so different from from like ActivityPub is made today, except that signing of content with public keys is more advanced concept, that what I was able to imagine.

    Well, they say that ActivityPub is glorified RSS with a rubbery spec.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Pleroma #StatusNet #Identi.ca #GNUsocial #Friendica #Hubzilla #OStatus #ActivityPump #ActivityPub
    #long #cwlong #ostatus #pleroma #hubzilla #mastodon
  5. Jupiter Rowland @[email protected] ·
    @Chao-c'
    The wiki reveals even different timeline:

    "The wiki" sounds funny to someone who has three wikis of his own on his Hubzilla channel. Anyway...

    To me, it seems, that Gargon simply was not as colossal nerd, as others, and somehow managed to create cult following of sufficient number of users, which were not really techies.

    Gargron simply was lucky.

    I think it was in 2016 already that German tech media got interested in decentralised alternatives to corporate silos. Mastodon caught their interest, being developed in Germany and all. Pleroma didn't, in spite of being developed in Germany, too, not to mention more feature-rich than Mastodon. Friendica was developed in Germany back then already, too, but it seemed like either tech media weren't interested in alternatives to something that needed alternatives much more than Twitter, or Friendica managed to continue to fly under the radar even then.

    Anyway, Mastodon got media coverage, and nothing else did.

    In 2017, right-wingers started attacking furries and queers on Twitter. They had to escape somewhere. Tumblr wasn't it, having been pretty much killed by being bought out and G-rated. But someone happened to know Mastodon due to the media coverage whereas nobody happened to know Pleroma due to no media coverage at all. So those furries and queers escaped to Mastodon. "Awoo" was briefly part of Mastodon's culture in the late 2010s due to the high furry-to-non-furry rate.

    From then on, Mastodon had the two advantages of past media coverage and more users. The rest was like a snowball, essentially. The more users something has, the more users something gains by inviting them.

    I guess Friendica and Hubzilla, both of which already existed back then, suffered from the same choice of mindsets: "If you build it, they will come," "We'll first need to get this and that fixed before we're ready for prime time," "Can't someone else take care of that? I'm bad at advertising stuff!" Plus, of course, people who really were bad at advertising stuff to anyone who's neither a developer nor a server admin.

    I was thinking about need for decentralized social media since at least 2009, as I was watching the old web to slowly loose any relevance. (My Facebook account was canceled without any explanations as soon as perhaps sometimes like 2010?).

    In 2009, there already was StatusNet. Granted, it was so obscure that vastly more people knew the "lighthouse server" Identi.ca than StatusNet itself. StatusNet supported the Twitter client API, but there were vastly more mobile apps that were hard-coded to Identi.ca than such where you could choose a StatusNet server because the huge majority of those who knew Identi.ca didn't even know it was part of a network. Identi.ca held some 90% of all StatusNet users.

    By the way, what killed StatusNet was when Identi.ca changed its backend from StatusNet to pump.io and its protocol from OStatus to ActivityPump, thus becoming incompatible with the rest of StatusNet. What remained was largely unable to stand alone. What kind of helped Identi.ca (OStatus as a profile sucked so badly that Evan and Erin themselves had to whip up ActivityPump) did the opposite to StatusNet. A bit later, the FSF scooped it up, forked it to GNU social and eventually merged what was left of StatusNet into GNU social. It got ActivityPub support later on, but it's gone now, too.

    Also, in 2010, Mistpark was around, and so was diaspora* (or what already existed of it at that time). diaspora* had tons of advance publicity due to its crowdfunding stunt, but then the four devs didn't manage to deliver before public interest had faded away, even with Mike's help on the protocol (not even kidding here). And speaking of Mike, he built Mistpark, but almost nobody came because he did nothing in terms of advertising. Even though Mistpark of May, 2010 was more powerful than diaspora* is today. Even though Mistpark took two months for a public alpha and four for a stable point release whereas it took diaspora* years to go beyond alpha, not to mention the entire development team being replaced.

    I guess you would have been a prime Friendica user candidate. Particularly, you would have been one of those who were happy on a Friendica node without the performance-hogging Facebook connector in times when everyone was seeking out and piling onto the nodes with that connector, just to see them close registration at not even 150 accounts.

    I was thinking about basing it on bunch of combined RSS feeds, the publicly compatible vs. the activity stream, which is not so different from from like ActivityPub is made today, except that signing of content with public keys is more advanced concept, that what I was able to imagine.

    Well, they say that ActivityPub is glorified RSS with a rubbery spec.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Pleroma #StatusNet #Identi.ca #GNUsocial #Friendica #Hubzilla #OStatus #ActivityPump #ActivityPub
    #cwfediversemeta #fediversemeta #activitypump #activitypub #cwlongpost #cwfedimeta
  6. Stefan Bohacek @[email protected] ·

    Happy 18th anniversary to the very first fediverse post, courtesy of @evan!

    web.archive.org/web/2008061816

    identi.ca/evan/note/Y0QwGyc1QY

    #fediverse #identica #anniversary #FirstPost

    #fediverse #identica #anniversary #firstpost
  7. Stefan Bohacek @[email protected] ·

    Happy 18th anniversary to the very first fediverse post, courtesy of @evan!

    web.archive.org/web/2008061816

    identi.ca/evan/note/Y0QwGyc1QY

    #fediverse #identica #anniversary #FirstPost

    #fediverse #identica #anniversary #firstpost
  8. Stefan Bohacek @[email protected] ·

    Happy 18th anniversary to the very first fediverse post, courtesy of @evan!

    web.archive.org/web/2008061816

    identi.ca/evan/note/Y0QwGyc1QY

    #fediverse #identica #anniversary #FirstPost

    #fediverse #identica #anniversary #firstpost
  9. Stefan Bohacek @[email protected] ·

    Happy 18th anniversary to the very first fediverse post, courtesy of @evan!

    web.archive.org/web/2008061816

    identi.ca/evan/note/Y0QwGyc1QY

    #fediverse #identica #anniversary #FirstPost

    #firstpost #anniversary #identica #fediverse
  10. Stefan Bohacek @[email protected] ·

    Happy 18th anniversary to the very first fediverse post, courtesy of @evan!

    web.archive.org/web/2008061816

    identi.ca/evan/note/Y0QwGyc1QY

    #fediverse #identica #anniversary #FirstPost

    #fediverse #identica #anniversary #firstpost
  11. Memo @[email protected] ·

    @MadeliefEnLeed

    Da sind ja noch einige „Leichen“ gelistet, und ja, ich bin seit 2008, oft mit eigenen Instanzen, im #Fediverse. ¯\_(ツ)_/¯

    Zuerst auf #Identica,  #Pumpio, #StatusNet, #GnuSocial und #Misskey bis vor kurzem noch mit eigenen #Mastodon und #Diaspora Instanzen.

    Seit dem 1. April (kein Scherz) gibt es allerdings nur noch zwei Konten. Eines auf Mastodon:

    mastodon.online/@memo

    und eines auf Diaspora: 

    diaspora-fr.org/people/5bab36d

    Alles andere kann tatsächlich weg. 😀

    #fediverse #identica #pumpio #statusnet #gnusocial #misskey
  12. Memo @[email protected] ·

    @MadeliefEnLeed

    Da sind ja noch einige „Leichen“ gelistet, und ja, ich bin seit 2008, oft mit eigenen Instanzen, im #Fediverse. ¯\_(ツ)_/¯

    Zuerst auf #Identica,  #Pumpio, #StatusNet, #GnuSocial und #Misskey bis vor kurzem noch mit eigenen #Mastodon und #Diaspora Instanzen.

    Seit dem 1. April (kein Scherz) gibt es allerdings nur noch zwei Konten. Eines auf Mastodon:

    mastodon.online/@memo

    und eines auf Diaspora: 

    diaspora-fr.org/people/5bab36d

    Alles andere kann tatsächlich weg. 😀

    #fediverse #identica #pumpio #statusnet #gnusocial #misskey
  13. Memo @[email protected] ·

    @MadeliefEnLeed

    Da sind ja noch einige „Leichen“ gelistet, und ja, ich bin seit 2008, oft mit eigenen Instanzen, im #Fediverse. ¯\_(ツ)_/¯

    Zuerst auf #Identica,  #Pumpio, #StatusNet, #GnuSocial und #Misskey bis vor kurzem noch mit eigenen #Mastodon und #Diaspora Instanzen.

    Seit dem 1. April (kein Scherz) gibt es allerdings nur noch zwei Konten. Eines auf Mastodon:

    mastodon.online/@memo

    und eines auf Diaspora: 

    diaspora-fr.org/people/5bab36d

    Alles andere kann tatsächlich weg. 😀

    #fediverse #identica #pumpio #statusnet #gnusocial #misskey
  14. Memo @[email protected] ·

    @MadeliefEnLeed

    Da sind ja noch einige „Leichen“ gelistet, und ja, ich bin seit 2008, oft mit eigenen Instanzen, im #Fediverse. ¯\_(ツ)_/¯

    Zuerst auf #Identica,  #Pumpio, #StatusNet, #GnuSocial und #Misskey bis vor kurzem noch mit eigenen #Mastodon und #Diaspora Instanzen.

    Seit dem 1. April (kein Scherz) gibt es allerdings nur noch zwei Konten. Eines auf Mastodon:

    mastodon.online/@memo

    und eines auf Diaspora: 

    diaspora-fr.org/people/5bab36d

    Alles andere kann tatsächlich weg. 😀

    #diaspora #mastodon #misskey #gnusocial #statusnet #pumpio
  15. Memo @[email protected] ·

    @MadeliefEnLeed

    Da sind ja noch einige „Leichen“ gelistet, und ja, ich bin seit 2008, oft mit eigenen Instanzen, im #Fediverse. ¯\_(ツ)_/¯

    Zuerst auf #Identica,  #Pumpio, #StatusNet, #GnuSocial und #Misskey bis vor kurzem noch mit eigenen #Mastodon und #Diaspora Instanzen.

    Seit dem 1. April (kein Scherz) gibt es allerdings nur noch zwei Konten. Eines auf Mastodon:

    mastodon.online/@memo

    und eines auf Diaspora: 

    diaspora-fr.org/people/5bab36d

    Alles andere kann tatsächlich weg. 😀

    #fediverse #identica #pumpio #statusnet #gnusocial #misskey
  16. Adhidarma Hadiwinoto :verifyc: @[email protected] ·

    Wondering kawan-kawan lama waktu zaman #identica 15 tahun yang lalu (kayaknya) bagaimana kabar mereka ya.

    #identica
  17. Adhidarma Hadiwinoto :verifyc: @[email protected] ·

    Wondering kawan-kawan lama waktu zaman #identica 15 tahun yang lalu (kayaknya) bagaimana kabar mereka ya.

    #identica
  18. Sergio Lima @[email protected] ·

    #fediverso #identica #Friendica

    Minha publicação mais antiga (e ainda disponível) no #fediverso foi feita em 04-06-2009, 17 anos atrás!

    No identi.ca (do @evan ). Como não há permalink, você tem que rolar a tela (rolagem infinita) até chegar a primeira publicação (última de cima para baixo).

    identi.ca/ticseducacao, que foi o nickname que usei no Twitter (2009-2023) e no Identi.ca (2009 -2020). O identi.ca era um clone federado (e melhor) do twitter.

    Mas vou poupar o seu trabalho de rolar tela e colocar uma captura de tela da minha primeira publicação no mesmo (a url citada na publicação não existe mais)!

    O interessante é que minha primeira instalação do Friendica (que perdi) eu configurei para replicar as publicações no identi.ca. Então tenho uma cópia de várias publicações que fiz na minha primeira instalação do #Friendica neste perfil!

    #fediverso #friendica #identica
  19. Sergio Lima @[email protected] ·

    #fediverso #identica #Friendica

    Minha publicação mais antiga (e ainda disponível) no #fediverso foi feita em 04-06-2009, 17 anos atrás!

    No identi.ca (do @evan ). Como não há permalink, você tem que rolar a tela (rolagem infinita) até chegar a primeira publicação (última de cima para baixo).

    identi.ca/ticseducacao, que foi o nickname que usei no Twitter (2009-2023) e no Identi.ca (2009 -2020). O identi.ca era um clone federado (e melhor) do twitter.

    Mas vou poupar o seu trabalho de rolar tela e colocar uma captura de tela da minha primeira publicação no mesmo (a url citada na publicação não existe mais)!

    O interessante é que minha primeira instalação do Friendica (que perdi) eu configurei para replicar as publicações no identi.ca. Então tenho uma cópia de várias publicações que fiz na minha primeira instalação do #Friendica neste perfil!

    #fediverso #friendica #identica
  20. Sergio Lima @[email protected] ·

    #fediverso #identica #Friendica

    Minha publicação mais antiga (e ainda disponível) no #fediverso foi feita em 04-06-2009, 17 anos atrás!

    No identi.ca (do @evan ). Como não há permalink, você tem que rolar a tela (rolagem infinita) até chegar a primeira publicação (última de cima para baixo).

    identi.ca/ticseducacao, que foi o nickname que usei no Twitter (2009-2023) e no Identi.ca (2009 -2020). O identi.ca era um clone federado (e melhor) do twitter.

    Mas vou poupar o seu trabalho de rolar tela e colocar uma captura de tela da minha primeira publicação no mesmo (a url citada na publicação não existe mais)!

    O interessante é que minha primeira instalação do Friendica (que perdi) eu configurei para replicar as publicações no identi.ca. Então tenho uma cópia de várias publicações que fiz na minha primeira instalação do #Friendica neste perfil!

    #fediverso #friendica #identica
  21. Sergio Lima @[email protected] ·

    #fediverso #identica #Friendica

    Minha publicação mais antiga (e ainda disponível) no #fediverso foi feita em 04-06-2009, 17 anos atrás!

    No identi.ca (do @evan ). Como não há permalink, você tem que rolar a tela (rolagem infinita) até chegar a primeira publicação (última de cima para baixo).

    https://identi.ca/ticseducacao, que foi o nickname que usei no Twitter (2009-2023) e no Identi.ca (2009 -2020). O identi.ca era um clone federado (e melhor) do twitter.

    Mas vou poupar o seu trabalho de rolar tela e colocar uma captura de tela da minha primeira publicação no mesmo (a url citada na publicação não existe mais)!

    O interessante é que minha primeira instalação do Friendica (que perdi) eu configurei para replicar as publicações no identi.ca. Então tenho uma cópia de várias publicações que fiz na minha primeira instalação do #Friendica neste perfil!

    #identica #friendica #fediverso
  22. Sergio Lima @[email protected] ·

    #fediverso #identica #Friendica

    Minha publicação mais antiga (e ainda disponível) no #fediverso foi feita em 04-06-2009, 17 anos atrás!

    No identi.ca (do @evan ). Como não há permalink, você tem que rolar a tela (rolagem infinita) até chegar a primeira publicação (última de cima para baixo).

    identi.ca/ticseducacao, que foi o nickname que usei no Twitter (2009-2023) e no Identi.ca (2009 -2020). O identi.ca era um clone federado (e melhor) do twitter.

    Mas vou poupar o seu trabalho de rolar tela e colocar uma captura de tela da minha primeira publicação no mesmo (a url citada na publicação não existe mais)!

    O interessante é que minha primeira instalação do Friendica (que perdi) eu configurei para replicar as publicações no identi.ca. Então tenho uma cópia de várias publicações que fiz na minha primeira instalação do #Friendica neste perfil!

    #fediverso #friendica #identica
  23. Jupiter Rowland @[email protected] ·
    CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
    So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

    #[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)

    Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

    Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

    Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

    On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

    #Hashtag

    Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

    On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

    #Hashtag

    Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

    But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

    The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

    Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

    But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

    You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

    This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

    Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

    Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

    When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

    Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

    So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

    And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

    I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte
    #cwfediversemeta #fediversemeta #cwhashtagmeta #iceshrimpnet #iceshrimpjs #hashtagmeta
  24. Jupiter Rowland @[email protected] ·
    CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
    So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

    #[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)

    Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

    Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

    Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

    On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

    #Hashtag

    Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

    On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

    #Hashtag

    Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

    But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

    The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

    Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

    But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

    You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

    This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

    Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

    Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

    When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

    Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

    So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

    And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

    I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte
    #cwfediversemeta #fediversemeta #cwhashtagmeta #iceshrimpnet #iceshrimpjs #hashtagmeta
  25. Jupiter Rowland @[email protected] ·
    CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
    So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

    #[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)

    Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

    Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

    Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

    On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

    #Hashtag

    Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

    On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

    #Hashtag

    Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

    But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

    The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

    Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

    But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

    You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

    This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

    Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

    Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

    When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

    Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

    So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

    And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

    I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte
    #cwfediversemeta #fediversemeta #cwhashtagmeta #iceshrimpnet #iceshrimpjs #hashtagmeta
  26. Jupiter Rowland @[email protected] ·
    CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
    So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

    #[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)

    Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

    Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

    Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

    On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

    #Hashtag

    Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

    On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

    #Hashtag

    Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

    But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

    The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

    Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

    But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

    You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

    This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

    Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

    Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

    When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

    Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

    So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

    And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

    I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte
    #x #long #forte #forkey #akkoma #cwlong
  27. Jupiter Rowland @[email protected] ·
    CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
    So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

    #[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)

    Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

    Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

    Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

    On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

    #Hashtag

    Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

    On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

    #Hashtag

    Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

    But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

    The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

    Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

    But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

    You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

    This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

    Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

    Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

    When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

    Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

    So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

    And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

    I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte
    #cwfediversemeta #fediversemeta #cwhashtagmeta #iceshrimpnet #iceshrimpjs #hashtagmeta
  28. Jupiter Rowland @[email protected] ·
    @「 Jürgen 」:fedi_mastodon:
    Irgendwie ist das doch nicht die „übliche“ Verwendung von Hashtags in Beiträgen. Was ist der Hintergrund bei Hubzilla, dass das so gehandhabt wird?

    Das hat Hubzilla geerbt von Friendica, weil es umgebaut wurde aus einem Fork eines Forks von Friendica. Und Friendica hat es übernommen von StatusNet, weil es von vornherein mit StatusNet föderieren sollte. Und StatusNet hat es geerbt von Identi.ca.

    Sie alle handhab(t)en Hashtags intern als Schlüsselwörter, die keine Raute enthalten. Und sie stellen die Raute außerhalb des Link vor den Link, um zu signalisieren: Das hier ist ein Hashtag. Wenn man einen Post, einen Kommentar oder eine DM verschickt, wird aus dem Hashtag automatisch ein entsprechendes Konstrukt aus ungelinkter Raute plus Link aufs Schlüsselwort generiert.

    Das ist wie bei Namen: Auf allen war bzw. ist das @ kein Teil irgendeines Namen, nicht des Kurznamen, nicht des Langnamen. Der Kurzname, der Teil des Profil-Link ist, hat auch kein @. Guck dir mal deine Erwähnung an: Das @ ist nicht Teil des Link, sondern steht vorm Link, und dein Langname ist erwähnt.

    Warum "die" das anders gemacht haben als auf Twitter und Mastodon? Ganz einfach: Weil "die" das vor Mastodon gemacht haben. Eigentlich sogar noch vor Twitter.

    Identi.ca und StatusNet waren von 2008. Etwa acht Jahre vor Mastodon. Das war der eigentliche Urknall des Fediverse. Und StatusNet hatte meines Wissens damals schon offizielle Unterstützung für Hashtags.

    Warum hat es das nun anders gemacht als Twitter? Weil es das vor Twitter gemacht hat.

    Es war nämlich erst 2009, daß Chris Messina offiziell Unterstützung für Hashtags bei Twitter eingeführt hat. Evan Prodromou, der Erfinder von Identi.ca, StatusNet und dem Fediverse, konnte unmöglich etwa ein Jahr im voraus ahnen, wie Twitter mal Hashtags implementieren wird. Und die Twitter-Entwickler dürften damals überhaupt nicht gewußt haben, daß auch nur Identi.ca existiert, geschweige denn, wie es Hashtags handhabt.

    Friendica ging im Mai 2010 an den Start, etwa fünf Jahre und acht Monate vor Mastodon. Friendica basierte zwar auf einem eigenen Protokoll, war aber von vornherein in der Lage, sich mit StatusNet über dessen eigenes OStatus-Protokoll zu verbinden. Praktischerweise hat der Friendica-Erfinder Mike Macgirvin gleich Identi.cas und StatusNets Handhabung von Hashtags übernommen. Zu diesem Zeitpunkt hatte Twitter Hashtags erst seit gut zehn Monaten.

    Ende 2011 hat Mike Macgirvin Friendica geforkt, dann den Fork geforkt und diesen Fork namens Red (später Red Matrix) dann ab 2012 komplett umgeschrieben. Zu diesem Zeitpunkt handhabte alles im Fediverse Hashtags noch auf dieselbe Art.

    Um diese Zeit wurde StatusNet nach GNU social hardgeforkt, das wohl versuchte, mehr wie Twitter zu sein. Daher wurden auch die Hashtags wie auf Twitter ausgeführt: mit der Raute als Teil des Schlüsselworts und als Teil des Link. StatusNet verlor dann nach der 2012er Umstellung von Identi.ca auf pump.io seine Entwicklungsgrundlage und wurde 2013 kurzerhand nach GNU social gemerget, ohne aber die Hashtags wieder auf die alte Form umzustellen.

    Im März 2015 wurde erstmals Hubzilla veröffentlicht, das entstanden war, indem die Red Matrix umbenannt und massiv erweitert worden war.

    Erst im Januar 2016 kam dann Mastodon, Pleroma kurze Zeit später. Weil beide ursprünglich alternative Frontends für GNU social sein sollten, übernahmen sie von GNU social die Twitter-Hashtags.

    Zu diesem Zeitpunkt sahen weder die neuen Entwickler, die Friendica seit Ende 2011 hatte, noch Mike Macgirvin es ein, warum sie ihre Software unbedingt an Mastodon anpassen sollten. Mike, der inzwischen zwei Nachfahren von Hubzilla betreut, sieht es bis heute nicht ein. Eher baut er serverseitige Gegenmittel gegen Mastodon in seine Software ein.

    Misskey landete meines Wissens erst 2018 im Fediverse, nachdem es ActivityPub adoptiert hatte. Das hatte übrigens Hubzilla als erstes, seit Juli 2017, und Mastodon als zweites, seit September.

    #Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Identi.ca #Laconi.ca #StatusNet #GNUsocial #Friendica #Hubzilla #Mastodon #Pleroma #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
    #cwfediversemeta #fediversemeta #cwhashtagmeta #cwlangerpost #hashtagmeta #cwlongpost
  29. kat @[email protected] ·

    good times

    #identica #statusnet

    #identica #statusnet
  30. kat @[email protected] ·

    good times

    #identica #statusnet

    #identica #statusnet
  31. kat @[email protected] ·

    good times

    #identica #statusnet

    #identica #statusnet
  32. kat @[email protected] ·

    good times

    #identica #statusnet

    #statusnet #identica
  33. kat @[email protected] ·

    good times

    #identica #statusnet

    #identica #statusnet
  34. kat @[email protected] ·

    What happened to "Lady Jane" and "Johnny Null" ?

    Didn't they meet via #statusnet / #identica and have a baby ?

    #AncientHistory

    #statusnet #ancienthistory #identica
  35. kat @[email protected] ·

    What happened to "Lady Jane" and "Johnny Null" ?

    Didn't they meet via #statusnet / #identica and have a baby ?

    #AncientHistory

    #statusnet #ancienthistory #identica
  36. kat @[email protected] ·

    What happened to "Lady Jane" and "Johnny Null" ?

    Didn't they meet via #statusnet / #identica and have a baby ?

    #AncientHistory

    #statusnet #ancienthistory #identica
  37. kat @[email protected] ·

    What happened to "Lady Jane" and "Johnny Null" ?

    Didn't they meet via #statusnet / #identica and have a baby ?

    #AncientHistory

    #identica #ancienthistory #statusnet
  38. kat @[email protected] ·

    What happened to "Lady Jane" and "Johnny Null" ?

    Didn't they meet via #statusnet / #identica and have a baby ?

    #AncientHistory

    #identica #statusnet #ancienthistory
  39. Haschek @[email protected] ·

    Hi, I'm new on #Mastodon, but I was in love with decentralized social networks even before the #Fediverse term was created. Remember #Identica? ;)

    Not many posts here yet, just a quick intro:

    * I post in german (native) & english (german).
    * topics: #photography, #music, #politics, #stupidjokes.
    * I test also #Pixelfed at @[email protected] & @[email protected]

    My old proprietary accounts for reference:

    * instagram.com/h45ch3k/
    * x.com/haschek

    #mastodon #fediverse #identica #photography #music #politics
  40. Haschek @[email protected] ·

    Hi, I'm new on #Mastodon, but I was in love with decentralized social networks even before the #Fediverse term was created. Remember #Identica? ;)

    Not many posts here yet, just a quick intro:

    * I post in german (native) & english (german).
    * topics: #photography, #music, #politics, #stupidjokes.
    * I test also #Pixelfed at @[email protected] & @[email protected]

    My old proprietary accounts for reference:

    * instagram.com/h45ch3k/
    * x.com/haschek

    #photography #music #politics #stupidjokes #pixelfed #mastodon
  41. Haschek @[email protected] ·

    Hi, I'm new on #Mastodon, but I was in love with decentralized social networks even before the #Fediverse term was created. Remember #Identica? ;)

    Not many posts here yet, just a quick intro:

    * I post in german (native) & english (german).
    * topics: #photography, #music, #politics, #stupidjokes.
    * I test also #Pixelfed at @[email protected] & @[email protected]

    My old proprietary accounts for reference:

    * instagram.com/h45ch3k/
    * x.com/haschek

    #photography #music #politics #stupidjokes #pixelfed #mastodon
  42. Haschek @[email protected] ·

    Hi, I'm new on #Mastodon, but I was in love with decentralized social networks even before the #Fediverse term was created. Remember #Identica? ;)

    Not many posts here yet, just a quick intro:

    * I post in german (native) & english (german).
    * topics: #photography, #music, #politics, #stupidjokes.
    * I test also #Pixelfed at @[email protected] & @[email protected]

    My old proprietary accounts for reference:

    * instagram.com/h45ch3k/
    * x.com/haschek

    #pixelfed #stupidjokes #politics #music #photography #identica
  43. Haschek @[email protected] ·

    Hi, I'm new on #Mastodon, but I was in love with decentralized social networks even before the #Fediverse term was created. Remember #Identica? ;)

    Not many posts here yet, just a quick intro:

    * I post in german (native) & english (german).
    * topics: #photography, #music, #politics, #stupidjokes.
    * I test also #Pixelfed at @[email protected] & @[email protected]

    My old proprietary accounts for reference:

    * instagram.com/h45ch3k/
    * x.com/haschek

    #mastodon #fediverse #identica #photography #music #politics
  44. Elric Erkose @zoowar ·

    @lohang Hello to you as well. Are you a remnant from ? Your name seems familiar.

    #identica
  45. Elric Erkose @[email protected] ·

    @lohang Hello to you as well. Are you a remnant from #identica? Your name seems familiar.

    #identica
  46. Elric Erkose @[email protected] ·

    @lohang Hello to you as well. Are you a remnant from #identica? Your name seems familiar.

    #identica
  47. Elric Erkose @[email protected] ·

    @lohang Hello to you as well. Are you a remnant from #identica? Your name seems familiar.

    #identica
  48. Elric Erkose @zoowar ·

    @andyc Aspiring since the time of .

    #duffer #identica
  49. Elric Erkose @[email protected] ·

    @andyc Aspiring #duffer since the time of #identica.

    #duffer #identica
  50. Elric Erkose @[email protected] ·

    @andyc Aspiring #duffer since the time of #identica.

    #duffer #identica
  51. Elric Erkose @zoowar ·

    @windigo I'm glad you're active again. I'm trying to recreate my experience here. I'm still having some trouble subscribing to some, others I can't find. Glad I found you.

    #identica #fediverse
  52. Elric Erkose @[email protected] ·

    @windigo I'm glad you're active again. I'm trying to recreate my #identica #fediverse experience here. I'm still having some trouble subscribing to some, others I can't find. Glad I found you.

    #identica #fediverse
  53. Johannes Brakensiek @[email protected] ·

    Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

    #activitypub #ostatus #statusnet #identica #fediverse
  54. Johannes Brakensiek @[email protected] ·

    Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

    #activitypub #ostatus #statusnet #identica #fediverse
  55. Johannes Brakensiek @[email protected] ·

    Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

    #activitypub #ostatus #statusnet #identica #fediverse
  56. Johannes Brakensiek @[email protected] ·

    Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

    #fediverse #identica #statusnet #ostatus #activitypub
  57. Johannes Brakensiek @[email protected] ·

    Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

    #activitypub #ostatus #statusnet #identica #fediverse
  58. Evan Prodromou @[email protected] ·

    Evan Prodromou on OpenChannels.FM

    A quick note that Evan is interviewed by WordPress social networking lead Matthias Pfefferle on the OpenChannels.FM podcast about the history of the Fediverse and where we’re going next. How Decentralized Social Platforms Grew from Identica to Modern-Day Mastodon covers a 15+-year period as the Fediverse was born and developed. The shownotes alone are extremely detailed and a great resource.

    #fedihistory #fediverse #identica #socialweb #wordpress
  59. Evan Prodromou @[email protected] ·

    Evan Prodromou on OpenChannels.FM

    A quick note that Evan is interviewed by WordPress social networking lead Matthias Pfefferle on the OpenChannels.FM podcast about the history of the Fediverse and where we’re going next. How Decentralized Social Platforms Grew from Identica to Modern-Day Mastodon covers a 15+-year period as the Fediverse was born and developed. The shownotes alone are extremely detailed and a great resource.

    #fedihistory #fediverse #identica #socialweb #wordpress
  60. Evan Prodromou @[email protected] ·

    Evan Prodromou on OpenChannels.FM

    A quick note that Evan is interviewed by WordPress social networking lead Matthias Pfefferle on the OpenChannels.FM podcast about the history of the Fediverse and where we’re going next. How Decentralized Social Platforms Grew from Identica to Modern-Day Mastodon covers a 15+-year period as the Fediverse was born and developed. The shownotes alone are extremely detailed and a great resource.

    #fedihistory #fediverse #identica #socialweb #wordpress