Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RE
Posts
3
Comments
235
Joined
2 yr. ago

  • Nissan Motors v. Nissan Computer

    In 1980, Uzi Nissan founded Nissan Foreign Car, an automobile service, in Raleigh, North Carolina.[9][10] In 1987, Uzi Nissan founded Nissan International, Ltd, an import/export company that traded primarily in heavy equipment and computers.[11] On 14 May 1991, Uzi Nissan founded Nissan Computer Corporation, which provides sales and service of personal computers, servers, and computer parts, as well as internet hosting and development. Nissan Computer registered nissan.com for its use on 4 June 1994, five years prior to Nissan Motor Corporation's interest in the domain.[10][2]

    Nissan Motors considered Nissan Computer's use of the name to be trademark dilution, and laid claim to the domain by alleging cyber squatting. However, Nissan Computer was named after its owner, Uzi Nissan.[13][14][15] Following the outcome of the case, Nissan Motors uses the name nissanusa.com for its U.S. website.

    Uzi Nissan died in 2020 due to covid and the website is now no more, but it used to contains his account abut Nissan suing him for the domain and he spent years and about a million dollar to defend himself. He won and Nissan was ordered to pay $50,000 for his trouble, so he was furious. More details can be found in the internet archive snapshot: https://web.archive.org/web/20190608101443/https://www.digest.com/Big_Story.php

  • I actually tried with latest version of Sync Dev already installed in my phone. What version are you using? Also, which google docs? I only follow the instruction in revanced manager that said to put the client id string in /data/storage/emulated/0/reddit_client_id_revanced.txt

  • There is an option in revanced manager to patch reddit sync to use your own oauth client id. I just tried it out and the patched reddit sync just crashed when it start loading the frontpage. oh well.

  • It's simple, really.

    • if you have Reddit app installed, uninstall it first
    • download revanced manager and install the apk. https://revanced.app/
    • find Reddit app's apk in apkmirror.com and download it
    • open revanced manager and select Patcher -> "select an application" -> storage and select the downloaded Reddit apk.
    • make sure "disable ads" is in the list of selected patches
    • run the patcher, wait until it completed
    • don't install the resulting apk right away yet. Instead, open the "..." menu on the top right of the screen and backup the patched apk
    • close the revanced manager app and open your file manager. Locate the patched apk you just backed up in the download folder, then install it.

    Note that I haven't actually tested this with actual Reddit app.

    Edit: oops, replied to a wrong thread

  • Also, do not post personal information here ever. Once you posted a comment, there are no guarantee you can fully delete them later. If you post a personal information, there is a chance that it might still up in some instance somewhere even if you attempt to delete it. Some instance might not receive the activitypub push about the deletion due to federation issue/lags, getting blocked from the original instance, bugs or random internet connection issues. Use other channel if you need to share personal info to fellow lemmings so you can be sure to purge them if needed later (e.g a link to pastebin, discord, etc)

  • (You don’t need to put the community name in the title, especially not with “@”, which signifies usernames. Communities are prefixed by “!”.)

    They posted from mastodon though, so they do need to mention the community in order to cross post there.

  • Security is a rabbit hole and you can go very deep depending on your risk model (an ordinary middle class people has different cybersecurity risk than, say, a CEO of a major bank). Let's say you are an ordinary lemming that don't have to be worry about being specifically targeted by a hacker group or a nation state, you just don't want some botnets get into your network and take over your IoT stuff, I think the following is reasonable enough:

    • by deploying your HA instance using docker or VM, if it somehow got compromized by an automated botnets / malware, the infection will be contained and you can easily wipe it off and start again. Real hackers might be able to escape the sandbox but run of the mills botnets that always scan the internet for exploits usually don't.
    • setup OTP: https://www.home-assistant.io/docs/authentication/multi-factor-auth/
    • you can max out security level of HA login page (or the entire HA) using cloudflare's firewall rule: https://developers.cloudflare.com/firewall/cf-dashboard/create-edit-delete-rules/ . This should stop most bots from trying to bruteforce your login page.
    • assuming you're using cloudflare tunnel, you aren't actually exposing your entire machine to the internet, but just the homeassistant port. That being said, it'll be nice if you take some precaution and disable root ssh login and perhaps disallow password login too, just for peace of mind.
  • In a way, this seems like a divorced couple quarrel. One party is super angry and felt betrayed, while the other part feels they didn't do anything wrong and was the actual victim instead.

    The community is like "How could you betray our trust! After all these years of our support!" and Red Hat is like "I didn't do anything wrong! Also, your support is overrated anyway. You're actually more like a leech."

  • Yes, that's totally fair, but a lot of people in the open source world, especially individual contributor, will only support an open-source product based on how many goodwill the backing company provides. Red Hat, before the IBM acquisition, is on the top of the list due to their enormous goodwill towards the open source community. Their willingness to support CentOS, which essentially making RHEL free and cutting into Red Hat's revenue, created a lot of respect among Linux supporters, which in turns promoted usage of CentOS and RHEL and provides integration for CentOS/RHEL on their own open source projects. Red Hat became this big was partially due to the support and promotion from the Linux enthusiasts advocating their use in their companies.

    The recent moves understandably made those people feel betrayed by Red Hat. Sure it's within Red Hat's right to do so, but in doing so, they burn a lot of goodwill and trust from their open source community.

  • Don't forget Red Hat wouldn't have problem with the "rebuilders" eating their lunch if they didn't kill CentOS in the first place. People that don't need support would just use CentOS, and people that do need support would still buy RHEL instead of paying Rocky, Alma and Rocky wouldn't exists, and Oracle Linux would've still a niche product. But greed (or IBM?) got the better of them and they killed CentOS to increase their short term revenue. Now they're getting bitten in the ass for that short-sighted decision (NASA contract with Rocky) and double down with an even stupider decision. They will surely get bitten in the ass again over this decision and probably will triple down with an even more stupider decision.

    I haven’t seen anything about RHEL cutting off paying customers who share source. It wasn’t in the link you shared, it wasn’t in any of the links provided by Rocky in said blog post you shared. I’d love to read about it if I’ve missed it, and reform my opinions.

    I think it's mentioned in red hat portal ToC. There are screenshots around the internet is you look for it.

  • The problem with Rocky is that they also stand to make money out of the same source code which is the disingenuous part, in my opinion.

    If only Red Had didn't kill CentOS, they won't have this problem now. But noooo. Their IBM overlord demand more revenue, so they killed CentOS to force their users to buy RHEL licenses which increase their short term profits. By killing CentOS, they created a vacuum that's now filled by Rocky, Alma and Oracle Linux. Red Hat see them as eating their lunch, so they double down on making stupid decision again.

    I'm sure their decision to make accessing RHEL source code harder will backfire again within a few years and Red Had will make an even dumber move again.