Y u no Mamaleek

  • 0 Posts
  • 438 Comments
Joined 4 months ago
cake
Cake day: November 3rd, 2025

help-circle







  • FrontPage was initially created by Cambridge, Massachusetts company Vermeer Technologies, Incorporated, evidence of which can be easily spotted in file names and directories prefixed _vti_ in web sites created using FrontPage. Vermeer was acquired by Microsoft in January 1996 specifically so that Microsoft could add FrontPage to its product line-up, allowing them to gain an advantage in the browser wars, as FrontPage was designed to create web pages for their own browser, Internet Explorer.





  • By the way, @[email protected], I brought up user stories in particular because they should be initially written or at least verbalized by either the target users or clients like managers. Neither designers nor programmers can know exactly what the target user’s needs are, or they may think they know but be mistaken — because they don’t have what’s called the domain knowledge, i.e. expertise of the target users.

    Of course, another major tool in a designer’s workflow is testing with target users before release, including with rough mockups — so any misunderstanding of users’ goals and workflow can be caught in time.

    For the context, I’m a dev who mostly does backend. But understanding design is interesting and helpful.



  • I mean, I wrote bash scripts for this on Mac, and Automate workflows on the phone. The scripts are pretty short and simple. The custom touchbar buttons were added with MTMR.

    In Windows, I can’t connect/disconnect Bluetooth devices via PowerShell without a UAC dialog appearing (or whatever dialogs those are). And the free third-party option for control of devices from the command-line is a binary from a site last updated ten years ago or so.

    In Linux, I’m perpetually mourning the absence of an app like Hammerspoon, that is scriptable with Lua (or a similar language), has tons of APIs for desktop automation, and a built-in http server for requests from the phone. Proprietary Unified Remote might be the closest thing, but its workflow is different.



  • The matter of wonder is that I never needed this ‘auth’ thing or the ‘trust’ thing in Windows, Mac, or Android, and never had recurring disconnection problems, before this experience. I just paired a device and then clicked ‘connect’ or ‘disconnect’ and went about my business. In fact, I was baffled by how people seem to always have some issues, devices connecting randomly, etc.

    Even Bluetooth range seems to have dropped compared to other platforms. My phone can reach the headphones over a large apartment, while laptop loses them if I walk behind a wall.


  • I’m guessing that the design documents might’ve been something in the vein of ‘user stories’ (if I correctly recall their name), which describe what some typical users would want to do with the app, so that the actual UI design would focus on these features being available front and center. This is a very legitimate design technique, and a good designer should always question why any elements must be present in the UI and whether they solve the user’s goals.

    This Blueman thing would definitely benefit from such approach, because right now it exposes a lot of technical details about which I don’t care, while simultaneously making my everyday operations with it inconvenient.


  • This bastard of an app manages to expose too much of the underlying processes and logic, of which I don’t care, in the utterly uninformative format. The OP forgot to mention that upon first pairing my headphones, I have to fend off three different notifications about ‘auth requests’, that provide me with no explanation what happens if I do or don’t satisfy said requests. These also reappear after the headphones disconnect for some inexplicable reason, until I give up on learning further details and click ‘always auth’. Which seems to help with the disconnections. Apparently some audio profiles are also occasionally unavailable unless I appease the blue fucker with ‘always auth’.

    Sometimes the headphones fail to connect, and all I get is some cryptic error message, with the only understandable word being ‘timeout’.

    The tray menu has a shitload of items which I never need, and then always lists devices to which I can reconnect, even when they’re already connected and have separate (and dynamic) menu items to disconnect from them. Plus each device is listed like they have titles of nobility, something like ‘audio and input profiles on HeadphonesModel’.