Skip Navigation

Posts
3
Comments
113
Joined
2 yr. ago

  • Not sure if I entirely understand what you're asking but here's my setup that sounds similar-ish that might help.

    I've got essentially 3 machines

    1. Download machine - contains Sonarr/Radar/Nzbget, etc... This machine isn't very powerful but it has A LOT of RAM.
    2. A Nas - this is where everything gets downloaded to. Primarily this machine just has a lot of HDD space.
    3. Jellyfin box -- Decent RAM and a beefy CPU for transcoding.

    The download machine has a network share to download directly to the NAS in a special /downloads/ folder. Once a download completes Sonarr, etc... move it to it's correct media folder.

    Finally the Jellyfin machine is monitoring the media folders for changes.

    I assume you could set up something similar with Plex instead of jellyfin and then store the fully downloaded files on a separate machine with a network drive, so Plex can see it. Essentially the NAS for you would be two machines one (the seedbox) for the partial downloads and a local NAS for the fully downloaded files?

    Anyway, not sure if that's what you're looking for.

  • Think of Lemmy as email. Each post or comment is just an email sent to a distribution group (a community). If your email server goes down, all of those users and distribution groups are gone. Now I'll still have the emails I sent to you in my email box but you won't be able to see them as your email server is offline. Sure you could create a new account on a new server but you'd have to tell everyone about your new address (federate) but there's nothing to associate your old user with your new one and there's no way to backfill data. I could reply-all or forward (comment) on to your new address but there's still no way to associate those old posts with your new account.

  • So the builder pattern is supposed to solve the problem of: if you have a large number of optional fields that may or may not need to be set to construct your object. Then once the dev has called all of the setters that they require, they call build to fully realize that object.

    Some rules that all builders should follow:

    • All setters SHOULD represent optional parameters. (Or ones that have a default value). If a parameter is required for all instances, include it in the constructor of the Builder itself.
    • All setters SHOULD return a copy of the Builder. This way you can chain calls off of each other.
    • Setters SHOULD do nothing more than store the provided value in a field local to the builder itself and then return itself (or a copy of itself).
    • You MUST expose a .build() method that will return the fully realized object. This method should essentially call the constructor for your target object using all of the parameters, regardless if a setter was called or not. Obviously any value where the setter wasn't called will be null or some default value.
  • Yes but what if you search and find a post that doesn't exist on your home instance? You'd be taken to a 404 page and can't do anything.

    But I've got an issue on GitHub for this. And just raised a PR on Lemmy to support the changes I need for this. But a reminder, once you can search all instances you may encounter 404s opening the posts that you find.

  • https://www.search-lemmy.com

    You can do advanced filters on posts or communities. Feel free to provide feedback as well. I'm still working on the order of the results, etc...

  • Not necessarily. I have several servers behind Cloudflare for free. I'm just limited on analytics, some advanced firewall settings, advanced cache management and maybe a few other features that I don't use. But the basic service is free.

    https://www.cloudflare.com/plans/free/

  • If an instance goes down (permanently), federation of all of the communities hosted by that instance essentially stop. The content that has already been posted remains but anything new added to those communities only remain on your home instance. The only way for federation to resume is for that instance to come back online with the same domain it started with.

  • Same. Honestly I need to create a community just for this tool IMO. But I don't have the time to moderate it.

  • With ActivityPub all of the primary ids contain the domain of the hosting server. So if you lose your domain none of the other instances know that you're the authority on those communities, posts, comments or users. So essentially federation breaks with all of the old data.

  • I'm also running Ubuntu as my main machine at home. (I have a Mac and do Android development for my day job).

    But at home, I do a lot of website and backend dev.

    1. Code in VSCode
    2. Build using docker buildx
    3. Test using a local container on my machine
    4. Upload the tested code to a feature brach on git (self hosted server)
    5. Download that same feature branch on a RaspberryPi for QA testing.
    6. Merge that same code to develop 6a. That kicks off a CI build that deploys a set of docker images to DockerHub.
    7. Merge that to main/master.
    8. That kicks off another CI build.
    9. SSH into my prod machine and run docker compose up -d
  • Unless you have an account there's no easy way to get access to the content on the page. Once you have an account there's technically nothing stopping you from just saving the HTML file to your computer.

    Something else you can try though, assuming you don't have an account, is to just turn off JavaScript. If the site lets you partially load the content and then asks you to create an account to read more, they usually just block the content by having JavaScript add an opaque overlay. With JavaScript disabled, obviously it's not there to add the overlay and you're able to keep reading.

  • That looks like 8.8.8.8 actually responded. The ::1 is ipv6's localhost which seems odd. As for the wong ipv4 I'm not sure.

    I normally see something like requested 8.8.8.8 but 1.2.3.4 responded if the router was forcing traffic to their DNS servers.

    You can also specify the DNS server to use when using nslookup like: nslookup www.google.com 1.1.1.1. And you can see if you get and different answers from there. But what you posted doesn't seem out of the ordinary other than the ::1.

    Edit just for shits and giggles also try nslookup xx.xx.xx.xx where xx.xx.... is the wrong up from the other side of the world and see what domain it returns.

  • Another thing that can be happening is that the router or firewall is redirecting all port 53 traffic to their internal DNS servers. (I do the same thing at home to prevent certain devices from ignoring my router's DNS settings cough Android cough)

    One way you can check for this is to run "nslookup some.domain" from a terminal and see where the response comes from.

  • It searches the title and body. It also automatically searches for similar words like. Like 'bike', 'biking', 'bikes' (aka stemming). Granted though, I'm still improving the page ranking as time goes on.

  • Totally agree.

    Just wanted to point out that app development has different costs, sometimes none, associated with it vs hosting something like a Lemmy instance.

    But p.s. logos and artwork can be bundled with the app itself. I assume, but I could be wrong, that many mobile devs have at least a handful of test devices available. Although the simulators have come a long way. But agreed test devices, especially newer ones can be expensive.