![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/d3d059e3-fa3d-45af-ac93-ac894beba378.png)
I have pocket fluff and no tea in my pocket.
I have pocket fluff and no tea in my pocket.
You never know when a filthy Baggins is going to come along and ask, “What have I got in my pocket?”
I never claimed it was. But Java comes with its own baggage of Oracle shenanigans (they could start licensing drama with open source forks just like they did a few years ago) and java security patches means maintenance. All of which would be completely unnecessary if Ubiquity let you setup the AP with ssl.
The controller interface is amazing. But it, or a phone app should not be required to set up an AP.
No, Pihole doesn’t help.
I think the reason you say you haven’t seen an ad on Windows is because the ads aren’t the traditional ads like you see on a webpage.
When someone talks about an ad on Windows, they are referring to the Spotify app presinstalled in the Start Menu, the OneDrive prompt for backing up during setup, and the weather bug on the taskbar that brings up news if you click it.
You might think that a weather widget isn’t an ad, but the idea is you click it, see a relevant news article, click the news article and you are taken to a traditional webpage with ads.
If you were actually able to set it up via ssh, then you should be able to point me to the documentation for the Ubiquity AP cli.
I’m not sure if you are a fanboi or a shill but it is dishonest to claim that you say you could configure your Ubiquity AP when Ubiquity itself refuses to provide documentation of the cli interface.
Another poster said the same thing and linked to the same thread I found years ago which says in effect, “There is no official cli documentation for the APs. You might be able to sneak a few commands by digging through the forums.”
Docker
Yes, the Java app dockerized.
Requiring a phone app, java app or Cloud Key to configure an AP isn’t home lab ethos. That it looses config on reboot if you configure it by ssh is weird given you don’t need a controller running once they are setup. They can be rebooted without a controller and still work fine.
Where did you find the command line documentation? I was never able to find anything.
I’m not sure about configuring them independent of a controller as I haven’t tried.
That’s my point. With regular ap’s you can do everything via ssh. Ubiquity doesn’t seem to document the command line. The website doesn’t list any commands. It only says “only do it with a Ubquity engineer helping you”.
I bought several before knowing what I was getting into. They work well but are designed by people worshiping Apple. Everything is locked into their ecosystem. You can’t even ssl into the access point to configure it. You need to run their Java controller app to configure them or worse buy another product (cloud key) just to configure the access points you purchased. Then they try really hard to get you to setup your network admin password on their cloud servers ( they have already had security breaches where the passwords leaked).
For a small businesses that pay someone off-site to manage their network they seem fantastic. But they are the opposite of homelab ethos.
But again, they work really well. The access points do channel strength negotiation automatically every night by talking to each other.
Its simple. Now that China is in the lead, do what China did to the west. If you want access to the markets you have to build a plant in the US and share IP. That’s what the EU just proposed to China’s EV manufacturers.
It’s good for everyone. Consumers get cheap batteries, China gets Western Markets, and Western companies get Chinese technology to drive the next wave of competition.
And as I said, it could still be enabled with a boot switch.
It’s not like all distros in 1999 had PAE enabled by default. You had to find a pae enabled kernel.
And Linux PAE has been buggy off and on for 20 years:
"It worked for a while, but the problem came back in 2022. "
2 years was a long time to wait to use the extra memory that Linux could use out of the box.
For 8 years, Linux had the same limitations as Windows. Then for 2 years it was ahead. Pae could always be turned back on with a boot switch. Going back 25 years to criticize Windows is kind of weird but you do you.
(I run Linux on a variety of PCs, SBC’s, and VM’s in my house. I just get annoyed by unjustified Linux fanboyism.)
Yeah that’s why I used the qualifier “most likely”. Production companies always know details before fans, so they are better positioned to market their products early.
Your other posts didn’t reply to your claim that it is a Windows only problem. Linux did and some distros (Raspberry Pi) have the same limitations as Windows 95.
32 bit Windows XP got PAE in 2001, two years after Linux. 64 bit Windows came out in 2005.
There are two solutions.
The first is to post to the very specific relevant forums. The niche forums want your content.
The second solution for you is to do what corporations do and create many sock puppets. When a new episode of a Disney series comes out, a post is made promoting it and no one is warned for self promotion despite the post very likely coming from Disney Marketing.
I’m not sure what you are talking about. Linux got PAE in 1999. Windows XP got PAE in 2001.
I understand the complaints because I hated it when Pixel dropped the jack. But it can be a smoother process than jacks.
I get in my car and no longer fumble to pull my phone out and plug it in. Pairing is quicker than plugging in a cable.
When doing yardwork I used to have to fish my cord through my shirt or it would get caught and yanked out by a tree branch. Even then it was cumbersome because of too much slack or too little slack causing disconnects or snags.
It’s not perfect. A downside that still might exist (I bypassed the problem years ago so I don’t know if they ever fixed it.) was Google’s auto pairing that wasn’t able to be turned off. When I walked close to the house from outside, my phone would decide on its own to pair with speakers in the house. But that’s a Google problem, not Bluetooth. It didn’t exist with Nexus because you could manually control pairing.
EWaste is a problem.
Qi charger puts less strain on the battery because it can’t charge as fast. It is less efficient though.
Using it lets you protect your USB port with a plug so it lasts forever. You no longer ever have to worry that it won’t work when you need it.
qi charger? bluetooth to audio dongle to convert your headphones to wireless?
My pixel 3a had burn in after 3 years. It’s the screen gui elements that rarely change that show the burn in. On android that’s the message bar at the top and the white line task switch at the bottom.
I’ve been hearing “OLED burn in is better now” ever since I got my Galaxy Nexus 12 years ago. But it still seems to last only 3 years.