mke

joined 4 months ago
[–] mke@programming.dev 2 points 1 week ago

For what it's worth, the rest of the report is mostly fine, and I'm inclined to believe I learned something about Drew. But I also felt that was not honest, and question if it had to be included at all. Looking around, it seems the author likes Stallman, and regardless of how they felt before, they probably disliked Drew when they found he was connected to the Stallman report.

So thanks for mentioning that weird vibe. I'm glad I wasn't the only one who paused at that section.

[–] mke@programming.dev 1 points 1 month ago (1 children)

And I'm saying you're better off without. That sentence is ridiculous enough already, it doesn't need the source to make it worse. But good on you for worrying about credit, do as you will.

[–] mke@programming.dev 1 points 1 month ago* (last edited 1 month ago) (3 children)

— vintermann, Hacker News

I don't know who this person is, but adding "Hacker News" doesn't give their words more credibility. It gives them less, if anything.

Imagine I quoted someone and, underneath it, added:

— PM_ME_UR_FEET, Reddit

Both of these enjoy the same level of base, intrinsic trust to me: none.

[–] mke@programming.dev 1 points 1 month ago (1 children)

Just for the record, I know little about gotosocial, but I've looked into Misskey a fair bit and I think it's irrelevant here.

FediDB data on active users seems off (a low ~12k MAU), but even if the real number is much greater, most are on the flagship instance (misskey.io) which has multiple CSAM censures on fediseer.

Put another way, it's almost counterproductive to include Misskey in these topics because simply federating with its biggest instance could be a liability for most 1st world western instances.

I doubt the Swiss government would get much out of Misskey.

[–] mke@programming.dev 6 points 1 month ago

No, I'm trying to reduce the influence of a problematic individual. The lawsuit has, and will have, more coverage.

[–] mke@programming.dev 39 points 1 month ago (3 children)

I didn't want to rain on your parade, but:

  • Firefox has hundreds of millions of users.
  • Lemmy has less than half a million total users, and YTD MAU peaked at 52k.

Even putting aside technical details, I fail to see how "Lemmy integration in the browser" could be a good product strategy. A plugin/extension can also be developed by independent developers, which seems much more fitting for the size of the target demographic. Maybe I'm missing something.

[–] mke@programming.dev 1 points 1 month ago

I'm sorry, banana, that was sarcasm. I saw nothing I'd call a quality.

[–] mke@programming.dev 13 points 1 month ago (4 children)

I would suggest not trusting anything Lunduke says, the man went off the deep end and became a harmful conspiracy theorist.

For example, he believes there is a trans advocacy group going around and destroying open source projects from within. That's right, only the Lunduke Journal has the truth, and the truth is that trans kids are killing open source.

[–] mke@programming.dev 7 points 1 month ago

Sorta. Only as a discussion starter, if you wanted. I was unsure how to frame my thoughts without being rude, but it seems I ended up being confusing instead. I'll edit my comment to try again, please try to read it in its intended spirit.

[–] mke@programming.dev 8 points 1 month ago (2 children)

The replies are a prime example of the fediverse microblogging sphere's greatest qualities.

This entire event is unfortunate, but unsurprising.

[–] mke@programming.dev 12 points 1 month ago* (last edited 1 month ago) (2 children)

Yes, I think that's natural. A large segment of their market is still there. Throwing away years of work when the accounts cost relatively little to maintain would be wasteful. I don't see how their presence there is relevant to this discussion.

[–] mke@programming.dev 3 points 1 month ago

In theory, I doubt development would continue. For a federated cohost to survive long term, it would also need to be open source, with a developer community that could fork the project and carry the torch. That's a very different cohost we're envisioning, even excluding required UX changes to make it possible.

At that point, one might as well imagine a cohost that explored better ways to make money, or attracted more users, or ran a tighter ship. Both scenarios lead to this discussion never happening.

view more: next ›