ggppjj

joined 1 year ago
[–] [email protected] 1 points 1 day ago

Sorry, this comment was mainly just providing the previous user with a correction because they seemed to think that the other person that they were replying to was talking about forcing people to use phone apps, which I assume we all agree is bad and would likely work if there were a concentrated push for it.

Concerning your points after "using the browser": I want websites to use replaceState and manage their own intra-page navigation with a cookie. They can still intercept the back button as they do now, but they should only get the single history entry until they switch to a new page, if they ever do.

[–] [email protected] 1 points 1 day ago

I don't think I'm disputing your facts, I was responding to the scenario you presented which was, essentially, "what about email". I would say it's fair that my opinion on a canonical browser history is solid and unlikely to change, though.

[–] [email protected] 1 points 1 day ago (2 children)

I think the word 'app' was being used in place of 'webapp' there, which is the general target audience for this feature.

[–] [email protected] 1 points 1 day ago (2 children)

I don't think that email and browser history are similar enough to make a meaningful comparison, honestly.

Maybe someone could say that, but I am not.

I see a specific instance of a specific bad feature being specifically abused. I don't care to entertain whatabouts.

[–] [email protected] 1 points 1 day ago (4 children)

I accept that it's how things are, I just personally feel as though the only way this feature could ever work as it does now is with the implementation it has now, and that the convenience of single page webapps that use history manipulation is not worth the insane annoyance of helping my grandma get out of websites that tell her that she has been hacked by the FBI.

[–] [email protected] 3 points 2 days ago (6 children)

I'm frustrated that removing bad functionality is being treated as a slippery slope with obviously bad and impossible jokes as the examples chosen.

I see a bad feature being abused, and I don't see the removal of that bad feature as a dangerous path to getting rid of email. I don't ascribe the same weight that you seem to towards precedent in this matter.

[–] [email protected] 2 points 5 days ago

I'd prefer an independently owned small store, as someone who installs cash register systems for independently owned stores primarily in rural West Virginia.

[–] [email protected] 7 points 5 days ago (1 children)

You appear to have accidentally responded to a different thread of comments. I mean this genuinely and not sarcastically.

[–] [email protected] 3 points 6 days ago

... With all currants in it? Just like mother used to forge.

[–] [email protected] 17 points 6 days ago

It's the Handset Protocol/Handsfree Protocol that was developed for simultaneous sending and receiving of voice data. They're the only protocols that support sending and receiving voice at the same time, and they do that by sending mono telephone quality audio and receiving mono telephone quality audio.

It's why most gaming headsets, even ones with Bluetooth, include a small RF dongle separately. Bluetooth is technically incapable of high-quality audio when recording.

[–] [email protected] 1 points 6 days ago (1 children)

Nothing better than selling a single-purpose bit of plastic intended to go into the microwave and boil water that is functionally a replacement for a bowl that you presumably already have that expressly states that you can only use it for up to 5 years.

[–] [email protected] 3 points 6 days ago* (last edited 6 days ago) (1 children)

Well, the Starlink could be connected by an admin to a computer that is connected to SIPRNet, right? It exposes itself as just a router.

I mean, assuming the Starlink was brought on board by someone with authorization to be on board, any possible adversarial situation would necessarily be an internal issue to begin with.

Personally, I think the most likely answer involves an Xbox.

view more: next ›