James R Kirk

You’ve got the right idea, uploading content on old internet was (largely) about putting yourself out there hoping to find like minded people to connect with. All those “quirky, weird” websites people nostalgize over weren’t seeking clout, they were seeking connection.

I think it’s healthy to deprogram ourselves from the idea that “followers” are the goal of creating content. If an influencer is making “art” with the express purpose of getting followers that they can leverage into marketing deals, then are they really making art? If the goal is to make money then… that’s just a job, imo.

“EEE” doesn’t really make sense in this context, and even if there was some way for Meta to affect non Meta-owned instances- ActivityPub is an open protocol and Meta is allowed to use it however they want.

Got it, very interesting! I look forward to it being worked out soon, Wordpress federation is awesome.

Still not fully integrated, but it’s nice to see broader ActiviyPub adoption beyond “follow a handful of users who opted-in”. I never expected Meta to be the company inching towards federation and not bluesky. Makes me wonder if Tumblr will ever follow through with their promises to federate.

edit: To the (sadly predictable) response that “Meta will screw you over in a heartbeat” YES, of COURSE they will, that’s why it’s GOOD to be able to access Threads content safely and privately from a non-Meta controlled platform.

Jellyfin is great, but in defense of Plex, they announced that remote streaming would require one of the two parties to have a Plex pass was coming back in March so I don’t know if it’s fair to say they are holding anything hostage.

If you’re using HAOS (ie not running in docker), there is an official add-on called “File Editor” that allows you to edit the config.yaml and upload files from the UI. It’s not perfect but gets the job done.

HA has a “www” folder that by default that is accessible to the network. Anything in /config/www appears at http://yourhassaddress:8123/local, so your images will be at http://homeassistant.local:8123/local/image.jpg

This is great, I just cross-posted it to !fedibridge@lemmy.dbzer0.com hopefully someone can post it to Reddit. It’s really nice to see a intro to the concept of the fediverse that doesn’t get bogged down with technical details.

It got cloudy

Not liking someone is not a good reason to root against decentralized platforms, IMO. The entire point of decentralization is that nobody gets to control the experience and who is/isn’t allowed to participate.

Unless he joins fedia.io you don’t really get a say in what he does… kind of the entire point behind decentralization…

It’s also an avenue for attacks.

There’s no need for hostility, your characterization of what is happening does not reflect reality.

A Fedi instance requires a time commitment, there are some good suggestions in here but I recommend some alternative frontends.

When using the official Mastodon app (as suggested in the “guide”) “instances” are not a factor at all (unless the user specifically goes out of their way). A new user could have never even heard of the term “instance” and the above steps would work fine.

You don’t just download the app, create an account, and go.

Actually with Mastodon this is literally how it works.

EDIT: I should say this is how it works now, it didn’t always used to be this way. The official Mastodon app used to ask the user to pick an instance, but for a number of years now it defaults every new account to mastodon.social unless they opt out. There was a big brouhah about centralization but the Mastodon devs felt it made for easier on boarding.

Turns out good web design skills does not always translate into other skills.

If an instance has a lot of spam, admins tend to notice and block it. In the future it’s likely admins will have more tools too, but for now the system works pretty well.

That is correct and echoes what I said

The Remote Watch Pass is only needed if neither you nor the server owner have a Plex pass: https://support.plex.tv/articles/requirements-for-remote-playback-of-personal-media/

When using an affected platform to stream personal video content remotely from a Plex Media Server, then one of the following needs to be true:

1. The admin account for the Plex Media Server has an active Plex Pass (which also allows remote playback for any other user streaming from that server)
2. Your account has an active Plex Pass
3. Your account has an active Remote Watch Pass

The remote playback restrictions do not apply to streaming music content to Plexamp or photos to our Plex Photos app.

I agree with your overall sentiment but also literally 100% of BlueSky users are on one instance.