I wouldn't say that the changes to album structure in response to technology changes is "concerning". Art changes as a society changes since art is a representation of the human condition (and the representation is usually made by people trying to represent their current condition). If the majority of music existed solely to get money, that's what would be concerning but I'd argue that's not the case presently.
The legal definition prohibiting encryption is in §97.113(4) and says that "messages encoded for the purpose of obscuring their meaning" are prohibited. This is generally accepted to be a blanket prohibition of "encryption" in the sense that SSH, SSL, TLS, VPN type traffic would be prohibited.
However, there are some interesting and positive nuances because the rule specifically doesn't ban "crypto". For instance, it is my belief that cryptography for the purpose of authentication or message signing/integrity checking is completely permissable. That is to say that you can even technologically allow things like TLS and HTTPS so long as you force a NULL cipher; so you get message integrity but no encryption so some observer could see all the traffic but not be able to interfere.
More broadly, the purpose of the ham radio allocation is learning / experimentation / personal use between hams / etc., not production services (and not even personal use between a ham and a non-ham, e.g., while listening in on ham frequencies doesn't require a license, a ham intentionally broadcasting to those listeners is not authorized under their license). These rules predate the world in which encryption for everything is commonplace, and they envision a world in which encryption means that other people can't learn from your communications practice. These rules are also written to discourage actual commercial users from using the ham frequencies, to keep the frequencies clear for hams.
Now that we live in a world where my writing this message to you (and, in fact, to the world, publicly under my name) goes over an encrypted channel and it would be unthinkable if it didn't, and where my texts to my friends about where to get dinner happen over an end-to-end secure messenger, and where most competent cryptography is developed in public, it's not clear the rules make sense any more. But that's where they come from.
BTW, one ham has argued that encryption for the purpose of using a standard protocol like WPA/802.1x (or, probably, SSH or SSL) that is otherwise compliant with the intent of the amateur service is legal, because the purpose of the encryption is not obscuring their meaning, the obscured meaning just a side effect of other goals: http://www.n5dux.com/ham/files/pdf/Data%20Encryption%20is%20...
Sometimes I wish a large company, like Google, bought large spectrum and released it to the public. We fight over Mhz here and there, but tons of the spectrum is allocated but barely used.
Speaking as an amateur radio operator who does experimental stations....
Encryption is illegal as you stated. However "Unique encodings of an analog or digital nature" are completely legal. You don't even need to tell the protocol.
We had this issue with D.star where it was an amateur radio digital protocol in which they didn't tell how to encode or decode. Brought up at an FCC hearing and deemed completely legal.
So call all encryption a "Unique encoding" and you're legally in the clear.
We had this issue with D.star where it was an amateur radio digital protocol in which they didn't tell how to encode or decode. Brought up at an FCC hearing and deemed completely legal.
This can't be right. IIRC you have to publish in a public place how your code works, and I believe the D-STAR specs are public; its just that any implementation is blocked because of copyright or whatever dumb crap.
This part of the regs have nothing to do with encryption. This is the so called "documented protocol" requirement. §97.113(4) is the relevant main rule that would govern encryption. There are various exceptions to this through the rest of the document such as spread spectrum, space stations, and telemetry/radio control all having some special case language.
Well, I stand corrected. I had admittedly just googled it myself. I had known the ban on encryption was pretty accepted in the amateur radio community. Thanks for the correction.
> With this update, Firefox is introducing scroll anchoring, which ensures that you’re not going to bounce around on the page as these slow-loading ads load.
While I love the idea of videos not automatically playing, I'm almost more excited for the scroll anchoring feature.
This happens to me every single day on the Windows 10 start menu and on my iPhone using the swipe-down search on the Home screen.
Why in God's green Earth the developers who implemented these don't cache obvious local results (like app names) to quickly return them is beyond me, and why the position of the results has to move after the fact is even more maddening
I typed "Arro" for an app I use last night, it took a moment to show up and when I went to click it, the web results populated so I accidentally clicked on "arroz con gandules". Sounds lovely, but I am certainly not expecting that to be the autocomplete...
Had the same problem on my iPhone. I turned off Siri for app search (Settings / Siri & Search / Suggestions for Search) and now the results are instant. (And local to my phone, so no internet-sourced results, but I’m fine with that.)
How Microsoft managed to ruin the Start Menu, on the other hand, is amazing. I had to reinstall a computer because some Cortana corruption had made it impossible to launch apps from the Start Menu’s search results. Even though I disabled Cortana. Incredible.
How Microsoft managed to ruin the Start Menu, on the other hand, is amazing.
My Windows 10 start menu lags. Press windows key or click on it, no response for a good ten seconds or more.
I have this on my work machine, a previous install, my home machine, a Surface Book, a remote desktop server on Windows 2016.
And yet, I've never seen anyone else talking about it. I can't believe I'm the only one who has this "my start menu has paged out to 5400rpm disk, then powered the disk down" experience.
Same here. Sometimes I’ll click on it a good five or eight times before it comes up. When people say Windows 10 is good, I feel like they’re living in an alternate dimension.
I think you guys are the exceptions to the norm here, and not the norm.
I have too many computers at home, some verrry slow ones, and they all pop up the start menu within a second or two unless I've just booted the PC.
I work with a lot of people who use Windows 10 all day long, and I've never heard one of them ever complain about a slow start menu. Complaints about search results? Absolutely.
I suspect it's something you're installing, and I'm sure you'll deny that (and you very well could be right, I don't know) and these things are time consuming to diagnose, unfortunately.
Any sufficiently popular OS is probably going to suck for ~tens of thousands of users while at least hundreds of thousands more wonder what the fuss is about.
Thank you for the Siri protip, that was one of my biggest frustrations with iOS (that + inability to take scrolling screenshots natively, similarly to how you can on Samsung Galaxy phones). For complete peace, I just wish there was a way to turn off all app suggestions in search at once, instead of flipping that switch in settings for every single app.
Every time I click the share button in Android, the icons are in completely different order. Not last recently used, not alphabetically. Completely random.
Your not accepting the 1st suggestion (Arrow) when you typed "Ar" decreased the probability that that was the term you intended. The next suggestion factored in that you were probably looking for something else and bumped up other suggestions.
That’s a bad assumption. People often type faster than they can respond to changes on screen. Typing speed & muscle memory means I’m more likely to type “arr” than just “ar”. But I’m also likely to be thrown off by the search reshuffling as it expands.
Once an item matches the search, it should stay in place unless it’s invalidated by further typing. Reshuffling just adds needless friction.
This actually made me laugh with how tone-deaf it appears to be about how users normally interact with a search field. Is this response based on industry "knowledge"? How did this sort of thinking come about?
That would be such a stupid way to implement a search.
When you search you don't type letter by letter and inspect the suggestions after each keystroke. You type many letters and only then you inspect the suggestions/results.
The iPhone search has been driving me crazy as well. Another one that always gets me is pressing a number in the recent calls list just after another call was ended.
You're absolutely right. The recent calls issue happens way too often. Nothing worse than calling your boss at 2am when you meant to call your wife or vice-versa...
I often put the phone in my pocket after a call without pressing the sleep button, so the screen stays active, causing me to unknowingly "butt dial" random numbers, sometimes talking to other people while a confused/mischievous person on the call is listening in...
On iOS I randomly get this weird lag when I swipe down and start typing an app name. Sometimes it shows LOCAL apps and sometimes it... doesn't. For a while. WHY, Apple, WHY? You used to "JUST WORK"
On Android, whenever I want to copy something I have to wait a few seconds for the menu to fully load. Otherwise I end up tapping on the wrong icon. Quite irritating.
This is a good argument for empty place holders when loading dynamic content. Although some people don't like them, it is an easy way to prevent UX issues like this.
I disagree. I think having some clicks ignored would be pretty annoying. The solution is to design your UI so that what people want to click on isn't jumping around.
Oh my god. Sad thing is that I'm almost sure that mist have happened somewhere. Not that they came to the "jumpy layout is good" conclusion, but that maybe an accidentally slower version of the page lead to that result and they ended up with "hey this version makes users want to click ads more"!
Or all of the sites that have adopted a 'card' view. Gannett sites all have this terrible UX that if you click in the white space around an article, it closes the article and takes you to the home page. [0] Accidental clicks on white space shouldn't do anything!
Accidental clicks on white space shouldn't do anything!
They are racking up click-throughs.
Advertisers pay just as much for accidental clicks as intentional ones, so the site operator is incentivized to generate as many as possible. Being the dumbest morons ever to mo a ron, the advertisers don't understand that they're the marks in this particular con game.
Eventually they will get tired of paying for worthless clicks, but I wouldn't hold my breath.
this has been happening to me recently on Google search, as cards load with info about the top results.
Anyone on Google reading this -- please either cut that out, or include css placeholders for content you expect your JS to load.
Both waiting longer for content to load and having to go back from clicking the wrong thing detract from the raison d'etre of fast and relevant search.
I was hoping to find someone else who mentioned this.
This catches me out regularly. I would not be surprised if a team at Google implemented this and immediately saw “increased engagement” from users in an AB test, so they locked it in permanently and considered it case closed, the science is in.
I'm constantly annoyed by that horrible feature too. It usually doesn't cause a misclick anymore, but it's really annoying that every time I go back to look a the next search result, the result moves once I've moved my cursor to the result I want to click.
Is there any use in removing these automatically-generated tags? They seem like something that might change the second Google's deployment pipeline pushes a new build (or even sooner).
Using the NYT iPhone app on the subway is maddening. Every time you go in and out of cell coverage the whole app pauses while it waits to load ads that will never come. It is so frustrating that I am close to giving up on it entirely.
Newegg has been particularly bad with this in the past. Looks like they have fixed it now, but used to be that it would take a 0.5-2 seconds for their advertisement to load above the "search within", "only show newegg products, I'm not looking for an amazon experience", and "sort by" fields. Go to click on those (I always prefer "only newegg" instead of the default "all sellers"), and half the time I'd end up clicking on the advertisement when it loaded.
Makes me wish there was some sort of an understanding that: The thing I just clicked was somewhere else within the last 400ms, so click on what used to be there."
I don't think it's likely to have been "planned" deliberately, as the result is an annoyed user. I think it's the result of naive A/B testing, without examining the deeper reasons for the results. "Oh wow, clicks are up 50% with the new layout!"
Of course, if you did discover the true reason for the increase in your click rates, you'd probably stay quiet about it. So maybe it's a bit of both.
That site that you're about to reload because it isn't doing anything? Suddenly loads just as your finger is depressing the mouse button to reload. That JavaScript heavy site that has brought your pc to its knees? Works just as you've elected to kill the process.
> That site that you're about to reload because it isn't doing anything? Suddenly loads just as your finger is depressing the mouse button to reload.
I dont think thats coincidence. More likely, the browser already has downloaded the page itself but is waiting for some resource before rendering it. If you reload, it renders what it has immediately.
How does it know my finger is swiftly moving towards the "R" part of ctl-shift-R? :-) I swear that I sometimes see it render right as my finger is getting ready to contact R.
> I'm almost more excited for the scroll anchoring feature.
If we could get this feature on mobile and desktop operating systems, I would be soo happy. I probably click/tap on something just before it moves about fifty times a day. Having the fastest devices only helps a little.
A similar annoyance: the browser insisting on switching focus once the page loads.
It happens nearly daily that I'll be typing in to an input field while the page is still loading, and Firefox will switch focus away from that input field when the page finishes loading.
The consequences of this are even worse for me, as I use the Tridactyl extension, which acts on vim-keystrokes when the focus is not in an input field. So if I'm in the middle of typing something in an input field and Firefox in its infinite wisdom chooses to switch focus out of the input field, what I type from then on will be acted on as commands to Tridactyl, which could do things like open, close, or reload a page.
That's actually the reason I stopped using VIM bindings in FF. The small amount of niceness from VIM bindings did not make up for the random annoyances.
Have you tried `set allowautofocus false`? It breaks some fancy editors like CodeMirror but you can always re-enable it on certain pages with `seturl`.
It appears to already be in Chrome. I have a site that I hate because their slider at the top always scrolls the site around, but that has recently stopped, and I've noticed that the page knows where I've scrolled to and adjust the scroll when the page changes above where I'm reading.
I switched back to Firefox about six months ago, and this issue was the only thing that ever made me consider switching back to Chrome; there's one forum I frequent where the "latest unread post" button was basically useless because of this.
Excellent news! Next step: TWitter and Facebook streams do not reorganize themselves by an algorithm on a Back button. You can click Back and comment the post that gave you the linked article in the first place.
Sad this is even necessary. Progressive loading is a relic of a bygone 28.8 kbps era. Connections are fast enough is where you should be able to draw everything into an off-screen buffer and display the completed page in one go.
People on lower quality connections (high packet loss/roundtrip) eat a lot of delay on page loads because the average site connects to like 20+ servers and the browser has to spin up a bunch of http connections. Then you have to wait for javascript to load... this is unavoidable.
Came here to say exactly this. Additionally, although someone who doesn't speak the same language as you (e.g. English) can potentially read your code and understand what it's supposed to do, I've never seen code used as purely a communication medium making me think that spoken/written languages are more complex and varied than programming languages.
From the standpoint of a designer, this will likely simplify asset development pipelines since the new spec appears to be much closer to the iOS guidelines.
> Yes they have issues (as does literally every brand/company)...
Just wanna draw attention again to the above quote from the comment at the top of this chain. Tesla's very public and always in the news. Of course we know about all the things you mentioned in your comment. That doesn't mean Tesla is a failure or needs to be razed to the ground. Work in any company big enough or that's in the public spotlight too long and you'll find exactly these kinds of issues running rampant. I'm not excusing the issues (they definitely need to be looked at and either fixed or learned from), but I do think it's important to look at the big picture instead of getting caught up in the weeds of relatively minor but overly publicized failures.
Out of genuine curiosity, do you have a list of good alternatives or some reading material on "paging" best practices? My team uses PagerDuty but I've never really questioned if there's a better method out there because the system PagerDuty replaced for us was so terrible that PagerDuty seemed like a godsend.
You guys are out here giving very strong dismissals of a very good service, and then referring us to a resource you wont even bother to link? Maybe you can link the actual resources to prove your argument instead of assuming you are correct and dismissing people to figure it out on their own. Usually, the standard for conversations here is held to a higher, non-twitter level, and I for one enjoy conversations held to higher standards.
While I understand your point, I would gently argue that to develop a truly great macOS or iOS app, you somewhat need to live in the Apple ecosystem to understand the design guidelines and quality that Apple customers have come to expect.
I bet the most downloaded apps these days are ground up cross platform and identical on every platform, e.g. steam, spotify, and web browsers. Relying on proprietary apple features that you have to clumsily port over to another OS would waste a lot of your time as a dev. You'd probably do your best troubleshooting on a cheap, under powered hackintosh than a model year macbook pro, to be honest.
Fair point. I tend to not like those cross-platform apps because of their generally-degraded performance so my previous comment showed a bit of my underlying bias.
Yes. But parent didn't contest that.
They rather made the point that you have to pay to "live" in that ecosystem. MacOS is officially only supported on Apple hardware ...
So it's not free and the fact that XCode is is therefore a moot point to that line of reasoning.
