• 1 Post
  • 115 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle





  • It’s a corporate store with a unified return policy, which unfortunately lists acceptable reasons for return and a TV that works but has bad backlight bleed is not one of them. The lesson learned here is pay closer attention to the warranties and return policies when you buy things. Unfortunately I didn’t anticipate backlight bleed that bad even being a thing that could happen. There is often a small amount when buying LED TVs so I expected there to be some.

    Unfortunately this strategy depends on you having access to a retailer with a better policy, many may not.



  • Your opinion doesn’t matter. What matters is everyone else’s opinion. Our interpretation of that TV is “Obviously defective”, but in their eyes it turns on and plays media and sound, and if you crank the brightness all the way up then in very bright scenes you don’t notice the blue tint.

    My only actual remedy in this case was go to small claims court, which costs money on top of time off from work, and winning would require explaining backlight bleed to a 70 year old judge and that while it’s normal, not to this degree. And even if I won, this would be against Sony so maybe after that they ban me from doing any kind of business with them ever again and I’d lose access to thousands of dollars worth of games I’d pay for and lose the ability to play my $500 game console. This shit is just stacked against you and there’s no real winning except to not buy their product in the first place. But what do you do when any manufacturer on the market can and would do this to you? Never buy a TV again I suppose.




  • If your retailer has a generous enough policy to let you return an opened TV because simply because you don’t like it. I spent $1,200 on a Sony TV with backlight bleed issues that were so bad that half the screen was tinted blue. I tried to return it or get a replacement but was told by both the retailer and Sony support that half the screen being blue was “normal for LED TVs and within acceptable parameters” and to go fuck myself.






  • Encrypt-Keeper@lemmy.worldtoSelfhosted@lemmy.worldNew to selfhosting
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    12 days ago

    Unfortunately not as self hosting is really just an amalgamation of a number of different technologies, concepts, groups of best practices, and there are nine and a half viable ways to do any given thing you’ll want to do. For my day job I manage several public systems that serve millions of requests a day and even I can’t really give you a “One definitive way of doing things”, but I have my preferences.

    I think if you wanted a rough plan of what would be the most valuable things to learn in which order it would be

    1. Docker, especially persisting your storage and also how its network works. Use containerized services only on your local network at first to get a feel for things, and give yourself the ability to screw things ip without putting yourself in any danger.

    2. VPNs and how they work. You can start with a direct stupid simple VPN like WireGuard, or Tailscale if you want a mesh-VPN. This will allow you to reach your services remotely without having to worry too much about security and the micromanagement that can sometimes come with it.

    3. Reverse proxies for things you’d like to expose to the public. At this point you want to learn as well about things like server hardening, have a system in place to automate software updates etc. there’s a common misconception that using a reverse proxy is innately much safer than port forwarding directly to your services. It can help by obscuring your home IP, and if you pair it with a WAF of some kind that’ll help you with much of the chaff attacks that get tossed your way, but at the end of the day in both cases you’re exposing the web services on your local network to the internet at large, so you have to understand the risk and reward of doing this.




  • Well almost nothing in this world is priced based solely on the cost of materials so I wouldn’t waste your time thinking in terms like that. And it is in fact the case that a $500 router is demonstrably better than a $100 router. A $300 UniFi router is pretty much the ground floor of decent router performance, and even then you’re severely lacking in warranty and support, and the software is subpar.

    Beyond a certain point things that are more expensive are just more expensive because they are, not because they represent better quality.

    This is true, but the “certain point” in this case is not $100. $500 is much closer to being that point, and even then that’s only if you’re thinking in the scope of a consumer router. Business class routers are thousands of dollars.