Not only are they federating with each other, but they implemented Group to Group following to help prevent duplicate posts. Its a feature that's been requested for lemmy/kbin/mbin, so it'll be interesting to see how well it works for them.
"We, current and previous employees of Apple Inc., wish to express our disappointment and shock at the lack of care and understanding this company has given the Palestinian community, not only abroad suffering in Gaza, but also towards our own team members and anyone who supports them within our stores and offices. "
Disagree. Its a consequence of corporations loudly proclaiming their support for groups when it cost nothing (think Black History Month here in the US). Corporations like to use a lot of empty marketing talk about societal issues when they can get away with it and ppl have decided to fight that by pushing companies to actually takes stands. Also, corporations here in the US have much larger voices than individual (and again this is because of the corporations' own actions), so some ppl see it as a way they can actually have an influence on their govt.
But wait, there's more, we're standardizing our Groups implementation so other projects can take advantage of our App and Client API.
So its compatible with lemmy but uses a different API and they want their API to be the standard for the threadiverse? This is why we should be using the C2S, but since we're not you should just stick with the lemmy api since that's where the client ecosystem is already at.
The lawsuit caps years of regulatory scrutiny of Apple’s wildly popular suite of devices and services, which have fueled its growth into a nearly $3 trillion public company.
Hasbro is probably gambling that it’s the IP that made the money, and not Larian being magic in a bottle as a developer
This is probably true, but how can executives be so stupid? Every review I read praised Larian specifically and how the made a huge game with no microtransactions and tons of little loving touches. You have to be willfully ignorant to think it was the IP and not the developer and their work that people were responding to.
in terms of giving one’s consent, exactly how the two are different?
Because in the second case, the user is choosing to post on a network where any other server can request their posts. A bridge is just an instance that understands more than one protocol. There's no difference in it and any other server requesting your posts. That's how the network works.
I said the two things are different, you said how does that make asking for consent for the two things different, and my response was that for one of them it already works that way without your consent. That is a clear difference. Yes, I'm talking about the technology to explain the difference, because it's a concrete fact. Your argument that a bridge should be opt-in requires an abstract boundary that some instances are are allowed to federate on an opt-out basis and others are not.
You don’t build trust in users by using practices like opt-out, which is again, the only argument I am trying to make.
The instance you're on uses opt-out practices. You didn't consent to your post federating to kbin.social and yet here we are. If you don't trust the bridge, fine, block it. Every tool on the fediverse that you already use to deal with its inherently opt-out nature is available for you to use with this bridge.
Thank you for the detailed explanation. It matches what I've heard from others while having this same debate. Now allow me to explain my side.
I have consented to functionality in which my posts are distributed to other instances within the Fediverse. It’s widely advertised and clearly explained that is how things function. I can readily find which implementations are part of the fediverse
This is the part I think is wrong and the cause of all of this. You can not find which implementations are part of the fediverse. No tracker that you can use has an up-to-date and accurate listing of implementations. New ones come online every day as some random developer builds something new. The fediverse doesn't have clear boundaries and I think the advertising that you mentioned does a disservice by implying it does. The fediverse is similar to the web; they're both based on open protocols and can be guided but not controlled, because anybody can build something on those protocols.
One response to this fuzziness has been to demand most features be opt-in. The reason I don't think this is tenable is because you have to have a hard boundary to determine what should be opt-in and what is ok to be opt-out. Your heuristic was native ActivityPub implementation. I don't think this scales (I feel like you're going to say this is a technological argument and therefore invalid, but it's also a social argument. Ppl don't want to use something that they have to constantly maintain. Constantly adding new servers/users to an allowlist is a chore that would drive ppl away. See google+ circles). It doesn't scale because like I said above new implementations pop up every day and these implementations are starting to branch away from the static archetypes we're used to (Twitter-like, Facebook-like, Reddit-like, etc). And some of them are existing projects that add AP support.
For instance, Hubzilla/Friendica has been bridging AP content for years. Do all of those instances require opt-in because they use a different protocol in addition to AP? There have also been bridges that translate RSS feeds to AP actor for years. Did the owners of those RSS feeds opt-in and should they have been required to?
What I'm trying to say is I think you're right that you can never keep up with the boundaries of the fediverse and where your posts end up. And I don't think there's an easy delineation for what should be opt-out vs opt-in. So instead we should be demanding that implementations add controls to our posts. Thinks like ACLs and OCAPs would allow you to control who can see your posts and interact with them and not care about new bridges/instances/whatever. Which is why I think the argument over opt-out vs opt-in is a distraction that will only keep the fediverse in this quasi-privacy space where you're dependent on yelling down any actor who is doing something with yours posts you don't like.
I wish you luck and would love to see better Interoperability, but mastodon has been against better Article support from the beginning. I'm not sure much has changed there
Bridgy Fed made a splash earlier this week by announcing its latest progress in connecting the Fediverse to Bluesky and Nostr. Sadly, not everyone was welcoming.
It doesn't scrape or facilitates scrapping. Your server sends your posts to the bridge and it federates it to other servers. That's how federation works. If you define that as facilitating scraping, then every instance on the fediverse facilitates scraping.
And nobody is disagreeing with their right to do that. They have the tools to curate their own experience. But they can't demand the fediverse work they way they want it to and no other way.
The fediverse is a decentralized network. It doesn't have a cohesive nature/direction. It's made up of servers providing twitter-like experiences, servers providing reddit-like experiences, forums, personal websites, video platforms, etc. You'll never know all the places your fediverse data has reached because the fediverse doesn't have hard boundaries so you can't possible measure it all.
Which is why I think complaining about other what other software does is pointless. Instead, users should be pushing their own software to adopt more features to allow them to control their experience and data.
For example, free software, no advertising as a business model, not commercial, not run by big corporations and talking over AP.
None of those are requirements to be part of the fediverse. The fediverse existed long before ActivityPub was even proposed. Free software, ad free, non commercial, not run by big corporations are all just coincidence because its a grassroots effort. Even now, there's multiple companies invested in the fediverse: Mozilla, Flipboard, Facebook, Automatic being the most obvious.
Even if you take those as given, none of those dictate any shared values. Bridgy-fed itself meets all of those requirements but clearly holds differing values. Truth Social, Gab, Spinster, etc are all on the fediverse despite being abhorrent to the majority of the rest of the fediverse.
I'm in favor of groups maintaining shared values and enforcing policies based on them. But those policies can never apply to an entire network made up of distinct projects, servers, and people all with different ideas about how it should work.
I suppose this is where the root of our disagreement lies. For me the technical network that links tools is not the fediverse. The fediverse is what is built on top of that network and it is inherently linked with the community
I wrote a long reply disagreeing with each of your points, but you're right. This is our disagreement. You're using the term fediverse to apply to a specific group of ppl/servers that share values with you and I think that's co-opting the term. The fediverse is more akin to the web (a platform based on technology that allows ppl access to other ppl and information) and it doesn't make sense to talk about it as a single organization.
I think trying to change its meaning like this is flawed and leads to issues like we're having now with Bridgy-Fed. You can't shout at everyone to use the tech in the way you want, because eventually there will be ppl/orgs that just don't listen. Instead, I think you should be pushing for existing platforms you're using (lemmy, mastodon, etc) to give you more control of your own data. There are ways to allow small-fedi users to create the exact type of spaces they want and anybody else to have the wide open fediverse they want, if the various project would implement them.
I'm happy to continue discussing this with you or leave it here. Either way, thanks for the chat and have a good one.
Web 1.0 means no interactivity outside of forms (client to server request<-> response cycle). Web 2.0 was the label used when sites started gaining interactivity, using Javascript.
Mozilla seized an opportunity to bring trustworthy AI into Firefox
Therefore, as part of the changes today, we will be bringing together Pocket, Content, and the AI/ML teams supporting content with the Firefox Organization
This is from the Mozilla release. The second quote does say "Firefox Organization" and not "Firefox", but it seems clear they are planning on integrating AI into Firefox.
But, I've reread @NotSteve_'s comment and they were saying the funding earned from AI could be put into Firefox, not AI itself. NotSteve wasn't claiming that putting AI into Firefox would bring in more funding, only that AI could be a separate source of revenue. So my question is moot.
A conversation is a collection of messages with a common context. The ActivityStreams specifications define both collections and contexts, but very little guidance is provided on how to use them effectively. This document specifies an Acti
This is the proposed FEP-61cf: The OpenWebAuth Protocol. OpenWebAuth is the “single sign-on” mechanism used by Hubzilla, (streams) and other related projects. It allows a browser-based user to log in to services across the Fediverse using a single identity. Once logged in, they can be recognised by other...
OpenWebAuth has been in use on the fediverse since before WebFinger became so widely used.
Like I said in a previous comment, this FEP was written by reverse engineering the existing implementation. It's still a proposal so it still has to go through a discussion period where issues like this can be worked out and it can be updated
Forgejo v7.0 is now available (forgejo.org)
Last Week in Fediverse – ep 65 (fediversereport.com)
Forum federation, Ghosts, Event Planners and the source code of Truth Social.
Apples4Ceasefire: Apple Employees Request Ceasefire Recognition (www.apples4ceasefire.com)
"We, current and previous employees of Apple Inc., wish to express our disappointment and shock at the lack of care and understanding this company has given the Palestinian community, not only abroad suffering in Gaza, but also towards our own team members and anyone who supports them within our stores and offices. "
Update on Pixelfed groups (mastodon.social)
Shipping soon ™ but we heard that before. Still looking forward to it and they explicitly mention Lemmy compatibility....
U.S. Sues Apple, Accusing It of Maintaining an iPhone Monopoly (www.nytimes.com)
The lawsuit caps years of regulatory scrutiny of Apple’s wildly popular suite of devices and services, which have fueled its growth into a nearly $3 trillion public company.
Larian Studios Is Officially Done With The Baldur’s Gate Series (kotaku.com)
Bluesky and Mastodon users are having a fight that could shape the next generation of social media (techcrunch.com)
📣 This is a callout proposing a working group to improve Article interop in Mastodon, and across fediverse servers & apps (lemmy.ml)
I posted a callout earlier this week, and originally planned to use Guppe Groups....
Tear Down Walls, and Build Bridges (wedistribute.org)
Bridgy Fed made a splash earlier this week by announcing its latest progress in connecting the Fediverse to Bluesky and Nostr. Sadly, not everyone was welcoming.
I want to be able to make my own Web 1.0 websites easily
And I’d like to be able to do it privately too, that’d be cool....
Mozilla downsizes as it refocuses on Firefox and AI (techcrunch.com)
An Introduction to Conversation Containers (fediversity.site)
A conversation is a collection of messages with a common context. The ActivityStreams specifications define both collections and contexts, but very little guidance is provided on how to use them effectively. This document specifies an Acti
FEP-61cf: The OpenWebAuth Protocol (socialhub.activitypub.rocks)
This is the proposed FEP-61cf: The OpenWebAuth Protocol. OpenWebAuth is the “single sign-on” mechanism used by Hubzilla, (streams) and other related projects. It allows a browser-based user to log in to services across the Fediverse using a single identity. Once logged in, they can be recognised by other...