wake.st is one of the many independent Mastodon servers you can use to participate in the fediverse.
the personal instance of Liaizon Wakest

Administered by:

Server stats:

1
active users

wakest ⁂

the CEO of Flickr, who is now active here at @d0n, is wondering if should implement and become part of the !

twitter.com/donmacaskill/statu

Flickr CEO Don MacAskill (@d0n) is currently running a poll to decide whether to add to :flickr: Flickr to join the (Mastodon, Pixelfed, Peertube, etc.)
Make your voice heard:
sfba.social/@d0n/1094226479952
Poll on Twitter too:
twitter.com/DonMacAskill/statu

Remember this has good and bad repercussions whether you use Flickr or not, it would be the first time an old giant joins us but also would bring many many new issues we would have to face together. Please boost for reach!

SFBA.socialDon MacAskill (@d0n@sfba.social)Would you like to see #ActivityPub on #Flickr? #fediverse (x-post from https://twitter.com/DonMacAskill/status/1597256480519966720) [ ] Yes & already pay. [ ] Yes & would start paying. [ ] Yes, but only for free. [ ] No, work on other stuff.

@d0n adding some folks to this thread cause its important: @cwebber@octodon.social, @evan, @Gargron, @grishka, @halcy, @hypolite, @mike

@d0n

I just remembered, there is also the license of the photo to consider.

If ever #Flickr will add #ActivityPub support, it is probably a good idea to include the photo's license in the 'message' when it's pushed to the #Fediverse network.

While, yes, works are automatically copyrighted to the owner, the general public doesn't think that way. Most Internet users assume, “if it's online, then it's public and free to use”. So including the license (even “Copyright” and “All Rights Reserved”) will help reiterate the photo is not to be redistributed outside the “reshare” features without permission.

On the other hand, it will also help expose #CreativeCommons and #PublicDomain works. Seeing something like “CC-BY-SA 4.0 International licensed photo” or “Public Domain photo” will create awareness and help their works be discovered and reused.

Just a thought. ^_^

@liaizon

@youronlyone @liaizon Absolutely. I think you’d be hard pressed to find a bigger advocate for photographer rights, including flexibility, than us. 👍

@liaizon
Or how about we don't give a fuck about the mental flatulence of a guy who ruined a perfectly good photography community by speedrunning the shittiestmanagementdecisions% category.

Yo, @d0n — please just keep doing what you do best, i.e. ruining #Flickr, and leave the #fediverse alone. You and your cult of mgmt 101 dropouts can fuck right off.

@d0n

@liaizon @d0n I am in two minds about this. I see the potential and I like the idea that I can publish to Flickr and have it publish that photo out to the Fediverse.

However, my text based ramblings are relatively curated. I don't dump an entire memory card of photos out onto Mastodon in one go.

Flickr often has people who literally do that... thousands of photos uploaded in one go with no curation.

@danieldurrans @liaizon That's not a common behavior on Flickr, but it does happen. Still, I'm not sure how that matters... it won't publish to people that don't follow the person in question? It won't flood anyone else.

@d0n @danieldurrans that depends on how you set up flickr with activitypub, if they are set as posted "public" then if someone uploaded a card full of photos at once and someone on a smaller instance was following that user, then those photos would flood the local view of the federated timeline which a lot of instances currently use as a sort of community view. as long as there are some per account posting/visibility settings on the flickr side this shouldn't be an issue tho.

@liaizon @danieldurrans Really? A single follower receiving updates marked "Public" from a remote instance would cause their entire local instance to see them? That's not how I read the spec, nor how I've experienced Mastodon so far...

@d0n @danieldurrans yes that is how it works here currently. See this helpful diagram: infosec.exchange/@securopean/1

I am talking about the "Federated Timeline" in this chart btw, not the Local timeline. But the Federated Timeline is also very very different depending on how big or small your instance is.

Infosec ExchangeSecuropean (@securopean@infosec.exchange)Attached: 1 image Useful diagram - from here https://axbom.com/mastodon-tips/ Also, https://pinafore.social/ is a nice uncluttered web interface.

@liaizon @danieldurrans Interesting. I think even without image card dumping, the "Federated Timeline" may get overrun if an instance the size of Flickr or Tumblr or whoever begins publishing. 🤔

@d0n @danieldurrans its per user being followed, so not necessarily. If I was only following one user on flickr from my account, my federated timeline would only contain their posts, not the posts of every user on flickr

@liaizon @danieldurrans But it's not just who you're following, it's also who on your instance is following. With hundreds of millions of members on Flickr and tens of millions of new photos a day on Flickr, instances with many local participants may get flooded with many "valid" Flickr photos.

