Okay yes this makes sense. Although, honestly i think I’d prefer the AP method of doing it because BlueSky sends ALL content to all nodes, so it’s MUCH less cost effective to join with a private server.

I run my own lemmy instance, so i know the data volume since 2023 has been probably like a terabyte or so. But, with BlueSky I’d have to account for the data volume of all users on the platform as a whole, bringing the data volume way up to tens of terabytes (a guess based almost entirely on nothing).

So it really boils down to yes I agree that AP has problems with data accessibility, but I’d prefer that over unnecessary data redundancy

… but at least the rest of their system is actually substantially more decentralized architecturally than AP is.

In the blog post you linked, neither the author or myself came to your conclusion:

However, I stand by my assertions that Bluesky is not meaningfully decentralized and that it is certainly not federated according to any technical definition of federation we have had in a decentralized social network context previously. To claim that Bluesky is decentralized or federated in its current form moves the goalposts of both of those terms, which I find unacceptable.

I don’t doubt that, I’m saying this more because there are additional routes that i had to configure in NPM to get lemmy working properly. This may be where OP is having issues, you can probably set them up in CF too but I have no idea.

Are you pointing cloudflare directly to Lemmy? I have mine going from cloudflare to Nginx Proxy Manager configured to serve Lemmy.

There is some additional configuration necessary for a reverse proxy in front of Lemmy, which is potentially where things are getting messed up for you?

I hope that lemmy doesn’t grow any heavier than it is growing right now

I hope for more like minded individuals to help them out

How is the latter supposed to happen without the former? Like it or not, many of us are here solely because Reddit went to shit with their extreme monetization. Lemmy is still a really small community and absolutely NEEDS larger adoption in order to remain a viable option

Exactly. While Lemmy isn’t exactly like the Internet archive, at least its self hosted so you could preserve anything you want for as long as you wanted on here

Yes, or if you find a solution you can post it here for preservation. I’ve posted some guides and info that i pulled from Reddit onto here because the way things are going, I can’t guarantee that information will still be available in a years time.

It’s a program that uses an SDR to pick up the signals broadcasted by planes (ADS-B) containing their flight information. Then the data gets uploaded to an aggregator (FR24, Flight Aware, ADS-B Exchange) that gives a global view of all planes in the sky.

You can use the aggregators for free without uploading, but you get some perks for being a contributor. I just do it because it’s cool and I use the platforms for getting info on flights I’m taking (you can tell if your flight is gonna be delayed if the plane is delayed elsewhere for example).

I took an old pi and threw a flight tracker on there. Now i have premium accounts on FR24, FlightAware, and ADS-B Exchange.

I have a few other pis which run other stuff though, my favorite thing to do is install nginx proxy manager and tailscale, then use it as an entry point to my network (this was born out of my main server being a bit unstable, which i have since fixed but kept NPM off of it because the pi is pretty much set and forget)

Ehhh i don’t think that justifies having people pay to stream, i doubt a lot of people even ever used that functionality and yeah they could have just pay walled it if it was that much of a problem.

Final thought: there’s also a fair chance (I’d rate it at almost 70%) that they presented this to us because they knew it would piss people off. Then, in a week or so, they will post a “we’re sorry, is this better?” with the changes they’re ACTUALLY going to make. A ploy to make us blindly agree to whatever they want because “at least it’s better than what they wanted originally” 🙄🙄

The audacity of this company to increase prices when:

A) downloads are locked behind the paywall but havent worked in years (probably close to a decade at this point)

B) they focus all the development time on bringing bullshit to the platform (live tv, rentals, other streaming app searches, etc)

Requiring a subscription for remote access is actually fucking insane, they don’t have any bandwidth costs associated with that other than authentication so ???

This will drive people to Jellyfin, and watch how fast Plex drops into irrelevance when all the selfhosters move away. Plex is (now was) the #1 thing to that both myself and others in this community would recommend to someone looking to get into selfhosting. ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯ not anymore, wonder how much the revenue will drop?

Nice! So you were able to get everything working?

Hey, can you elaborate a little bit more? Based on my Google search, casa-os is a front end for selfhosting? So, I would assume that you are not connecting to the right ports.

So, my assumption is: casa-os is using your port 80 and 443, so when you set up the DNS A Record, and navigate to it in your browser, it takes you to the homepage for casa-os. If this is indeed the case, then you have a couple options. You could:

1. Change the ports that casa-os is using and then rebind NGINX to 80 and 443
2. set up a second device just for NGINX (which is what I do, I use a Raspberry Pi just for network entry for stability reasons)
3. (I’ve never done this, so YMMV) you might be able to use Tailscale Serve
   • You would have it serve the port for NGINX under your Tailscale DNS name
   • Once you’re there, I imagine that you could use a CNAME DNS record or something on your custom domain in order to continue using the domains that you want, sub domains, SSL, etc.

Let me know what ends up working for you. I hope that either option 1 or 3 work, if those fail then you can definitely get it working via option 2 :)

Can you provide an example? I’m a little confused by what you mean.

Once the port is open, you should be able to access it via the tailscale IP just as you would locally on your network

Ahhh i gotcha, so basically it forwards traffic through the pi so that you can send traffic through tailscale on devices that don’t support it? Sounds like a cool idea tbh

Good on ya for the tailscale/syncthing though, off-site backups are super important! If Jellyfin supported federation you could merge your library and your parents library and have it all accessible through each of your local instances. Maybe one day they’ll add it, i think it would be a killer feature.

Glad the write-up helped though, it should at least help you move towards single instances (at least for immich) since you can just backup on tailscale via the dns entry!

Glad to help, yes that is a perfect example of how you could use this to your benefit. Much easier to just tell people to enable VPN (tailscale) and navigate to an easy to remember URL.

I’m somewhere in the middle, I do cybersecurity professionally so i work a lot with technical stuff but my hobbies are much deeper in it so theres a lot of stuff i don’t know. But, thanks to these communities i was able to learn how to do a lot of things and have now levelled up into doing the research on my own and trying to give back :)

In your dream scenario, is that each family member would be hosting immich/jellyfin on their pi zero? Or is the pi zero somehow routing traffic for them back to your server for jellyfin and immich?

Happy to help!

Side note, if you want to make publicly available services, you could use cloudflare tunnels. They work in a similar way – letting your services be accessible over the Internet without needing to open ports. Some other people in the comments have mentioned that Tailscale funnel can also work for this, but i haven’t used it so I can’t really advise on that front

Just looked it up, seems to pretty cool. Does it only work with one service though? You proxy one port to your tailscale domain name, but does it do routing for additional ports at the same time?

I’ve only done surface level research into it, and honestly didn’t come across this when i was doing the research for NGINX Proxy Manager, but it seems a little limited in comparison.

Happy to be proven wrong though, any easy solution is a good solution :)