Wow, similar thing for me, I have a 'bicuspid aortic valve' which means the aortic valve in my heart is a bit funky and doesn't push blood through as it should. And that makes the FAA also deem me medically unfit. I think there is a process to get a medical exemption, but with the cost of getting a license so high already, I just decided to stick with MSFS. I get to 'fly' a 737 like I wanted as a kid, learn all about it, but I'm not shelling out thousands and years of my life (okay, maybe I am shelling out some money but I like pretty airports!)
lml
joined 1 year ago
That's something I want to get into. I want to set up that self hosted software, forget what it's called, but you can integrate with IoT devices just like you can with a mainstream assistant service like Google Home.
What I really want to do is automate my blinds, which are the chain loop type, so I can say "house, open the living room blinds" like they did in Smart House, the Disney channel original movie (or maybe that was Home Alone 4, but we don't talk about that one). I found a little motorized device that integrates with these chain blinds but it was a bit pricey. Of course if I tried to make it with my own Arduino etc it would be an ugly mess.
I'm in the process of getting those working--I've had some issues with the captcha plugin so far.
Good idea, I just looked however and they've changed the instances page to: https://fedidb.org/software/kbin. So any server that has federated with any other listed is on there, I believe. More Kbin instances out there than I thought!
On Lemmy that is. Kbin I believe replicates everything (unless I set my server up wrong). My server at the moment pulls in around 1.5 GB a day it seems. There is a pull request open on the kbin git repo for a feature to auto-remove old media. Personally I'd like the ability to turn on/off media replication. If an instance wants a complete copy in case of defederation/disconnection somehow, they can opt in and mirror all media that comes in. Most servers should just link to the original image source on the originating instance though.
Very true, if you don't mind losing your post history. A simple way to migrate subscriptions would be great for those folks that make a new account every once in awhile anyway.
It's not, unfortunately. The main issue I see with implementing that is all of your existing posts/comments would still link to your old account on other instances. So either your old instance would have to forward requests for your account to the new instance, or maybe ActivityPub has some way to push that update out and update your account's home across the fediverse. I don't know enough about it unfortunately.
You are welcome to create multiple accounts in any case. Suppose that defeats the purpose of the fediverse though.
Sorry, I should have included that info. You got me thinking, however, and I made the decision to defederate from lemmynsfw.com. I'm not against the communities it hosts, but I don't want to deal with any of the content hosting legal questions that come with it (or at least minimize it where I can). There do appear to be some posts that make it in to the 'random' microblog section that are NSFW, I will look into what I can do for those.
You can run your own instance and not allow anyone else to sign up, though I do agree the effort it requires if it's just for a single person is a lot. Spread out amongst friends, or other folks who don't mind chipping in, makes it seem a bit more sensible. But there is always the option to turn off registrations, and on Lemmy at least you can make registrations require approval.
The only other way your instance could incur more running costs than you'd like is if you have a community on your instance that gets very popular, and folks from all instances start posting to it (think stuff on Beehaw, Lemmy.world, etc.) Then your server needs to be the man in the middle, facilitating communication between users of other communities. But you always have the option of not allowing communities to be created, or stopping federation altogether if it gets to be too much. There really isn't a way it would suddenly cost you more money than you thought, unless you aren't monitoring it enough (which isn't much more than setting up notification emails for storage use, system crashes, etc).
Running your own instance is the only way to really be sure that the costs are being covered on the up-and-up. Otherwise you're just taking folks at their word. Your data, in the end, could always be sold to anyone. It is publically available through the ActivityPub protocol, after all. But that also means there's really no need to pay for it, so no one would buy it.
Your knock on the door analogy is exactly right--when I started my instance, I had to search every community that I wanted to see directly by URL. Then my server would send a message to that community's server saying that I subscribed to that community. Now, every time a post is made at that community, it's server sends my server an update. If I post a comment to a community on lemmy.ca (like I am now), from my kbin instance (remy.city), and you are reading it from kbin.social, that means my server first saved my comment locally, then sent it to lemmy.ca, and lemmy.ca sent it to your kbin.social because you subscribed to the community. So in that case, lemmy.ca is the 'authority', and is responsible for sending updates out to subscribed parties.
There is no such thing for instances--each new instance has to manually make a connection to another (i.e. a user on the new instance must subscribe to something from another instance). I think the tools like fediverse.observer are reading comments or other activity from popular instances, and are then compiling a list of the instances they find by doing that. But there is no central server/authority that makes communication between instances possible. Each instance has to talk to each other instance for it to happen. It's a bit inefficient but is necessary for decentralized communication.
The best way to know who owns the service you use it to own it yourself. That does come with a lot of overhead, though. I started my own kbin instance because I, like you, was worried about "what if one day I go to login and my home instance decided to shut off forever?" That can't happen now, besides if I forget to pay/something goes wrong with the server. But I enjoy tinkering so it works out in my case.
I think ultimately users are responsible for which instance they choose to sign up for. If there isn't much transparency on a certain instance, it may not be the one for you. I agree that the sign up pages could have some areas where more information could be shared. Of course, it is up to each instance admin to share accurate and factual information as to who they are/where the money comes from/goes etc.
I want to get into ham radio. Just like the fediverse, it's decentralized, and it's the original way to chat across the globe!