@d0n @liaizon Also worth noting that a photo will end up getting cached on every server that sees the post, with the associated implications of storage space and alike.

Perhaps a starting point would be to put some friction into the process... rather than fedi-posting every uploaded photo, the user has to go to their Photostream and press a button on each photo they want to fedi-post.

@d0n @liaizon @danieldurrans
This is a good topic to discuss, but it's going to happen with or without #Flickr.

#Pixelfed is already out there, publishing photos via #ActivityPub. It doesn't have a ton of users yet, but I haven't heard anyone complaining that its behavior is terrible.

That said, maybe Flickr should have a timer wherein it batches up activity from a user and sends it out as a single update? That way if I upload 500 photos, I don't slam my followers w/ 500 posts?

@liaizon @d0n it would/will be interesting to see what that might.lok like, and added the caveat to him that new folks here are leery of corp social media and older users are a bit anti-.

@liaizon @d0n

Everyone into the pool! #fediverse is 'the new black'

@liaizon @d0n well.. i gave up proprietary software to start using pixel fed

@liaizon @d0n this would be fucking sick honestly. Not sure what else would excite the millions of former Flickr users more

@liaizon @d0n this would be great, #Flickr is already very friendly with RSS feeds for pretty much everything, ActivityPub would be the cherry on top!

@liaizon @glynmoody @d0n who was replying to Matt Mullenweg of Wordpress.com also adding to Tumblr (owned by Automattic), not missing the opportunity...

@acesabe @liaizon @d0n indeed, a great opportunity for him - and for us if #ActivityPub really takes off...

@acesabe @glynmoody @d0n yes I probably should have mentioned that in this post as well. I already made a few posts about the tumblr announcement that got a bunch of response but it is indeed rather important to think of this as a snowballing effect, to think of the consequences not of just one platform stuck in "the old world" adding activitypub but if "the industry" starts seriously considering this narrative possibility

@liaizon @acesabe @d0n indeed. as it happens I have an article on this topic coming out tomorrow or the day after.

@glynmoody would love to take a read!

@glynmoody
Very curious about your take on that... Especially on the issues around ads on the commercial platforms and how that will mix with the federated systems and the strong anti-ad, anti-tracking ethos common in the #fedivers
@liaizon @acesabe @d0n

@dirkhh @liaizon @acesabe @d0n luckily, I address precisely some of those issues - will post here when it is up

@liaizon @d0n

I doubt the fediverse would be better off with vc funded international corporations

@liaizon @d0n Alright guys, the ship's on fire; it has been a nice time but won't work anymore.
Someone else wishes to develop a new social network?

@liaizon jesus christ. I'm still not fully with this but even as generally someone who is cautious this is starting to look pretty potential watershed moment

@liaizon @d0n @cwebber @evan @Gargron @halcy @hypolite @mike

My personal opinion is simple: the more services with preexisting user base adopt ActivityPub, the better for the humanity. If someone doesn't want to federate with them, they'll be able to block that federation anyway. There are no major downsides really.

