Selling distribution seems like a decent move. Focus on production and sell to every other steamer.
Selling the whole company is click bait. Even Apple (suggested in the article), doesn't have the cash or desire to buy Disney outright. At best it would look like a merger and be mostly stock but it'd still be monumentally stupid for everyone.
Lemmy and Kbin are the "threadiverse", where content is submitted by users to specific groups and replies are shown in a tree-structure. In ActivityPub behind the scenes, I believe this is achieved by making non-user Actors that re-post everything @'d at them.
Mastodon is not thread based, users post as themselves and other users follow them directly. Then everything is shown lineally.
Film companies aren't generally in the business of selling the rights to their products. As you say, it's a cash cow they can keep milking for years. They can re-release the same film on new platforms and continually contract it out to different streaming platforms for years. Why would they sell you a distribution license in perpetuity for anything resembling an reasonable cost?
Mic arms will have a tripod style screw mount at the end and then will probably come with several different pieces that can fit on the end. The one you're describing is a shock mount and they should list the microphone diameters they accept. You'll probably also be able to directly mount the microphone or use a rigid clip.
You can see them individually per post on your profile but there is not a global "karma" number. Some people have made api scripts to calculate it but its not an intended part of the platform.
This is from my own instance so I guess you might not see it.
Are you saying you only allow-listed certain instances? Federation is on for all instances by default, you don't need to enable federation for each remote instance in the admin panel. Remove everything from the allow-list, add any thing you don't want to see in the block-list and all those little instances should start appearing.
Nope, I've seen nothing firm about them doing or not doing it, but OP asked about current information and at the moment they are open source and do not have a standards document.
As it stands I wouldn't jump on AT for a project of mine and wouldn't recommend it as a superior protocol on those grounds.
So when Bluesky introduces a new feature or a breaking change in the protocol anyone downstream will find out when it gets pushed, maybe a little ahead of time when it comes in as a pull request. Bluesky goes live with the change immediately, maybe in a public beta channel, maybe straight to prod, depending on their testing setup. Anyone running a bluesky compatible server becomes immediately incompatible until they rush to implement the new changes. The best user experience will be had on first party servers, driving the vast majority of users there.
For a standard defined protocol, like ActivityPub for example, to introduce a change like that it would first go to the standards comittee where it would be discussed publically with stakeholders. The changes would be published and then all parties would begin implementations at a pace that makes sense to them. It's like when you hear about new Wi-Fi versions several years before any devices actually support them. One group doesn't just get to come out with some crazy new change that everyone else has to reverse engineer and then race to keep up.
What Bluesky is doing might be fine and make sense for their model, whatever that may be. I just want to point out that there is a difference and it drastically changes what the future of the service will look like.
Bluesky's protocol implementation is open source but the protocol isn't defined by any standard. Once its open and federating, if that ever happens, anyone who wants to connect will be entirely beholden to the latest published version from bluesky and whatever protocol documentation they provide. They're starting in the middle of the EEE playbook, anyone who wants to join in has to chase them.
As far as I know AT isn't actually being used anywhere at the moment. Bluesky has a single server with closed registration and no federation partners. Despite being open source, AT isn't really intended to be an open protocol.
ActivityPub, on the other hand, has a few hundred servers including several dozen large ones all federating nicely together.
Federation is on by default on all instances. As soon as you search and subscribe to remote communities they'll start federating. So far so good on my little one user instance.
I know following users was a pretty big sticking point on reddit, it was certainly a feature I had no interest in using, but it's a lot more interesting here with federated interoperability. Regardless, I think it'll be a while before the lemmy devs even have time to think about features like that.
TheOneCurly @ TheOneCurly @lemmy.theonecurly.page Posts 0Comments 164Joined 2 yr. ago
Anecdotally in my local instance feed the most memes are coming out of blahaj's 196 and World's Lemmy Shitpost