Skip Navigation

Posts
2
Comments
1,623
Joined
2 yr. ago

  • I'm just curious if 'B' still retrieves the content from 'A' to show in user feeds.

    It works the other way around: instance A pushes the content to instance B. Therefore if A defederates B, then obviously A ain't gonna be pushing the content.

    There's an edge case where instance C is involved: A could comment on a post on C, and then C would forward it to B as well. But then B wouldn't be allowed to fetch the user profile from A anyway and might just drop it regardless. I'm not sure the particular way Lemmy handles this.

  • Ordered two drives from them, came in very well packaged and even included the PWDIS adapter. Very good deals. Could throw the box across the yard and the drives would probably survive.

  • As a starting point. Are there any hardware recommendations for a toy home server?

    Whatever you already have. Old desktop, even old laptop (those come with a built-in battery backup!). Failing what, Raspberry Pis are pretty popular and cheap and low power consumption, which makes it great if you're not sure how much you want to spend.

    Otherwise, ideally enough to run everything you need based on rough napkin math. Literally the only requirement is that the stuff you intend to run fits on it. For reference, my primary server which hosts my Lemmy instance (and emails and NextCloud and IRC and Matrix and Minecraft) is an old Xeon processor close to a third gen Intel i7 with 32GB of DDR3 memory, there's 5 virtual machines on it (one of which is the Lemmy one), and it feels perfectly sufficient for my needs. I could make it work with half of that no problem. My home lab machine is my wife's old Dell OptiPlex.

    Speaking of virtual machines, you can test the waters on your regular PC by just loading whatever OS you choose in a virtual machine (libvirt if you're on Linux, VirtualBox or VMware otherwise). Then play with it. When it works makes a snapshot. Continue playing with it, break it, revert to the last good snapshot. A real home server will basically be the same but as a real machine that's on 24/7. It's also useful to test things out as a practice run before putting them on your real server machine. It's also give you a rough idea how much resources it uses, and you can always grow your VM until it fits and then know how much you need for the real thing.

    Don't worry too much about getting it right (except the backups, get those right, verify and test those regularly). You will get it wrong and eventually tear it down and rebuild it better what what you learn (or want to learn). Once you gain more experience it'll start looking more and more like a real server setup, out of your own desire and needs.

  • I feel like a lot of the answers in this thread are throwing a lot of things with a lot of moving parts: Unraid, Docker, YunoHost, all that stuff. Those all still require generally knowing what the hell a Docker container is, how to use them and such.

    I wouldn't worry about any of that and start much simpler than that: just grab any old computer you want to be your home server or rent a VPS and start messing with it. Just pick something you think would be cool to run at home. Anything you run on your personal computer you wish was up 24/7? Start with that.

    Ultimately there's no right or wrong way to do things. It's all about that learning experience and building up that experience over time. You get good by trying out things, failing and learning. Don't want to learn Linux? Put Windows on it. You'll get a lot of flack for it maybe, but at the very least over time you'll probably learn why people don't use Windows for server stuff generally. Or maybe you'll like it, that happens too.

    Just pick a project and see it to completion. Although if you start with NextCloud and expose it publicly, maybe wait to be more comfortable with the security aspect before you start putting copies of your taxes and personal documents on it just in case.

    What would you like to self host to get started?

  • You shouldn't need sudo for a traceroute, so that's something special on your system.

    It's kind of like ping, it uses raw sockets and does need special privileges, but some distros make those SUID binaries so normal users can use them anyway.

  • No, because it's a balancing act. There's fraud everywhere, it's just how things are. It's not worth spending more than it gets back in the name of moral purity.

    The allegations of widespread fraud usually have an ulterior motive other than cutting down fraud. It's usually about the group of people needing the service as a whole and demonizing them with fraud allegations to cut down important social services. Nobody ever talks about banking fraud, stocks fraud, even when done by the literal president. It's always poor people on welfare programs, food stamps, healthcare that are somehow "the problem".

    I couldn't care less about poor people not declaring the 10h of work they managed to find, it's literally impossible to survive on food stamps and welfare without doing undeclared work and if you do declare it you just get penalized more than you earned. It's a system designed for you to not escape out of.

  • They have no business collecting any data in the first place. If I wanted my data collected I'd be using Chrome like everyone else. I'm not choosing to use their buggy ass inferior and slower browser for any of Mozilla's services, I'm choosing it because I want to support non-Chromium browsers and regain my privacy.

    There's no point whatsoever to using Firefox if it's just a worse Chrome.

  • Nope. The protocol is way too public for shadowbanning.

    You can be banned by other instances than your home instance, when that happens no new post/comment from you will federate to that instance in particular but the others still sees it as normal.

    For example, I could ban you on my instance, and I wouldn't see anything from you ever again, but my instance would be the only instance to see that ban.

    If you get banned from LW or lemmy.ml then a lot of people won't see you so that could definitely feel like a shadow ban, but there's nothing shadow about it you can see it in the mod log.

  • Permanently Deleted

    Jump
  • It ran fairly well for me out of the box. I think it's similar to trying to run Windows 98/2000/XP on modern VM software, it gets utterly confused and needs very specific hardware configuration to boot. Modern VMs run this good in big part because of paravirtualized hardware.

    I think what made Ubuntu so good is a combination of being based on Debian and also being there at the right time when Linux software was getting generally better. When I tried Mandrake it was too early for Wine to run any sort of game, codecs were lacking for video. When I tried Linux again with Ubuntu, there was now VirtualBox and computers fast enough to run that reasonably, graphics drivers were more usable. Compiz was popping off to show off that Xorg could now do compositing like macOS and Vista.

    Mandrake was good but limited by what Linux could do back then. Enjoyed it quite a bit but 9 year old me ran back to XP for the games. When I tried Ubuntu I was a bit older and more interested in programming and WoW ran great in Wine, so I managed to stick and have been on Linux since.

  • Permanently Deleted

    Jump
  • My very first distro I believe was Mandrake 10, it's the distro that planted the seed to eventually switch for real with Ubuntu 7.10

  • It doesn't have to be Mastodon or a social platform. It could just be a news/blog kinda deal that happens to support ActivityPub and people can subscribe to it to get it on their feeds.

  • If a community is hosted on instance A and a user that’s on instance B creates a post in this community, is the post hosted on A, B? Or are individual comments hosted on the instance of their respective authors?

    Both, but the instance the community is on is the one that forwards it to all the other instances will get it from.

    what happens when your account gets deleted? Are all my messages deleted? Does this happen to all instances (it syncs the deletion?)

    It does delete everything, but it's a bit buggt and cannot be guaranteed (because I can just restore from backup and undelete everything if I want).

    do instances cache posts and comments posted on other instances? If so, RAM or disk?

    Everything is pushed to all interested instances and host their own copy.

    will having too many instances increase the load of all instances? (If they all have to sync?)

    Only the ones that you subscribe to. But yes generally it would increase load on the big ones like lemmy.ml and lemmy.world since they're popular.

    But also in a way, it's no different than one user viewing the post, and your instance have a copy of it and can serve many more users. And the remote instance gets to push it to you when it's convenient. So not really a problem.

    if I want to check the comments of a post, does my client ask this to my instance of to the instance of the author or to the community's instance?

    Your instance already have a copy of it all. You always go through your instance (except media, depending on your instance's settings if the media cache/proxy is enabled).


    Roughly, how ActivityPub works is that instance A subscribes to B (by sending it a subscription request to a given community), and then B just sends A everything that happens from that point on. If you post, then A goes to B to inform it of the post, and then B broadcasts it it to everyone else. A owns the user, B owns the community.

    Most questions can then be answered by thinking of what would happen. What would happen if B bans a user from A? Well A doesn't care, neither does C, B will just ignore everything from that user. What happens if A bans the user? Well, that user can't post at all so indirectly also banned from B and C. What happens if A bans a user from C but C posts to B? A will ignore it, while B and C sees it. And so on.

    Each instance is independent and makes its own decisions, so the view is slightly different from instance to instance.

    And yes the fact everyone basically have a fully copy of everything does have some considerable privacy implications. A rogue instance can just ignore deletes and keep full edit histories. Every post, every comment and every vote is public information. It's entirely an honor system when it comes to deleting stuff.

  • Making the news and people unable to keep up is part of the strategy.

  • There's also a bunch of controversy around their premium features and it supposedly bricking devices it deems were pirated licenses.

  • He's going to create a crisis and have demands, threaten the tariffs until Canada makes some form of deal, postpone it, and come back with a new crisis, rinse and repeat.

  • Not really fixable unfortunately as both iOS and Android make a big assumption that an app is tied to a company with a well defined set of URLs it can handle. And it needs to know by the URL as well, not what it points to.

    It has no way of knowing it belongs to a fediverse app until it's already opened it up in the browser.

  • Because phones are a mess of out of tree patches specific to that phone model with zero hope of being upstreamed into the Linux kernel without a cleaner rewrite because it's not good, it's made to work and nothing more. They do stuff like just copy pasting the drivers into the project for the next chip, make some changes, and now you have several versions of the same driver for a whole bunch of slighly different chips. The community can't keep up with that or make it generic enough.

    It's improved but companies like Qualcomm also used to basically drop the code to the manufacturers when the chip launches and then move on with little maintenance for the code and stop maintaining the code once the chip is not produced anymore. Manufacturers don't have the expertise to maintain that forever nor the will, so you end up with a kernel that keeps aging and isn't keeping up with Android and the community hasn't been successful in integrating it all either.

    Google's been pushing hard for this to improve but they're the only ones to even care. Samsung and others would much rather sell you a new phone.

    There's also the problem that phones don't really have a BIOS, the kernel is expected to just know where the devices are via the device tree. So each phone needs a specially built kernel for it too.

    Projects like LineageOS often manage to push those phones a couple versions longer but eventually interest dies as well because of kernel pains.