• 1 Post
  • 560 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • Looks really nice and seems like it should be a great foundation for future development. Personally I can’t lose Nextcloud until there are sufficiently featureful and reliable clients for Linux, Windows, Android that synchronize a local copy and help manage the inevitable file deconfliction (Nextcloud Desktop only barely qualifies at this, but it does technically qualify and that represents the minimum viable product for me). I’m not sure a WebDav client alone is enough to satisfy this criteria, but I am not going to pretend I am actually familiar with any WebDav clients so maybe they already exist.


  • You’re on the right track. Like everything else in self-hosting you will learn and develop new strategies and scale things up to an appropriate level as you go and as your homelab grows. I think the key is to start with something immediately achievable, and iterate fast, aiming for continuous improvement.

    My first idea was much like yours, very traditional documentation, with words, in a document. I quickly found the same thing you did, it’s half-baked and insufficient. There’s simply no way to make make it match the actual state of the system perfectly and it is simply inadequate to use English alone to explain what I did because that ends up being too vague to be useful in a technical sense.

    My next realization was that in most cases what I really wanted was to be able to know every single command I had ever run, basically without exception. So I started documenting that instead of focusing on the wording and the explanations. Then I started to feel like I wasn’t capturing every command reliably because I would get distracted trying to figure out a problem and forget to, and it was duplication of effort to copy and paste commands from the console to the document or vice versa. That turned into the idea of collecting bunches of commands together into a script, that I could potentially just run, which would at least reduce the risk of gaps and missing steps. Then I could put the commands I wanted to run right into the script, run the script, and then save it for posterity, knowing I’d accurately captured both the commands I ran and the changes I made to get it working by keeping it in version control.

    But upon attempting to do so, I found that just a bunch of long lists of commands on their own isn’t terribly useful so I started to group all the lists up, attempting to find commonalities by things like server or service, and then starting organize them better into scripts for different roles and intents that I could apply to any server or service, and over time this started to develop into quite a library of scripts. As I was doing this organizing I realized that as long as I made sure the script was functionally idempotent (doesn’t change behaviors or duplicate work when run repeatedly, it’s an important concept) I can guarantee that all my commands are properly documented and also that they have all been run – and if they haven’t, or I’m not sure, I can just run the script again as it’s supposed to always be safe to re-run no matter what state the system is in. So I started moving more and more to this strategy, until I realized that if I just organized this well enough, and made the scripts run automatically when they are changed or updated, I could not only improve my guarantees of having all these commands reliably run, but also quickly run them on many different servers and services all at once without even having to think about it.

    There are some downsides of course, this leaves the potential of bugs in the scripts that make it not idempotent or not safe to re-run, and the only thing I can do is try to make sure they don’t happen, and if they do, identify and fix these bugs when they happen. The next step is probably to have some kind of testing process and environment (preferably automated) but now I’m really getting into the weeds. But at least I don’t really have any concerns that my system is undocumented anymore. I can quickly reference almost anything it’s doing or how it’s set up. That said, one other risk is that the system of scripts and automation becomes so complex that they start being too complex to quickly untangle, and at that point I’ll need better documentation for them. And ultimately you get into a circle of how do you validate the things your scripts are doing are actually working and doing what you expect them to do and that nothing is being missed, and usually you run back into the same ideas that doomed your documentation from the start, consistency and accuracy.

    It also opens an attack vector, where somebody gaining access to these scripts not only gains all the most detailed knowledge of how your system is configured but also the potential to inject commands into those scripts and run them anywhere, so you have to make sure to treat these scripts and systems like the crown jewels they are. If they are compromised, you are in serious trouble.

    By now I have of course realized (and you all probably have too) that I have independently re-invented infrastructure-as-code. There are tools and systems (ansible and terraform come to mind) to help you do this, and at some point I may decide to take advantage of them but personally I’m not there yet. Maybe soon. If you want to skip the intermediate steps I did, you might even be able to skip directly to that approach. But personally I think there is value in the process, it helps defining your needs and building your understanding that there really isn’t anything magical going on behind the scenes and that may help prevent these tools from turning into a black box which isn’t actually going to help you understand your system.

    Do I have a perfect system? Of course not. In a lot of ways it’s probably horrific and I’m sure there are more experienced professionals out there cringing or perhaps already furiously warming up their keyboards. But I learned a lot, understand a lot more than I did when I started, and you can too. Maybe you’ll follow the same path I did, maybe you won’t. But you’ll get there.



  • Nextcloud is just really slow. It is what it is, I don’t use it for any things that are huge, numerous, or need speed. For that I use SyncThing or something even more specialized depending on what exactly I’m trying to do.

    Nextcloud is just my easy and convenient little dropbox, and I treat it like it’s an oldschool free dropbox with limited space that’s going to nag me to upgrade if I put too much stuff in it. It won’t nag me to upgrade, but it will get slow. So I just don’t stress it out. So I only use it to store little convenience things that I want easy access to on all my machines without any fuss. For documents and “home directory” and syncing my calendars and stuff like that it’s great and serves the purpose.

    I haven’t used Seafile. Features sound good, minus the AI buzzword soup, but it looks a little too corporate-enterprisey for me, with minimal commitment to open source and no actual link to anything open source on their website, I don’t doubt that it exists, somewhere, but that raises red flags for potential future (if not in-progress) enshittification to me. After eventually finding their github repo (with no help from them) I finally found a link to build instructions and… it’s a broken link. They don’t seem to actually be looking for contributions or they’re just going through the motions. Open source “community” is clearly not the target audience for their “community edition”, not really.

    I’ll stick to SyncThing.


  • According to the protocol they share (ActivityPub) communities and hashtags are essentially the same thing, they’re a grouping containing many posts. Typing out a hashtag is how you tell Mastodon to add your post to that “hashtag group” (and you can add your post to multiple hashtags). In Lemmy, the community you post in IS the group (and you can cross-post it to multiple communities). The result is the same. They’re the same thing, just different ways of connecting your posts into them, and displayed in very different ways depending on which part of the Fediverse you’re using.


  • Sounds like you’re doing fine to me. The stakes are indeed higher, but that is because what you’re doing is important.

    As the Bene Gesserit teaches: I must not fear. Fear is the mind-killer. Fear is the little-death that brings total obliteration. I will face my fear.

    Make your best effort at security and backups, use your fears to inform a sober assessment of the risks and pitfalls, and ask for help when you need to, but don’t let it stop you from accomplishing what you want to. The self-hosting must flow.



  • I agree with you. I think many baskets is better than guessing that you’re exclusively picking the right basket. The key question is how you (and from here on I am referring to “you, as a creator” not “you, personally”) are allocating your effort across the many baskets. Even acknowledging that there are many baskets and options is a necessary starting point. If you are treating the options with lower population and lower views as second class citizens and just throwing your content up there too without any additional thought or attention that’s fair, given where they are right now, and at least it’s a step in the right direction, but you need to start thinking about the next step too. If you look at Peertube and see a waste of your time that has no future, you’re entitled to your opinion but I’d respectfully disagree. I think it pretty clearly is the future or at least a step towards it. If you think we’ll simply never escape Youtube, then by all means bend the knee to them and don’t waste your time anywhere else.

    But remember that Youtube was new and disruptive once too and people said it could never succeed at what it was trying to do. And now that it’s succeeded, we think it could never fail, it’s too big to fail. Things don’t succeed until they do. Things don’t fail until they do. It doesn’t happen overnight, it happens gradually but if you realize things are shifting early, and spend your effort wisely in the places where your efforts will become most valuable, you’ll be ahead of the curve and in a really good position to maximize the benefit. Or by the time you realize it’s happening, you’re already falling behind and you’ll be scrambling to make the transition. And if you’re completely wrong and the alternative just quietly dies as they sometimes do, your effort is wasted but you’re otherwise not really any worse off than you already are.

    Is any alternative video platform worth investing your time and effort in? Not based on what any of them are today, no. But based on what they will be? I think so. You have to think so too, if you want them to succeed. Will they succeed? Can Youtube ever fail? Only time, and you, each and every humble individual content creator, will decide.

    Be the change you want to see in the world, don’t wait for it for it to happen to you.








  • It’s definitely not burn-in, it’s likely some kind of defect in the backlighting system. For most LCDs the “backlight” is essentially a big thin white/mirrored panel reflecting or diffusing light in a very carefully consistent way from a very bright light source, typically either a fluorescent tube at the bottom or more commonly nowadays evenly spaced strips of LEDs. Some higher end models use more elaborate designs but they’re the minority. Defects in the backlight panel, the back of the LCD panel, or stuff like dust or even insects getting inside that reflective/diffuser chamber will affect the consistency of the backlight as it both blocks a bit of the light from reaching some places and reflects it to other places it shouldn’t be. That’s what it looks like is happening here. It could be some kind of delamination of some of the surfaces inside the TV, or it could be some puff of dust that somehow got inside, or even something like a spider decided that was a great place for a cobweb. Without opening the panel it’s hard to say what’s going on exactly, it might just need a very delicate cleaning or it might need replacement parts.

    If you’re afraid of spiders, I’m sorry, you just have to burn the house down now, it’s the only way to be sure.





  • Me too. At least with Temu and Wish I know the majority of my money is going directly to some crook in China and not to Bezos. Cut out the extra middleman. Same low quality of goods, direct from the drop-shipper lying about them or perhaps even the factory counterfeiting them. It’s a substantial improvement in supply chain honesty and legitimacy, you’re left with no illusions about the products and all the reviews are fake, so it’s deeply refreshing to not have to try to figure any of it out. It’s always 100% consistent. You know exactly what to expect, with no worry you’re accidentally going to overpay for something you think is genuine and receive a box full of rocks that’s obviously been opened, stolen and returned, nah not on these sites. You’ll get exactly what’s pictured (not to scale necessarily, though). Way more reliable than Amazon.


  • Not sure if you’re being sarcastic, but I want to emphasize that whether you mean it that way or not, it’s true. Each person helping and participating makes the work a little easier and success a little closer. A movement requires leaders and builders, certainly, and those people are often doing a lot of heavy lifting. But it also simply requires members, and numbers, and people just showing up. Your support, simply just being here, means more than you might know.