Search
562 results for “maegul”
-
@maegul
Fedi Film Club? That sounds cool. Reminds me of the #MastodonBadMovieClub 😎 -
-
@maegul @Johannes Ernst To be fair, something like "mobile identity" already exists. In the Fediverse. Not as an experimental proof-of-concept, but in stable daily use for longer than Mastodon has even been around.
It's called "nomadic identity". It was created by @Mike Macgirvin 🖥️ in 2011 with his Zot protocol and first implemented by himself in 2012 in the Red Matrix which became Hubzilla in 2015. It's also part of the Nomad protocol, a successor of Zot, upon which Mike's latest creations commonly referred to as (streams) is based.
Nomadic identity allows you to have your channel (similar to what an account is just about everywhere else) on multiple server instances at the same time. Not backup-like static copies, but identical clones which are being kept in sync in near-real-time.
In case any of you don't know yet: Both can use ActivityPub as well, and they're federated with Mastodon. I'm actually writing this from a Hubzilla channel that has one spare clone.
Also, both Hubzilla and (streams) have bidirectional support for another creation of Mike's, a single-sign-on system named OpenWebAuth which automatically recognises your login on compatible instances.
The obvious catch is that neither of these features are available anywhere else, at least not to this extent. Hubzilla and (streams) are the only nomadic federated server applications, and they're also the only ones that with server-side OpenWebAuth support which means that they can recognise OpenWebAuth logins from elsewhere.
And it's safe to say that what doesn't exist on Mastodon may be seen as non-existent in the Fediverse altogether.
CC: @Ben Pate 🤘 @Laurens Hof @Vicki Boykis
#Long #LongPost #CWLong #CWLongPost #Fediverse #NomadicIdentity #OpenWebAuth #Hubzilla #Streams -
@maegul @chrisoffner3d @michaelsfuhrer Something similar to #lk99 happened when the #BICEP2 team announced signals of cosmic inflation in the cosmic microwave background. Essentially all the world experts descended on a Facebook group of all places & thrashed it out collegially. Also in the pandemic when experts thrashed out droplet vs aerosol transmission and there was a paradigm change in real time played out on arXiv & Twitter.
-
@maegul @hrefna Innovation my asp. #stocktonrush was in a hurry to exploit deep sea mining & he didn’t have the money or investors to do it properly. His solution? Put the lives of people at risk. It was greed, entitlement, & a desperate need to be as well-known as Branson or Elon. #titan #titanic
-
@maegul @Jeff Sikes @Kainoa @Chris Trottier This would have to happen on the server side. And this, in turn, would work the best if it happened directly on the instance servers, and if it was part of the #Fediverse projects themselves.
We've seen what happens when you rely on a third party. It tends to lean towards something centralised, either because someone deliberately only designs a centralised service for it, e.g. #Mastodon full-text search, or because nobody but the devs can be bothered to run an instance, e.g. #Guppe.
Also, decentralised third-party services will have to be connected to Fediverse instances by the admins manually because the admins will have to decide which instance to connect. Many admins won't take that step at all because they've stopped reading the manual the very moment their instance started working reasonably well, and so they don't even know that they have to connect to such a service.
That said, the Fediverse already speaks one common formatting language, and that's #RichText. #CalcKey translates the #Markdown in out-going messages to Rich Text. #Hubzilla translates the #BBcode in out-going messages to Rich Text. #Streams translates Markdown, BBcode and #HTML to Rich Text. And so forth.
Also, translation between message formats will remain half-useless as long as certain projects show a severe lack of capabilities of displaying messages, and this won't change anytime soon, if ever.
Like it or not, #Mastodon fans, but Mastodon is the worst offender. It can't have more than four images in one post, and it can't embed images within the text. All stuff that has been possible on projects older than Mastodon even before there was Mastodon.
On #Hubzilla (and not only there, but just to take one example), I can design any regular message like a blog post:Text block 1
Image 1
Text block 2
Image 2
Text block 3
Image 3
Text block 4
Image 4
Text block 5
Image 5
Text block 6
Image 6
Text block 7
Image 7
Text block 8
Image 8
Text block 9
This is perfectly normal. And this is perfectly legit. #Friendica, Hubzilla and #Streams were deliberately designed to make this possible. And while Hubzilla has an optional extra functionality for long-form articles, Friendica and (streams) only have this one way of long-form posting. So, again, this is normal and legit and intentional.
On Mastodon, however, the very same post looks like this:Text block 1
Text block 2
Text block 3
Text block 4
Text block 5
Text block 6
Text block 7
Text block 8
Text block 9
Image 8 | Image 7
Image 6 | Image 5
The images are ripped out of their context, reversed in their order, and only four even make it into what Mastodon displays.
The only thing a "translator" could possibly do here is put the images in the correct order. Still, only four would make it onto Mastodon timelines due to Mastodon's limitations, only that it'll be the first four instead of the last four. And also due to Mastodon's limitations, they will still end up after the end of the post instead of embedded between text blocks where they belong.
In the opposite direction, from Mastodon to Hubzilla, a "translator" could be a bit more useful. Currently, when a Mastodon toot with multiple images appears on Hubzilla, the images are put ahead of the text and in reverse order. What the "translator" could do (unless Hubzilla introduces that first) is embed the images at the end of the post in "reverse reverse" order. I'd suggest to also resize them (non-destructively; Hubzilla does that by default with its own images) so that four of them can be shown in a 2x2 arrangement just like on Mastodon, but on Hubzilla, that would cost them the alt-text. -
Thankyou for the fascinating thread on sizes of server. 50% of Mastodon being on centralised servers is a thing alright.
-
@maegul @davidslifka @algorithms
That's s great question!
I'm happy to do what I can, but on this particular server I'm limited to a paltry 500 characters 😉
I'm afraid i can't do your request much justice in that miniscule amount of space, but fortunately, someone else had already provided a pretty good, semi comprehensive demo, but first, let me remind you also that #Cakckey has a much superior search facility over that of mastrotron, which adds much to antennas:
-
@davidslifka @maegul @algorithms @atomicpoet
Hey that's a great resource too!
And Chris' link to @judell 's InfoWorld article is also really helpful. Jon also takes a moment to highlight just how powerful #Fedilab is, a mainstay everyday goto of my #Fediverse interaction on #Android a few years running!
Chris is also a valued member of our #Fediverse_City room on matrix.
A pleasant inconvenience today is trying to keep up with the rapid contemporary Fediverse innovations 🚀
⛵
.
-
Hey guys,
My Mastodon post, which started this thread is my review of the #RedditAlternative Squabbles.io.
I didn't write anything about KBin.
Why not start your own thread, fresh about KBin?
Thanks either way
-
@ericatty @failedLyndonLaRouchite @maegul @stux when I first found out about the fedi.directory and fediverse.info I was thinking, wow are we headed back to the white pages and yellow pages again? Or maybe we’re revisiting the Yahoo directory years?
The Yellow Pages had one hell of a run! I wish I had saved some old ones. They were like time capsules of what your local community was on any given year. They took up so much space that you couldn’t wait to throw out the old ones, but yet if you found a really old one, it was hard not to spend the next hour just flipping through it.
-
@Probably Paul 🌍 @maegul @Kevin Davidson @Ada #CalcKey has full #NomadicIdentity?
As in, you can have identical clones of your account/channel simultaneously on multiple instances? They're kept in-sync with each other in real-time? All clones display the same Webfinger ID which uses the domain of the primary instance? And you can make any clone your new primary instance?
Because this is what nomadic identity actually means.
The only projects known to me that support it are #Hubzilla, #Streams and the now-defunct #Zotlabs projects #Redmatrix, #Osada, #Zap, #Misty a.k.a. #Mistpark2020 and #Roadhouse, basically everything created by Mike Macgirvin after #Friendica.
In fact, I've got my doubts that full nomadic identity can be pulled off without having multiple channels per account/login. And this is another feature which the projects mentioned above have and the ActivityPub-based microblogging/macroblogging/"social network" projects don't.
Or are you referring to how easy it is to move your entire account with everything on it from one instance to another? That isn't what nomadic identity means. -
@Probably Paul 🌍 @maegul @Kevin Davidson @Ada #CalcKey has full #NomadicIdentity?
As in, you can have identical clones of your account/channel simultaneously on multiple instances? They're kept in-sync with each other in real-time? All clones display the same Webfinger ID which uses the domain of the primary instance? And you can make any clone your new primary instance?
Because this is what nomadic identity actually means.
The only projects known to me that support it are #Hubzilla, #Streams and the now-defunct #Zotlabs projects #Redmatrix, #Osada, #Zap, #Misty a.k.a. #Mistpark2020 and #Roadhouse, basically everything created by Mike Macgirvin after #Friendica.
In fact, I've got my doubts that full nomadic identity can be pulled off without having multiple channels per account/login. And this is another feature which the projects mentioned above have and the ActivityPub-based microblogging/macroblogging/"social network" projects don't.
Or are you referring to how easy it is to move your entire account with everything on it from one instance to another? That isn't what nomadic identity means. -
@Probably Paul 🌍 @maegul @Kevin Davidson @Ada #CalcKey has full #NomadicIdentity?
As in, you can have identical clones of your account/channel simultaneously on multiple instances? They're kept in-sync with each other in real-time? All clones display the same Webfinger ID which uses the domain of the primary instance? And you can make any clone your new primary instance?
Because this is what nomadic identity actually means.
The only projects known to me that support it are #Hubzilla, #Streams and the now-defunct #Zotlabs projects #Redmatrix, #Osada, #Zap, #Misty a.k.a. #Mistpark2020 and #Roadhouse, basically everything created by Mike Macgirvin after #Friendica.
In fact, I've got my doubts that full nomadic identity can be pulled off without having multiple channels per account/login. And this is another feature which the projects mentioned above have and the ActivityPub-based microblogging/macroblogging/"social network" projects don't.
Or are you referring to how easy it is to move your entire account with everything on it from one instance to another? That isn't what nomadic identity means. -
@Probably Paul 🌍 @maegul @Kevin Davidson @Ada #CalcKey has full #NomadicIdentity?
As in, you can have identical clones of your account/channel simultaneously on multiple instances? They're kept in-sync with each other in real-time? All clones display the same Webfinger ID which uses the domain of the primary instance? And you can make any clone your new primary instance?
Because this is what nomadic identity actually means.
The only projects known to me that support it are #Hubzilla, #Streams and the now-defunct #Zotlabs projects #Redmatrix, #Osada, #Zap, #Misty a.k.a. #Mistpark2020 and #Roadhouse, basically everything created by Mike Macgirvin after #Friendica.
In fact, I've got my doubts that full nomadic identity can be pulled off without having multiple channels per account/login. And this is another feature which the projects mentioned above have and the ActivityPub-based microblogging/macroblogging/"social network" projects don't.
Or are you referring to how easy it is to move your entire account with everything on it from one instance to another? That isn't what nomadic identity means. -
@Probably Paul 🌍 @maegul @Kevin Davidson @Ada #CalcKey has full #NomadicIdentity?
As in, you can have identical clones of your account/channel simultaneously on multiple instances? They're kept in-sync with each other in real-time? All clones display the same Webfinger ID which uses the domain of the primary instance? And you can make any clone your new primary instance?
Because this is what nomadic identity actually means.
The only projects known to me that support it are #Hubzilla, #Streams and the now-defunct #Zotlabs projects #Redmatrix, #Osada, #Zap, #Misty a.k.a. #Mistpark2020 and #Roadhouse, basically everything created by Mike Macgirvin after #Friendica.
In fact, I've got my doubts that full nomadic identity can be pulled off without having multiple channels per account/login. And this is another feature which the projects mentioned above have and the ActivityPub-based microblogging/macroblogging/"social network" projects don't.
Or are you referring to how easy it is to move your entire account with everything on it from one instance to another? That isn't what nomadic identity means. -
@m @[email protected] @AlisonW @maegul @DanaBlankenhorn @loktai @[email protected] @Ronkjeffries @benpate @apples_and_pears @pinkyfloyd @kimschulz @ngaylinn @jaz @deef @fediversenews @hosting Would that we all had the far-sighted wisdom of #SirTim Berners-Lee, whether real or accidental, to SEE what decentralization could accomplish with http, a simple hypertextual link, and an expanding universe of associational interconnections. #atomic
-
@m @[email protected] @AlisonW @maegul @DanaBlankenhorn @loktai @[email protected] @Ronkjeffries @benpate @apples_and_pears @pinkyfloyd @kimschulz @ngaylinn @jaz @deef @fediversenews @hosting Would that we all had the far-sighted wisdom of #SirTim Berners-Lee, whether real or accidental, to SEE what decentralization could accomplish with http, a simple hypertextual link, and an expanding universe of associational interconnections. #atomic
-
@m @[email protected] @AlisonW @maegul @DanaBlankenhorn @loktai @[email protected] @Ronkjeffries @benpate @apples_and_pears @pinkyfloyd @kimschulz @ngaylinn @jaz @deef @fediversenews @hosting Would that we all had the far-sighted wisdom of #SirTim Berners-Lee, whether real or accidental, to SEE what decentralization could accomplish with http, a simple hypertextual link, and an expanding universe of associational interconnections. #atomic
-
@m @[email protected] @AlisonW @maegul @DanaBlankenhorn @loktai @[email protected] @Ronkjeffries @benpate @apples_and_pears @pinkyfloyd @kimschulz @ngaylinn @jaz @deef @fediversenews @hosting Would that we all had the far-sighted wisdom of #SirTim Berners-Lee, whether real or accidental, to SEE what decentralization could accomplish with http, a simple hypertextual link, and an expanding universe of associational interconnections. #atomic
-
CW: AI, Nivenly, Haidra, StableDiffiusion
@[email protected] @[email protected] the parent post has links to a great case-study-in-progress of community governance; and @[email protected] and @[email protected] this ties in with the discussion here as well.
Some of the things to look for, based on the experiences I noted with some of other community governance efforts ... thinking about these up front could lead to a more inclusive and effective discussion, and once it's done looking at them in retrospective could be another good data point for what does and doesn't work.
-- @[email protected]'s #TertuliaExtraordinaria discussion (collected here in a single document) is a great example of a fediverse governance-related discussion conducted in a way that lets multiple voices be heard (as opposed to privileging those with the largest platform). What if any mechanisms will be used here, both in the broad initial discussion and then the next phase of the general membership discussion?
-- In the social.coop and cosocial discussions, BIPOC and transvoices were almost completely absent. Will there be a similar dynamic here #nivenly discussion? [To be clear, I'm talking both about who participates and whether cis white participants elevante the voices of non-participating BIPOC and trans people.]. And the parent post discusses another "who's at the table" question that could crop up here:
"For example Nivenly is tech- and open-source focused. How well represented will artists, photographers, writers, actors, and musicians -- the people who tools like #Haidra exploit -- be in the discussions and voting?"
-- Mastodon doesn't have no way of getting notified about replies to a post that _don't_ mention you; it's functionality that's been requested multiple times, dating back to 2018 if not earlier. Github discussions are better on this front; and unlike vanilla Mastodon they allow formatting via Markdown. So on the one hand it's a more useful platform for people who are used to Github -- which, given Nivenly's techie and open-source focus, presumably includes all the board and paying members, and quite possibly most of the people who have accounts on @[email protected]. At the same time though @[email protected]'s has some good points about the lack of inclusivity of using github.
Of course Nivenly's also encouraging discussions on the fediverse and in their Discord chat, and offering an email option for people to submit questions ... that's good: people without github accounts aren't excluded from the conversation. Still, the structure certainly favors people who do have github accounts. In particular, techies (who as a class, and in some cases as individuals, are more likely to profit from normalizing exploitative AI governance) are more likely to have github accounts than artists, photographers, writers, actors, and musicians (who as a class and as individuals are the ones who are exploited), so this could accentuate the potential "who's at the table" problem.
-- as @[email protected] mentions in the post, it's not clear what mechanism to use for voting. is there a way to use existing affordances to address this? If not could some straightforward improvements help?
@[email protected] @[email protected] -
CW: AI, Nivenly, Haidra, StableDiffiusion
@[email protected] @[email protected] the parent post has links to a great case-study-in-progress of community governance; and @[email protected] and @[email protected] this ties in with the discussion here as well.
Some of the things to look for, based on the experiences I noted with some of other community governance efforts ... thinking about these up front could lead to a more inclusive and effective discussion, and once it's done looking at them in retrospective could be another good data point for what does and doesn't work.
-- @[email protected]'s #TertuliaExtraordinaria discussion (collected here in a single document) is a great example of a fediverse governance-related discussion conducted in a way that lets multiple voices be heard (as opposed to privileging those with the largest platform). What if any mechanisms will be used here, both in the broad initial discussion and then the next phase of the general membership discussion?
-- In the social.coop and cosocial discussions, BIPOC and transvoices were almost completely absent. Will there be a similar dynamic here #nivenly discussion? [To be clear, I'm talking both about who participates and whether cis white participants elevante the voices of non-participating BIPOC and trans people.]. And the parent post discusses another "who's at the table" question that could crop up here:
"For example Nivenly is tech- and open-source focused. How well represented will artists, photographers, writers, actors, and musicians -- the people who tools like #Haidra exploit -- be in the discussions and voting?"
-- Mastodon doesn't have no way of getting notified about replies to a post that _don't_ mention you; it's functionality that's been requested multiple times, dating back to 2018 if not earlier. Github discussions are better on this front; and unlike vanilla Mastodon they allow formatting via Markdown. So on the one hand it's a more useful platform for people who are used to Github -- which, given Nivenly's techie and open-source focus, presumably includes all the board and paying members, and quite possibly most of the people who have accounts on @[email protected]. At the same time though @[email protected]'s has some good points about the lack of inclusivity of using github.
Of course Nivenly's also encouraging discussions on the fediverse and in their Discord chat, and offering an email option for people to submit questions ... that's good: people without github accounts aren't excluded from the conversation. Still, the structure certainly favors people who do have github accounts. In particular, techies (who as a class, and in some cases as individuals, are more likely to profit from normalizing exploitative AI governance) are more likely to have github accounts than artists, photographers, writers, actors, and musicians (who as a class and as individuals are the ones who are exploited), so this could accentuate the potential "who's at the table" problem.
-- as @[email protected] mentions in the post, it's not clear what mechanism to use for voting. is there a way to use existing affordances to address this? If not could some straightforward improvements help?
@[email protected] @[email protected] -
CW: AI, Nivenly, Haidra, StableDiffiusion
@[email protected] @[email protected] the parent post has links to a great case-study-in-progress of community governance; and @[email protected] and @[email protected] this ties in with the discussion here as well.
Some of the things to look for, based on the experiences I noted with some of other community governance efforts ... thinking about these up front could lead to a more inclusive and effective discussion, and once it's done looking at them in retrospective could be another good data point for what does and doesn't work.
-- @[email protected]'s #TertuliaExtraordinaria discussion (collected here in a single document) is a great example of a fediverse governance-related discussion conducted in a way that lets multiple voices be heard (as opposed to privileging those with the largest platform). What if any mechanisms will be used here, both in the broad initial discussion and then the next phase of the general membership discussion?
-- In the social.coop and cosocial discussions, BIPOC and transvoices were almost completely absent. Will there be a similar dynamic here #nivenly discussion? [To be clear, I'm talking both about who participates and whether cis white participants elevante the voices of non-participating BIPOC and trans people.]. And the parent post discusses another "who's at the table" question that could crop up here:
"For example Nivenly is tech- and open-source focused. How well represented will artists, photographers, writers, actors, and musicians -- the people who tools like #Haidra exploit -- be in the discussions and voting?"
-- Mastodon doesn't have no way of getting notified about replies to a post that _don't_ mention you; it's functionality that's been requested multiple times, dating back to 2018 if not earlier. Github discussions are better on this front; and unlike vanilla Mastodon they allow formatting via Markdown. So on the one hand it's a more useful platform for people who are used to Github -- which, given Nivenly's techie and open-source focus, presumably includes all the board and paying members, and quite possibly most of the people who have accounts on @[email protected]. At the same time though @[email protected]'s has some good points about the lack of inclusivity of using github.
Of course Nivenly's also encouraging discussions on the fediverse and in their Discord chat, and offering an email option for people to submit questions ... that's good: people without github accounts aren't excluded from the conversation. Still, the structure certainly favors people who do have github accounts. In particular, techies (who as a class, and in some cases as individuals, are more likely to profit from normalizing exploitative AI governance) are more likely to have github accounts than artists, photographers, writers, actors, and musicians (who as a class and as individuals are the ones who are exploited), so this could accentuate the potential "who's at the table" problem.
-- as @[email protected] mentions in the post, it's not clear what mechanism to use for voting. is there a way to use existing affordances to address this? If not could some straightforward improvements help?
@[email protected] @[email protected] -
CW: AI, Nivenly, Haidra, StableDiffiusion
@[email protected] @[email protected] the parent post has links to a great case-study-in-progress of community governance; and @[email protected] and @[email protected] this ties in with the discussion here as well.
Some of the things to look for, based on the experiences I noted with some of other community governance efforts ... thinking about these up front could lead to a more inclusive and effective discussion, and once it's done looking at them in retrospective could be another good data point for what does and doesn't work.
-- @[email protected]'s #TertuliaExtraordinaria discussion (collected here in a single document) is a great example of a fediverse governance-related discussion conducted in a way that lets multiple voices be heard (as opposed to privileging those with the largest platform). What if any mechanisms will be used here, both in the broad initial discussion and then the next phase of the general membership discussion?
-- In the social.coop and cosocial discussions, BIPOC and transvoices were almost completely absent. Will there be a similar dynamic here #nivenly discussion? [To be clear, I'm talking both about who participates and whether cis white participants elevante the voices of non-participating BIPOC and trans people.]. And the parent post discusses another "who's at the table" question that could crop up here:
"For example Nivenly is tech- and open-source focused. How well represented will artists, photographers, writers, actors, and musicians -- the people who tools like #Haidra exploit -- be in the discussions and voting?"
-- Mastodon doesn't have no way of getting notified about replies to a post that _don't_ mention you; it's functionality that's been requested multiple times, dating back to 2018 if not earlier. Github discussions are better on this front; and unlike vanilla Mastodon they allow formatting via Markdown. So on the one hand it's a more useful platform for people who are used to Github -- which, given Nivenly's techie and open-source focus, presumably includes all the board and paying members, and quite possibly most of the people who have accounts on @[email protected]. At the same time though @[email protected]'s has some good points about the lack of inclusivity of using github.
Of course Nivenly's also encouraging discussions on the fediverse and in their Discord chat, and offering an email option for people to submit questions ... that's good: people without github accounts aren't excluded from the conversation. Still, the structure certainly favors people who do have github accounts. In particular, techies (who as a class, and in some cases as individuals, are more likely to profit from normalizing exploitative AI governance) are more likely to have github accounts than artists, photographers, writers, actors, and musicians (who as a class and as individuals are the ones who are exploited), so this could accentuate the potential "who's at the table" problem.
-- as @[email protected] mentions in the post, it's not clear what mechanism to use for voting. is there a way to use existing affordances to address this? If not could some straightforward improvements help?
@[email protected] @[email protected] -
CW: AI, Nivenly, Haidra, StableDiffiusion
@[email protected] @[email protected] the parent post has links to a great case-study-in-progress of community governance; and @[email protected] and @[email protected] this ties in with the discussion here as well.
Some of the things to look for, based on the experiences I noted with some of other community governance efforts ... thinking about these up front could lead to a more inclusive and effective discussion, and once it's done looking at them in retrospective could be another good data point for what does and doesn't work.
-- @[email protected]'s #TertuliaExtraordinaria discussion (collected here in a single document) is a great example of a fediverse governance-related discussion conducted in a way that lets multiple voices be heard (as opposed to privileging those with the largest platform). What if any mechanisms will be used here, both in the broad initial discussion and then the next phase of the general membership discussion?
-- In the social.coop and cosocial discussions, BIPOC and transvoices were almost completely absent. Will there be a similar dynamic here #nivenly discussion? [To be clear, I'm talking both about who participates and whether cis white participants elevante the voices of non-participating BIPOC and trans people.]. And the parent post discusses another "who's at the table" question that could crop up here:
"For example Nivenly is tech- and open-source focused. How well represented will artists, photographers, writers, actors, and musicians -- the people who tools like #Haidra exploit -- be in the discussions and voting?"
-- Mastodon doesn't have no way of getting notified about replies to a post that _don't_ mention you; it's functionality that's been requested multiple times, dating back to 2018 if not earlier. Github discussions are better on this front; and unlike vanilla Mastodon they allow formatting via Markdown. So on the one hand it's a more useful platform for people who are used to Github -- which, given Nivenly's techie and open-source focus, presumably includes all the board and paying members, and quite possibly most of the people who have accounts on @[email protected]. At the same time though @[email protected]'s has some good points about the lack of inclusivity of using github.
Of course Nivenly's also encouraging discussions on the fediverse and in their Discord chat, and offering an email option for people to submit questions ... that's good: people without github accounts aren't excluded from the conversation. Still, the structure certainly favors people who do have github accounts. In particular, techies (who as a class, and in some cases as individuals, are more likely to profit from normalizing exploitative AI governance) are more likely to have github accounts than artists, photographers, writers, actors, and musicians (who as a class and as individuals are the ones who are exploited), so this could accentuate the potential "who's at the table" problem.
-- as @[email protected] mentions in the post, it's not clear what mechanism to use for voting. is there a way to use existing affordances to address this? If not could some straightforward improvements help?
@[email protected] @[email protected] -
@markrprior
Thanks. I often refer to the green list here, which tracks the environmental factors:https://greenfediverse.codeberg.page/green-instances/
Though I think that #greenFediverse db is getting old.
-
I hope #Hajkey keeps developing for blahaj.zone and similar communities, particularly the long sought after #FediverseSafety features that never seem to arrive on the #Fediverse and become more important as greater adoption occurs and user culture changes - like the amount of transphobic users that Lemmy has brought here and the dev bros think this is progress. #Firefish #Calckey #IceShrimp @[email protected]
RE: https://hachyderm.io/users/maegul/statuses/110767208159622462 -
Lemmy is experimenting with plugins.
https://lemmy.ml/post/15187879
Still in experimental prototyping stages it seems, but cool to see. Hope it gets worked on and works out well.
Could be an interesting experiment for the Fedi in general?
It’s using rust’s extism, so webaasembly for plugins.
-
FYI, for those #akkoma / #akkomane users interested ...
phanpy (eg, phanpy.social) seems to work well with akkomane / akkoma.
It provides deck/columns and picks up on the longer post length too.
No separate post editing view though ... but you can pop it out into a separate window.
No awareness of the local only visibility, which reveals how dire mastodon's influence over that feature has become IMO.
And the wonderful catch-up feature seems to work too!
-
Ooof
Reading this thread, I cannot help but think there's a gulf developing (or that has developed) between #AcitivityPub and old-school #fediverse peeps and most of the developers looking to do things on the fediverse.
I'm no fan of #mastodon 's dominance, but standardising a microblogging API around the foundation laid by mastodon and adopted (it seems) by many makes a lot of sense.
The "gulf" seems to be whether AP is "everything" or a "starting point"
https://social.wake.st/@liaizon/111693052737189407 ( @liaizon )