@hamishcampbell @_elena the good part is that this is what we should do in the best case scenario, too. So, all worthwhile.
@hamishcampbell @_elena one other thing: bridging is really important for us all right now. It's how we can tell developers to implement ActivityPub and still get access to the BlueSky audience. I hope everyone works to support BridgyFed.
So, I think there are two important things people in the Fediverse movement can do to help with these possible outcomes.
The first is to keep building on ActivityPub. I love our protocol and our ecosystem, and I think it's a wonderful network. But it's also a necessary hedge against clawback or collapse.
The optional birthDate field gives other projects a standardized data source for age verification compliance.
I think we should start calling this age attestation rather than verification, or does the confusion help us here by making the linux ecosystem seem like it’s more compliant than it is?
Not to my knowledge. Granted all I did was a 1 second kagi search so there might be something floating out there. I do feel like if he made some kind of official statement, it’d be pretty big news though.
Sears showed up on day and said they were renegotiating the deal and were only going to pay 75% of the price per mower. The company had no choice, but to accept even though they were now losing money on each unit sold. Then suddenly Sears began offering their own mower, and stopped buying any at all and the company, full of debt, was ruined.
Same as it ever was...
@tom @julian @astro There are some small differences in following between a relay and a regular actor. But it's essentially correct.
https://codeberg.org/fediverse/fep/src/branch/main/fep/ae0c/fep-ae0c.md
Very well said. Couldn't agree more. A wolf in sheep's clothing. A patina of 'open systems' over a solid $100M corporate core.
This all brings in a firehose, which can be a lot of data to handle, especially if you're only interested in a few topics.
Fedibuzz has solved this really nicely, by having one relay per hashtag. So an admin can add a few hashtag relays for topics of interest to their users.
@julian We apparently agree that expecting us to follow bot accounts to see hashtags is absurd. But that's how it looks to me.
Are you saying that this is under the hood stuff and we are not expected to follow bot accounts? That somehow these accounts will transparently deliver the hashtags we follow? If so, it's a huge mistake to notify users that an instantly created bot account has boosted a post.
And again, I think the bigger problem is hashtag abuse. I hope someone is working on that.
@julian @mlanger I don't actually think it's an ugly hack.
In ActivityPub world, things that you follow remotely are actors. They can be people, groups, organizations, bots, even other things like documents or places.
For following a hashtag remotely, I think it should look like any other actor on the network.