@grishka @liaizon @d0n @cwebber @evan @Gargron @halcy @hypolite @mike I still think the Context Collapse angle (probably at least one or two other angles) on this is heavily under-theorized, and certainly under-tooled-for (technological capabilities tools, and social norms tools) as far as the ActivityPub and the Fediverse we have now.
(I'm... pretty sure that's one of the angles explicitly being considered in @cwebber 's current work? I think.)

Like it's not that simple that there are NO downsides. We should go into this expecting and searching for a lot of recurring social friction, and not close our eyes when walking into this.

@liaizon i actually don’t know how I feel about those but I guess vaguely; positive? Mostly because it‘s starting to be quite a few companies. You‘d think if there’s a lot, an embrace extend extinguish type scenario is harder

but also, I‘ve not really any experience with large scale systems, I‘m not a masto or activitypub core dev, and working at MS doesn’t immediately make you an EEE expert either, so that’s pretty much just really just „personal feeling“. Not sure if we‘d limit/suspend them. Would talk it through with coadmin probably, likely ask users for input :icosan_think:

Good lord @liaizon@social.wake.st did you just necro a 3 year old topic 🤣

@julian what is time anyway

@woffs @liaizon 😂 We’re rabidly customer centric, so very interested in their voices, but we still make the decisions (and must live with the results).

@liaizon would love to hear people's take on the pros/cons of this.

@alisynthesis

What I can think of (and some based on what I've seen in other heated threads).

CONS:

* Potential corporate or for-profit organisations dominating, or filling, the fediverse.

* Once the above are involved, they will also get involve in the future of the fediverse.

Like moving the protocol in a direction people doesn't want, which will benefit them in the long run, and not the fediverse and its citizens.

Or, introducing unofficial stuff here and there, and since they're the largest, it's either everyone else implements their unofficial additions, or gets left behind (and possibly ordinary users encouraging everyone to move to a "better" platform).

* Then later, after all is said and done, said large services disconnects from the fediverse (Facebook did this, they connected to the XMPP network, then years later disconnected from it, citing this and that about XMPP). Or, creates their own fediverse network.

Since a lot of ordinary users are used to the way things are, ordinary users left behind will more likely move too.

PROS:

* It will increase the content available in the #Fediverse.

The fediverse has been around since 2008, it was called "identiverse" until 2010-2012 when the former as first coined. Yet, it took an Elon to start a mass migration.

One of the usual reason I hear from my own network (ie family, friends, colleagues, and so on), is content (the other is network).

Content that matters to them are not in the fediverse. Like official accounts of this and that. And personalities they want to get updates from.

* People, who otherwise wouldn't create a fediverse account, will now be available in the network.

This is good. As mentioned previously, people's "network" is one other reason I personally often hear as a reason. If their family, friends, colleagues, and so on, are suddenly available in the fediverse, it eliminates that reason why they don't care about it at all.

* Awareness.

Mass media will start to talk about the Fediverse. Their respective tech sites, tech TV/cable programs, won't be able to ignore and dismiss the fediverse anymore.

People who are against the fediverse, for whatever reason, will have a fediverse account simply because they are using one of these existing services.

---

Just to be clear, the above pros and cons were only what I think and what I've observed in other heated discussions. It does not represent my stand.

My stand is this: The fediverse is a web standard, an open protocol. Anyone can join the fediverse. There is no central authority, or any 'body' governing it, and I believe that's by design.

Existing fediverse instances are already blocking other servers for a hundred reasons, from the no-reason-just-because-I-feel-it, to a very justified reason (like two-thirds of the instance is about hate). As others have already said, if they don't want existing corporate-run / for-profit services in the fediverse, they can just block them. And their members who are fine with it can either move or create another account; and vice versa. (Which I think is the spirit of fediverse, choice and freedom.)

^_^

@liaizon

@youronlyone @liaizon thanks so much for taking the time to write this. It provides good food for thought. As someone who hasn't used social media for a long time until finding the fediverse, I'm wary of celebrities and corporations jumping in and (for me) poisoning the waters. That said, I have some faith that the protocol will allow me the power to sort out those issues myself, as you point out, and the benefits are significant. So, I'll vote yes.

@liaizon @d0n Interesting looking at the current results of the same poll on the two platforms. On Twitter it’s “Yes & already pay.” in the majority. On Mastodon, it’s “Yes, but only for free.”

@mpjames @liaizon

Noticing a similar pattern myself. :)

@liaizon @d0n@sfba.social Course a capitalist would be on an instance we suspended for homophobia.

@liaizon @d0n just closed my flickr account after like 14 years lol

@liaizon @d0n Looks useful. Build on existing RSS support.

@liaizon what do you think? Flickr is a centralized platform, so it would just add one huge instance to the fediverse. On the other hand, would they be able to spam us fedizens here with their ads? In that case many servers would defederate, I think, and so I wonder what's in there for them?

@maikek I think its inevitable that some big centralized corporate environment will join us so we might as well get it out of the way with a service like flickr and make the necessary changes to deal with what happens when youtube or facebook try to join us.

@liaizon
They can... It wouldn't change much seeing as the rules of conduct would still apply and they would likely be silenced (blocked) by most servers if they run ads. It's not really up for debate as to if they can use the scripts and activity pub seeing as it's all foss, anyone can use it and or modify the scripts.
@maikek

@thingamajig @maikek Don is bringing it up for debate and asking our opinions about it right now. Some people are really in favor and some people will try to push them away. I think it is very important to think through the long term effects of what it will mean. The AP spec is also still a very moving target. It hasn't really changed since its first release but mastodon and pleroma and lemmy and the rest have added things specific to themselves that would either get supported not by Flickr 🧵

@thingamajig @maikek and if flickr didn't support the additions of mastodon to the spec then they wouldn't really support mastodon. but if they Do support all the specifics to mastodon then that reinforces mastodons position as the "way" AP should be done. This is all stuff we need to figure out regardless but it is a bit scary to do this right now. There are a lot of things we haven't figured out yet ourselves and adding flickr means adding potentially 60 million active users 🧵

@thingamajig @maikek we are currently at around 2 million active users all across the fediverse, so it could completely change the dynamics around here...