0x1C3B00DA avatar

0x1C3B00DA

@0x1C3B00DA@kbin.social

A case for preemptively defederating with Threads

With Meta beginning to test federation, there's a lot of discussion as to whether we should preemptively defederate with Threads. I made a post about the question, and it seems that opinions differ a lot among people on Kbin. There were a lot of arguments for and against regarding ads, privacy, and content quality, but I don't...

0x1C3B00DA,
0x1C3B00DA avatar

Meta (or any large entity) cannot monopolize or control the fediverse. If their implementation starts drifting from established norms, they will be blocked by most instances or will just be incompatible. The example used to back up this argument is usually XMPP, but people forget that XMPP is still around. It never died; its just a smaller, niche network.

The fediverse is already a small, niche network. So if Meta comes in and tries to control the network, it will then be responsible for maintaining its own "Meta-fediverse" network (that some instances may choose to be a part of) while the remaining instances will remain as a small, niche network. Meta can't force current fediverse servers to implement any Meta-specific features or to change their software in any way.

The mod workload argument is the only one that I see being a real issue, but the target is wrong. Anyone worried about that should be discussing it with fediverse devs to improve mod tools, not trying to force the entire fediverse to stay at their preferred size

0x1C3B00DA,
0x1C3B00DA avatar

Any data they can get from federating, they can get much easier by just scraping it. If your goal is data harvesting, implementing ActivityPub is a huge waste of money

0x1C3B00DA,
0x1C3B00DA avatar

No ActivityPub is explicitly push-based. If you follow someone on a remote server, the remote server pushes their posts to your server. Meta can push content into the fediverse, but like any other user/server they can be blocked if its spammy

0x1C3B00DA,
0x1C3B00DA avatar

You can't really Embrace, Extend, Extinguish an open standard. Anybody can continue to use the unextended version and that's exactly what would happen if Meta tried it. They can't force servers to update or implement meta-specific features

0x1C3B00DA,
0x1C3B00DA avatar

Implementing ActivityPub at their scale costs way more than allowing a drop-in-the-bucket network to go on existing. The fediverse is not really competition for them

0x1C3B00DA,
0x1C3B00DA avatar

They don't need ActivityPub for that. Nearly everything on the fediverse is public and scrapable. If they want to monetize fediverse data, they already can

0x1C3B00DA,
0x1C3B00DA avatar

Genius (the lyrics company) tried to license the content on their website and a judge said that can't be legally binding because there's no guarantee the scraper read it. It seems like the same would apply here.

0x1C3B00DA,
0x1C3B00DA avatar

It looks like I was mixing up some facts. The Genius case was denied because genius doesn't own the copyright to the lyrics they were publishing. I can't find the case now, but there was a case where a judge said scraping was allowed because it wasn't a given that the scraper had read a ToS.

0x1C3B00DA,
0x1C3B00DA avatar

They used it in a perfectly acceptable and understandable way. The definition you're describing as sarcastic is an official meaning of the word. https://www.merriam-webster.com/dictionary/patronize

0x1C3B00DA,
0x1C3B00DA avatar

People who say that are generally talking about the signup where you have to pick an instance. And then there's the worry over which other servers yours federates with. If you isolate your attention to a single instance, then all those worries go away.

The same already happens on the fediverse in regards to mastodon itself. A lot of people discuss the fediverse almost wholly in terms of mastodon.

0x1C3B00DA,
0x1C3B00DA avatar

It's an explicit goal of ActivityPub, but mastodon implemented its own bespoke API instead of the ActivityPub Client to Server (C2S) API. Apps got developed for mastodon using its API and other services implemented the masto API instead of C2S to get app support.

And anytime you bring up C2S to current projects, they brush it off. So it seems like the grand idea of the fediverse is way far off and not likely to happen soon.

Threads has hashtags now (www.theverge.com)

“Tags work a little differently than hashtags do on platforms like Instagram and X (formerly Twitter). When composing a Threads post, you start a tag by tapping the # symbol and then typing out your topic. But instead of being limited to just one word, you can type out a whole phrase (with spaces!) and add special characters,...

0x1C3B00DA,
0x1C3B00DA avatar

That wouldn't make them incompatible with the fediverse. ActivityPub can support tags with spaces, even though no current fediverse platform allows it. A post with a hashtag with spaces would still federate to other services and if that services is robust enough, should still be linked up so that you can click it to see the tag feed.

0x1C3B00DA,
0x1C3B00DA avatar

ActivityPub can support tags with spaces, even though no fediverse platform allows you to write tags like that. The name of the tag can be pretty much whatever you want, as long as it has a valid URL.

0x1C3B00DA,
0x1C3B00DA avatar

I don’t understand why these new services need to reinvent common vocabulary for their services (ie: notes (which is a completely different thing on Twitter), channels, antennas, pages etc)

I don't know about the rest of the terms, but note is actually the standard term for a microblog post. It was used by services before and contemporaneous to twitter and is the ActivityStream term for these posts.

0x1C3B00DA,
0x1C3B00DA avatar

I wasn't claiming note was the first term used to refer to them only that it's been used to refer to them for a long time

0x1C3B00DA,
0x1C3B00DA avatar

Their step one is:

identify medium-to-large sized Fediverse servers

which means it'll be weighted toward mastodon servers. I hope they account for that somehow.

[Work In Progress]: Vosh - a third-party screen-reader for the Macintosh | AppleVis (www.applevis.com)

After getting fed up with the general neglect of MacOS accessibility from Apple, and having wanted to work on something meaningful for quite some time, I decided to attempt something that for some reason nobody seems to have tried to do before: write a completely new screen-reader for that platform. This isn't an easy task, not...

0x1C3B00DA,
0x1C3B00DA avatar

I've never bought an apple product but I've worked at multiple jobs that provided me with a mac so I still want to see improvements in the mac ecosystem.

Also, I'm not a screenreader user but I am a web developer and screenreader users deserve the same experience as typical screen/keyboard/mouse users. Developing for screenreaders sometimes feels like developing for browsers use to be with inconsistencies and unimplemented standards. For browsers, it was Chromes launch that really spurred competition in the space that drove vendors to implement standards and interoperability so it seems reasonable that a new screenreader could provide the same outcome for screenreaders.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • anitta
  • ethstaker
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • tacticalgear
  • osvaldo12
  • Youngstown
  • thenastyranch
  • slotface
  • rosin
  • kavyap
  • ngwrru68w68
  • cisconetworking
  • JUstTest
  • Durango
  • khanakhh
  • normalnudes
  • provamag3
  • everett
  • mdbf
  • cubers
  • tester
  • modclub
  • megavids
  • GTA5RPClips
  • Leos
  • lostlight
  • All magazines