![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/2QNz7bkA1V.png)
The entire Material Design framework in JS and Web Components in 80kb
https://clshortfuse.github.io/materialdesignweb/components/buttons.html
JS and Web Components are not the problem. Poor design is.
The entire Material Design framework in JS and Web Components in 80kb
https://clshortfuse.github.io/materialdesignweb/components/buttons.html
JS and Web Components are not the problem. Poor design is.
Years (decades) ago it wasn’t uncommon to create self-signed/local CAs for active directory, but it’s really uncommon today since everything is internet facing and we have things like Let’s Encrypt.
It’s so old, the “What’s New” article from Microsoft references Windows Server 2012 which is around when I stopped working on Windows Server. I kinda remember it, and you needing to add the server’s cert to your trusted roots. (I don’t know about Linux, but the concept is the same, I’m sure. I never tried generating certificates, but know all the other client -side stuff. Basically you need a way to fulfill CSRs.)
https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/
What you’d want to do it in Windows is all there, and Microsoft made that pretty easy back then to integrate with all their platforms and services, but I’d caution, do you really want to implement 10+ year old tech?
I don’t know why you’re bringing up Palisade. The OP clearly says Telluride and the text mentions Kia. I have the same car, 2020.
You either have remote start over Kia Connect or key fob. It’s either, not both.
And a Reddit comment goes further:
No 2020 Tellurides in North America had remote start on the key fob from the factory.
https://www.reddit.com/r/KiaTelluride/comments/14737v9/telluride_remote_start/
See also: https://www.kiatelluride.org/threads/2020-telluride-remote-start.1825/ (outside of US has fob)
You can’t remote start with the key (at least on the 2020). It’s remote cellular start that runs on a ~40 second interval or nothing (or third party).
I have a Telluride. I’ve been downgraded to Lite which gives you notifications if you forget to lock your car. But remote start is no longer available.
The way it worked seems to be polling since you could wait around up to a minute for the car to perform a command.
The worst part is the car does not have “local” remote start. I’d have to buy another piece of equipment for that and install it. It’s not available at all on the key fob.
Did well with Brother laser printer. Canon was okay.
I had setup a friend’s HP printer and noticed he was constantly switching to WiFi Direct in order to print. I did him the favor of connecting it to the AP, so he wouldn’t have to manually switch all the time.
The moment it got online, the printer locked itself down and refused to continue print until he paid for a subscription service on the ink.
We don’t like when people add color to our monochromatic text.
According to Route Note, which appears to offer a middle-man service for artists, their ranking, as of November 2023, is:
Should be a hyphen instead of period before NAHOM.
And yet…
Double NAT with DMZ.
Those SIP ALGs are more trouble than they are worth. If you are using SIP devices, use a different outbound port on each device (eg: 5060, 5061, 5062).
As a PocketPC (WinMo) user before the iPhone even existed, I take offense to the claim.
They pioneered capacitive touchscreen for ease of use, but I had ditched dumb phones years before iPhone.
Note XDA refers to the old Windows Mobile XDA phone and then became an Android community. I was there for that transition and none of us were very impressed with the iPhone, but understood that it would be something for the tech illiterate would eat up.
When Android came out, we went from Custom Roms for WinMo to Custom ROMs for Android.
KAKATTE KOI!
(EVEN LOUDER GAMECUBE CONTROLLER NOISES)
Are PWAs “only” websites that are shown as an app or do they have features that would distinct them from “normal websites”?
In theory, they’re the same. In practice, user agents (read: browsers) can dictate extra, uh, privileges to PWAs. For example, Safari Mobile won’t allow push notifications for just websites. As a dev, we don’t control this aspect. We just code "isPushAllowed()` and continue from there. As a marketer or apps/software I learn what browsers and environments allow what, so I know they need to install as a PWA to get access to some APIs.
Can PWAs reserve disk space for offline downloads for example (Spotify has got a PWA but that one is mainly their website shown as an app).
Branching off the other point, it’s up to the user agents. For example, Safari Mobile will delete storage for websites after a certain time (I think 6 months). But PWAs have unlimited lifespan (a misconception years ago). It’s not what you asked (storage size vs lifespan), but it gives you a clue to how browsers manage this. I personally haven’t experienced much issue with storage, but I do know there’s even a File API which gives access to your actual drive. I would imagine if browsers are allowing us to access “unlimited” storage over the file system, the restrictions for the Local Storage aren’t that important.
A short search brought me here which mentions 80% of total disc space for Chrome, 50% for Firefox, and 1GB for Safari. Nothing here talks about PWAs, but I’d imagine Safari is the only one worth concern. I can research more if you want, but it’s not in my use case to concern myself with local storage.
Edit:
And I probably can’t install a listener via PWA like Discord does for their Rich Presence, can I?
As long as there’s an API, for better or for worse, we can do it in PWA. From what I read, there doesn’t seem like anything like this in the Web API. Background tasks are currently somewhat restricted in the interest of battery conservation of mobile devices. From a theoretically point, an app running in the same environment as the PWA could have somethig shared between them. There are API in addition to Web APIs, like extensions, but there’s probably a lack of normalization for detecting what is running on the device.
The idea of making everything in the Chrome Addon/Extension API in to real API is part of Product Fugu and from looking Chrome never built anything to expose what native system processes are being run with a web site. It’s honestly such a specific (and invasive) prospect I doubt it’ll ever happens. The closest is chrome.tabs
but there’s no web equivalent.
Sharing of other PWAs running probably won’t happen because sandbox/isolation is pretty core to Web right now. Cross-app data sharing is something I don’t know about yet, but maybe if PWAs mature we’ll see that. Then games and media players can “broadcast” to other PWAs data like presence. I’d imagine that branch from the Web Share API.
I’ll take this opportunity to state my bias. I believe in the Web standards, meaning it shouldn’t matter what browser or environment you use. They should all be the same. I want this for myself and express this to my clients.
But because standards are “living” it’s always a moving target. What is supported today by your preferred setup may not take full advantage of what a Web App provides. But the idea is, after a while, you will gain those features later in your setup as browsers get better.
This is something I’ve seen in practice since I wrote a lot in PWA and told my clients that eventually it’ll be in Safari, but I’m not going to write a native app for outdated browsers. And the investment paid off. Before, Safari users didn’t have Wakelock, Push, or good WebRTC experience, but today they’re mostly indistinguishable from Chrome Android. I didn’t have to change a single line of code to make that happen.
About 8 years ago now I ditched .NET, Java (Android), and Objective-C (iOS) to JS in frontend and backend with NodeJS and PWAs and couldn’t be happier for a dev perspective.
All frontend is just one code. Sure, you have to manage browsers compatibility, but it’s not a major issue. Mobile users and desktop use the same application. I didn’t know Firefox dropped PWA on Desktop, though most of my desktop users were using Edge or Chrome. I can only think of one client that used Firefox and it worked fine, except for Firefox has some out of spec EventSource
bugs. Safari has gotten better (especially after 16.4) now where I would Firefox as the leading source of browser issues when developing. Also, Safari 17 looks to finally treat PWAs with some legitimacy. We even have Push notifications now!
I don’t understand Firefox’s decision, but Firefox on Android still supports PWAs on Android. But if they no longer care about desktop PWAs then I’ll give Firefox less importance for desktop environments. Probably doesn’t mean much in testing, but that means if I find a Firefox exclusive bug related to desktop (eg: mouse), I might just ignore it.
I would highly recommend PWA over Electron. There’s nothing better than getting clients to transition to your software from a competitor with just a simple PWA with no install. I also support as far back as Chrome 88, which means any EOL ChromeOS device is still supported.
You might need newer APIs depending on usage, but I haven’t found anything that I need to tap into some sort of native runtime for core usage. Maybe WebRTC runs better on newer Chrome, but nothing really requires native code. It’s just easier to maintain one single codebase without locking out potential clients because of OS (desktop or mobile).
Or having a few screws loose / not all there.
The Material Design 3 guidelines expresses how content should flow with foldable with slight differences compared to a tablet, for example:
https://m3.material.io/foundations/layout/canonical-layouts/list-detail
But you can mostly get away with a standard, two-pane layout as you would a tablet, though the center padding may be off.
You probably want the center 24dp spacer to be where the crease is, but it gets a bit complicated if you want to use a Nav Rail since it’ll offset your layout by 80dp. Here is a web based demo of what the configurations can look like.
Touchstream met with Google in December 2011 but was told that the tech giant wasn’t interested in partnering with it in February 2012. For reference, the first generation Google Chromecast was released in 2013.
Not really patent trolling when you meet with the company, they say no, and then they launch their own version.
The Who were kinda silly (eg: Boris the Spider) in their early years.