0x1C3B00DA

joined 8 months ago
[–] 0x1C3B00DA@fedia.io 1 points 1 week ago (1 children)

Self hosting isn't really compatible with viral content

The post I was replying to claimed virality and self hosting are at odds with one another because it causes skyrocketing expense. My point was that maybe someone selfhosting a server in the fediverse is not as interested in virality. And I doubt even the most viral posts in the fediverse would break the bank of a selfhoster

[–] 0x1C3B00DA@fedia.io 2 points 1 week ago

Virality is nowhere near the only reason for posting videos. People post them to make jokes, teach something, reply to someone else, etc, or all the same reasons someone might make a blogpost or a post on a link aggregator.

[–] 0x1C3B00DA@fedia.io 2 points 1 week ago

Theres no web app? That seems short sighted. You apparently cant access anything without logging either. I dont expect these shorts to get much viewership if you have to register and download an app to see anything. It also doesnt seem in the spirit of the fediverse

[–] 0x1C3B00DA@fedia.io 2 points 1 week ago (10 children)

Maybe the problem in that equation is the expectation of virality and not self hosting?

[–] 0x1C3B00DA@fedia.io 1 points 1 month ago

That's not a contradiction, it's maybe an incomplete argument. And I was relying on my previous sentence that mastodon has a history of steamrolling other implementations to imply that they would do it again and were already warning about that. But none of this even matters; I've made a follow up comment that lays it out more explicitly.

[–] 0x1C3B00DA@fedia.io 10 points 1 month ago (2 children)

I didn't cherry pick a statement. I included the part where they said the very first draft.

I did fail to explain how its a power grab, but that's was only because I thought it was a fairly obvious one-to-one point. I've also added another example. But lemme try again.

  1. Mastodon has a history of pushing features that affect interop with other implementations without seeking feedback from other implementations or outright ignoring the feedback they do receive.
  2. A member of the mastodon team wrote a FEP to formalize a setting related to search indexing. This was the right way to go about it. yey Mastodon was working with other implementations. But that FEP didn't receive positive feedback and it seems like it was abandoned.
  3. Now mastodon is trying to standardize something using the ideas from that FEP, outside of the FEP process (which is the agreed upon way to collaborate between implementers).
  4. They're warning on their site that they have deadlines and may not incorporate feedback if they can't resolve it without breaking deadlines.
  5. They are under no obligation to incorporate it after their initial draft and, historically, mastodon is unwilling to update their work to incorporate other implementers' feedback.

A more collaborative way to do this would have been to seek feedback before making a grant proposal and making the grant proposal jointly with other projects so they weren't the only ones getting paid for it.

[–] 0x1C3B00DA@fedia.io 3 points 1 month ago (4 children)

Mastodon has a history of steamrolling other implementations.

This means we might not always be able to incorporate all the feedback we get into the very first draft of everything we publish

The site even warns that theyre on a deadline and may not incorporate feedback.

EDIT: they also mention a "setting" that determines if a user/post is searchable. theyve presented a FEP to formalize this setting but nearly everyone else had issues with their proposal. as usual for mastodon, this looks like them sidestepping external feedback and just doing what they want

 

Let's build another web browser based on Servo!

 

I recently read Has the IndieWeb Become Irrelevant from starbreaker.org. The post does a great job linking to and summarizing a spate of posts that I will call “people being mad at the IndieWeb”, while also being one of these posts. These posts accuse “the IndieWeb” of being elitist, exclusionary, overengineered, complicit, and unnecessary, among many other things. There are some common threads I noticed among these posts: None of them mention micro.

[–] 0x1C3B00DA@fedia.io 4 points 4 months ago

chat apps and systems like Twitter and Mastodon aren't a good place for journalism

Super agree with that. Framing this feature as specific to journalism was a poor choice. The feature is useful for any writer/blogger/joe schmoe on the web

[–] 0x1C3B00DA@fedia.io 12 points 4 months ago

It's a cool feature, but it sucks that (once again) the mastodon team is taking control of fediverse-wide features and ignoring outside criticism.

https://github.com/mastodon/mastodon/pull/30398

[–] 0x1C3B00DA@fedia.io 4 points 4 months ago

South Carolina, in the US Southeast

[–] 0x1C3B00DA@fedia.io 4 points 5 months ago

Then, there is TikTok algorithm which is a common critic of the app but is how you get a never-ending flow of content which isn't uninteresting enough for you to turn the app off

I think there needs to be some kind of discovery algorithm for new users with an empty feed (or even existing users who just wanna find something new) but a federated alternative doesn't need something as powerful as the tiktok algorithm to be a decent replacement. It doesn't need to surface a "never-ending flow of content" because it doesn't have a financial incentive to keep you in the app endlessly.

 

For the past few years, I've been running a tech blog focused on the Fediverse. It's evolving into a bonfide news organization.

[–] 0x1C3B00DA@fedia.io 3 points 5 months ago (8 children)

on-demand pods that travel on existing abandoned railways.

They're reusing existing tracks.

 

The first released candidate of LiveView 1.0 is out!

 

SFO Museum has joined the “Fediverse”. We have begun to operate a series of automated “bot” accounts that are published using the ActivityPub protocols and that can be subscribed to from any client, like Mastodon, that supports those standards. These are automated, low-frequency, accounts and they currently only support a limited set of interactions: Accounts can be followed or unfollowed, individual posts can be “liked”, “boosted” or replied to but those replies will not be answered (yet) or published on the SFO Museum websites. To get started we’ve created three “groups” of accounts: Things which have happened recently involving the SFO Museum Aviation Collection; Things which have happened in the terminals (new and old) and; Things from the collection which are related to flights in and out of SFO.

view more: next ›