Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)KO
Posts
1
Comments
25
Joined
2 yr. ago
  • I understand why you want that, and I'm glad that decentralization/defederation allow you to keep that.

    I have to ask though, why do you want to keep other people from getting that algorithmic, corporate content if they want it? Especially since this will allow them to do it without giving up so much personal info via apps. (While also allowing us to interact/evangelize the FOSS way > corporate systems)

  • Permanently Deleted

  • Only if people voluntarily give up their privacy and switch to a threads account/app, right? I mean ultimately the argument is that Meta will develop features so cool that we’ll all give up our privacy for them?

    Idk, it just seems like if that’s the fear, I think it will happen regardless and even defederating won’t really stop that. I feel like people will just make new accounts wherever the cool place to be is.

    I’m all for defederating just because you don’t want to see or associate with that content though, that totally make sense.

  • sigh

  • The entire fediverse is built upon the idea of an open protocol that anyone is welcome in yet it seems like everyone is shocked that a corporation is finally jumping in.

    This was inevitable and more will be coming. The beauty of the fediverse is that you can still find an instance that gets all the mainstream content of the Meta stuff while not subjecting you to the algorithm and data gathering that Meta apps have. In addition, if you DON'T want to participate and see that stuff, the fediverse provides ways to de-federate your neck of the woods and live in bliss without seeing and interacting with any Meta content.

  • sigh

  • I think it’s a downside that I’ve heard they’re not federating immediately, but rather doing that in a few months.

    Instagram Threads WILL entice a bunch of people to leave Twitter (and eventually get to the fediverse), but if Insta Threads aren’t federated on day 1, we can’t offer up alternatives to users that doesn’t harvest data.

    Instead, they’ll only get that choice in a few months, though still better than never I guess 🤷‍♂️

  • Mine definitely didn't work until I defined the IP, and I got that idea from reports that others had posted online haha. Not sure what we're doing wrong but there are dozens of us!

    Good callout on the redundancy of the pull command, I didn't even think/notice that!

  • Selfhosted @lemmy.world
    kobra @lemmy.world

    How I self hosted wefwef on macOS with Docker

    I posted this as a comment in the wefwef community but thought it might also be relevant here. If anyone is interested in self hosting wefwef this is how I did it on macOS:

    Start by installing Docker desktop

    Open Terminal and type in:

    docker pull ghcr.io/aeharding/wefwef:latest

    Then, you need to use a Docker run command like below to get things started. In this example, I put my local IP in as "192.168.1.2" but you'll need to adjust that value to whatever your machine's IP is.

    docker run --rm -d -p 192.168.1.2:5314:5314 -e "CUSTOM_LEMMY_SERVERS=lemmy.world,sh.itjust.works,lemmy.ml" ghcr.io/aeharding/wefwef:latest

    At that point, I went to my iPhone, opened Safari and went to 192.168.1.2:5314 and boom, there's wefwef. Install this as PWA and name it (local) or something to differentiate it from the normal wefwef and you're good to go.

    Disclaimer: I’m brand new to all of this so I’m sure this isn’t the best way. But it got me