Former Diaspora core team member, I work on various fediverse projects, and also spend my time making music and indie adventure games!

  • 76 Posts
Joined 5 years ago
Cake day: November 29th, 2019


  • Most of the backlash pertains to the board members appointed to the new nonprofit. One of the members is a lawyer that has defended crypto and AI companies, another is ex-Twitter angel investor Biz Stone.

    Mastodon’s community usually has some kind of vague beef about one thing or another when it comes to Eugen and the decisions he makes for the project, whether it’s a new feature or a design change or that he didn’t do something that other projects wanted to do.

  • He’s periodically shown updates on it. From talking to him, there are a number of challenges:

    • Being blocked by other features, like a UI refactor
    • Compatibility with other existing implementations (less of a problem now with the Group Federation FEP by
    • Wanting to include Private Groups
    • Bringing in moderation, assignment, and delegation tools for groups.
    • Dealing with unrelated issues pertaining to the day-to-day maintenance
    • Needing to break out new experiments in a branch to see how well an idea actually works

    I think the biggest thing is that he probably does spread himself pretty thin at times, and is still learning how to rely on community pull requests and contributions. It can be a really hard thing to do, especially if you feel the need to provide the creative direction for how things ought to work.

  • Sean Tilley@lemmy.mlOPMtoFediverse@lemmy.mlLemmy's Image Problem (Updated 02-06-2024)
    5 months ago

    No, it’s how I see you based on pretty much any time I observe you making a public comment. Which is unfair of me, admittedly, I can’t possibly see everything you write. Most of the time, though, you come across as hostile, and read as though you’re dunking on other people and projects.

    Anyway, the article was updated somewhat to give proper credit for your recent developments and point to your fundraising efforts.

    Have a nice day.

  • Sean Tilley@lemmy.mlOPMtoFediverse@lemmy.mlLemmy's Image Problem (Updated 02-06-2024)
    5 months ago

    If you can take a moment to move your massive, fragile ego out of the way, you’ll realize it’s not a hit piece. It’s criticism of your behavior in reaction to what is frankly a reasonable set of requests.

    Journalism is not just about serving as a propagandic mouthpiece to lionize you and your work. Sometimes, I have to report on subjects that are frankly horrible, people acting shitty, and how people in spaces react to that.

    Effectively you are blowing the complaints of a single user completely out of proportion. It is true that we didnt respond ideally in the mentioned issue, but neither is it okay for a user to act so demanding towards open source developers who provide software for free.

    This issue is basic fucking table stakes for user safety and data compliance, and the fact that it still does not exist after four years of being a project is wild to me. It creates liabilities for admins. The fact that it’s still a problem, right now, illustrates that these things are not direct concerns in how you design software.

    I find it very questionable that you publish this sort of hit piece against Lemmy without even bothering to ask for a comment from our side.

    Your comments were in the GitHub issues.

  • Look, no one is ungrateful for the work you and Dessalines are doing. I get it - I helped run a large-scale federated open source social network over a decade ago. It’s an amazing, incredible experience - but, it’s also grueling, demanding work, and community members and users can be incredibly fickle. Especially when it comes to living off of donations, and having to carve out a technical stack all by yourself. That shit is hard.

    Here’s the thing: your users, your community, your efforts in general, pretty much ride or die by the people who run instances of your software, advocate for your platform, and develop apps and tools for your ecosystem. If something is broken at a foundational level, it’s ultimately your responsibility to decide what to do about it.

    Code is not the only fruit of someone’s labor here. Your community is doing a lot of labor for you too, and making even less money doing so. At some point, if people don’t think their needs are being met to keep running their communities and stave off the worst of the worst, it’s going to tank people’s confidence. People will leave. And they’ll talk on the way out. Optics matter.

    I’m not saying you have to drop everything to accommodate some random concern right away. But some of the responses you’ve given to people that had reasonable asks, that had reasonable use-cases in ensuring smooth operations of instances in compliance of laws…some of your reactions are terrible.

    If your default when someone asks you about GDPR compliant features is to scream at people, demand that they do the work for you, make excuses that you’re too busy, or belittle someone because you disagree with someone, you’re doing community management ass-backwards, and you’re burning away community goodwill every time you do it. It’s hostile and demoralizing, and people will come to resent you for it.

    If you have such high demands then you shouldnt use it, and switch to another platform instead. And yes you are clearly stoking an attack against Lemmy, I wonder why you hate our project so much.

    See, this is exactly what I’m talking about. Someone asks for something, points out problematic behavior, gives feedback on how something could be better, and you lean into the myopic belief that this is somehow an attack or an effort to undermine you. My brother in Christ, if there is any ill-will towards how you do things, it is because of your own behavior, not on the merits of your project, your political alignment, or who you are as a person.

    I don’t hate your project, but you need to pull your head out of your ass, and realize that you’re dropping the fucking ball on trust and safety. People hosting instances aren’t going to stick around forever if you keep defaulting to hostility.

  • I take it you’ve never run a community instance. The problem is, laws vary by jurisdiction, and can have a very real effect on how you run your server when shit hits the fan.

    We recently ran a story about a guy building his own Fediverse community and platform, who just happened to be a bit naive about the network. He’s off in his corner, doing his own thing, people find his project and assume it’s some kind of weird scraper. After disinformation came out about it, someone remote-loaded child pornography to his server, for the purpose of filling a report with the police.

    The guy is based on Germany. Local jurisdiction requires one year of prison time minimum. It matters.

  • No, you’re good, and we’re mostly on the same page! My general expectation is that your server tries its best, maybe there are still copies out there, but you shrug and say “eh, I wiped my stuff locally, good enough”.

    But yeah, I agree that once something leaves your server in terms of the passage of data, there are no guarantees. And I do agree that significant structural changes are necessary and important for the network’s continued evolution!

  • There’s nothing wrong with having good third-party tools, that was not my point. db0 in particular has done some amazing, amazing work.

    What’s fucked, however, is having a project:

    • whose core infrastructure only offers the most threadbare tools
    • there’s zero consideration from development on privacy, user safety, or basic controls to handle when shit hits the bed
    • the devs are stone silent when waves of CSAM crash through instances
    • they openly mock people or say they’re “too busy to do this” when it comes to meeting the most basic expectations of how a social platform ought to work.

    Like, this is not an attack on Lemmy itself, I think the platform can be a real force for good in the Fediverse. But let’s be honest, this project is not going to live very long if nothing changes.

    Basic things like having the ability to easily remove images from storage should be part of the core platform. The fact that this still isn’t a thing even four years into the project is insane.

  • Yeah, I agree. I think the important thing is “was the local content scrubbed?” Because at least if that was done, the place of origin no longer has it.

    Federated deletes will always be imperfect, but I’d rather have them than not have them.

    What might actually be interesting would be if someone could figure out this type of content negotiation: deletes get federated, some servers miss it. Maybe there’s a way to get servers to check the cache and, if a corresponding origin value is no longer there, dump it?

  • Unfortunately, even if instance admins were to unanimously defederate, Meta—or any social media corporation—could create white-label instances to take their place, and we might be none the wiser of their control of them.

    I don’t necessarily disagree with this idea, but they would have to justify the business case to their shareholders. As of right now, the idea of a whitelabel personal silo is a limited value proposition to people not already invested in the Fediverse. If it’s whitelabel, what will Meta do? Start a new company? Inevitably, people would figure it out, and go with something else.

    It’s true that we can always choose to defederate from them. What’s to worry about is their meddling with the ActivityPub standard using their incomparably vast resources, and them making their own extensions to the standard in efforts to suck users back into the Borg. Things like that.

    I said this a little further up in the conversation, but if Meta produces some horrendous, awful version of ActivityPub that only benefits them, what’s stopping the rest of us from forking the protocol or adopting a different one? If we never switch to their version of doing things, and there’s feature breakage between us and Meta, who actually loses here?