screaming in digital

fixate on what you think you know… you’re missing what you don’t though.

  • 1 Post
  • 254 Comments
Joined 3 years ago
cake
Cake day: May 7th, 2023

help-circle


  • ymmv, but debian has always been near perfect through upgrades for me: even a recent buster -> bullseye -> bookworm -> trixie went smoothly.

    issues usually arise from not maintaining a clean debian stable install (e.g. you were using backports or lots of 3rd party repos). if those are cleaned up prior things still usually go well.

    not saying you didn’t have issues, but in my experience with with lots and lots of debian systems, upgrades have been 99.9% cakewalk.


  • honestly, I have always had pretty decent experiences with non-oem lead-acid batteries. my local battery place has a decent supply and longevity is roughly the same as the oem ones (3-4 years). I have never had any issues (type or frequency) that were not also an issue with oem batteries.

    almost no UPS mfcr makes their own batteries, so if you strip off the labeling from the oem ones, you may even find an exact replacement.

    edit: another advantage of a local place is the core-return rebate and disposal of your old batteries.










  • You shouldn’t be getting downvoted.

    agreed. a tad snarky, but it was an honest opinion. lemmy will grow and communities will fill out.

    dumb idea here..

    one thing that may help are clients that allow community aggregation into meta communities. this would allow users to be presented with a themed superfeed of similar communities across many instances. easiest done at the client level (no protocol changes needed), but could be extended to communities using meta tags or moderator inclusion into meta communities with protocol help. protocol support would also allow meta communities to be presented via the web interface.

    perhaps this has already been done in some clients. if implemented thoughtfully it could be interesting and perhaps even useful.



  • federation certainly allows the bubble to close - {dot}world is an example; zero hate, people can absolutely choose to ensmollen their PoV if that makes their world safer. the nice thing is, interesting, thriving alter-views are only a federated instance away :-)

    I tend towards the democratic socialist point of view as a default, but damn-me if hexbear isn’t both entertaining and informative, even if I disagree with some of their more… spicy(?) positions (sometimes vehemently).

    lemmy{dot}ml is one of the most widely federated instances around, primarily because its a pretty diverse mix of lefty and lefty-ish ideas. lemmygrad{dot} hexbear{dot}net and blahaj{dot}zone and others equality as infuriating/interesting are all accessible from lemmy{dot}ml. its a pretty ideal instance, for me at least.

    one thing I do try to make a point of doing is preferentially interacting on non {dot}world posts and comments. many peeps will post across community instances to encourage engagent diversity. keeping things active on non-{dot}world communities helps everyone.





  • its not, really. and its something you get used to and come to appreciate.

    the city analogy is a great one - every town has its own flavor. many towns build roads (federation) between them so all inhabitants can easily travel to each other… as a city.

    some towns self-isolate or are isolated from other towns (defederated) for all sorts of reasons and, if you want to see what they have to offer, you can set up a house directly in that town or another town with a road to (federated with) that town. it really does allow some very cool places to thrive - like the internet was before it was purchased.

    lemmy{dot}.world chooses to keep things pretty… bland? thats their right, but there is quite a bit of quality spiciness out there if you have a house in a well connected (widely federated) town or decide to set up a few additional houses in some of the more exotic towns.

    does anyone have a federation graph up and running right now? should be easy-ish based on instance published federation lists.


  • agreed. you are using DNS-01 challenges. so the workflow is…

    your local certbot machine initiates an https connection to the letsencrypt servers to start the DNS-01 challenge. during this HTTPS dialog, your local certbot is informed of the key material to insert into your DNS records. your local certbot then modifies your netcup DNS server (hosted remotely, not on your local network) with the keying material and the letsencrypt servers verify that the keys are actually there, proving that you control the domain. the letsencrypt serves then issue you the certificate (again, via HTTPS) and your local certbot stores it in your local host.

    the issue is most likely stems from the initial HTTPS connection that certbot tries to make to the let’s encrypt servers. while your firewall allows this traffic out, it does not allow return traffic back in because of your explicit blocking of US (and perhaps other) based addresses.

    even through your are using DNS for your domain autentocation, your local host - the machine running certbot - is unable to initiate the certificate transfer because of the firewall blocking return traffic.

    the two external networks (and, therefore IP ranges/subnets/etc) that are important here are the let’s encrypt servers and the netcup DNS servers. certbot will have to talk to both of these in order to function.