• 0 Posts
  • 150 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle
  • As it is, you only see new comments if you scroll past the post again (and your client has refreshed it) or if you open it directly. If your client hasn’t updated the comment count or if you refresh your feed and the post falls off, you’ll never see it anyway.

    A “Watch” feature would solve this better. If you watch a post, you get aggregated notifications for edits and comments on the post. If you watch a comment, you get aggregated notifications for replies to it or any of its children.

    By aggregated notifications, I mean that you’d get one notification that said “The post you watched has been edited; 5 new comments” rather than a notification for each new comment.

    Then, in addition to exposing a “Watch” action on posts and comments, clients could also enable users to automatically hide posts that are watched, either by marking them as hidden or by hiding watched posts without updates.

    If the latter approach were taken, notifications might not even be necessary - the post could just get added back into the user’s feed when changes were made. It would result in a similar experience to forums, where new activity in a topic would bump it to the front, but it would only impact the people who were watching it.

    You can kinda get that behavior by sorting your feed by Active, but this could be used with other sorting methods.






  • Unless they intercept the handshake as a proxy and have access to everything after that.

    You’re thinking of a MitM proxy, and generally speaking what you described is not a risk when using public wifi.

    There are two ways you can set up a MitM proxy:

    1. Forward all traffic back to the user unencrypted (over HTTP)
    2. Forward all traffic back to the user encrypted (with HTTPS)

    The first option will result in prominent warnings in all modern browsers. If the sites in question implemented HSTS and the user has visited them before, the browser will outright refuse to load them.

    The second option will result in even more prominent warnings that you have to go out of your way to bypass in all browsers. The only way it wouldn’t would be if one or more of the following is true:

    1. your computer has already been compromised and root certificates were installed, such that the proxy owner could use it to sign the certificates
    2. if a certificate authority was compromised, or
    3. if the site itself was compromised (e.g., if the attacker was able to acquire the SSL cert used for the site or the credentials necessary to generate a new, trusted one).


  • FOSS doesn’t mean free as in beer. Even so, you can get support for all of the things you mentioned, and more, for free. You can find the link from my comment above by searching for “Awesome Standard Notes,” but since you mentioned editors specifically, this will take you directly where you want to go: https://github.com/jonhadfield/awesome-standard-notes#editors

    Edit to add: you can enable a community created editor (other than the ones that are included in the paid subscription) by going to Preferences > Plugins > scroll all the way to the bottom > and then, in the text box under “Install Custom Plugin,” paste the url (like https://mortalhappiness.github.io/sn-tui.editor/ext.json for the Tui Markdown Editor), then click Install, review the extension info, and then click Install again. You can follow these same steps to install a different theme, too.

    There are several Markdown compatible editors in that list, so you’re free to choose the one that works best for you.

    The Append Editor supports multiple types of Markdown, including Github Flavored Markdown, as well as LATEX. You can get an inline check mark by prepending a line with - [ ], but when you press enter it doesn’t make the next line a checkmark, nor can you click a checkmark to check/uncheck it, so it’s not a good choice if checklists are your main use-case. Some better options:

    Tui Markdown Editor requires you to manually start a checklist the same way, but then a new line in either markdown or wysiwyg mode will also have a checkmark. You can also check/uncheck in wysiwyg mode with a click.

    The Rich Markdown Editor is also good for checklists. It only offers a wysiwyg experience where you type in the same view as the final one (rather than having a split view), but there’s no top menu. You can still type the normal Markdown characters with exceptions when it’s something that requires multiple characters. In that case, type / on a new line to get a list of options, then type a couple characters and choose the best option. For example, I can’t just type - [ ] and get a checklist because it escapes the characters so that I get a list that would render the [ ]. But I can type / and then type “checklist” or “todo” (really just 2 characters of either of those words) and choose that option to start an in-line checklist. And if I hit enter, the next line defaults to being another checklist item. You can also click the checkmark to check or uncheck it.

    For a dedicated task list, Scratch also works well. It’s not Markdown behind the scenes, though (but it is still readable plain text). You can start a checklist by clicking the checkmark icon in the top menu. Like the Rich Markdown Editor, a new line will create a new checklist item and you can click the checkmark to check/uncheck it.

    You also might check out the “Advanced Checklist.” It’s in the “Official Extensions” link but I just tested and was able to install it on a free account. (Note that you can also self-host the “paid” editors other than the Super editor and use them for free, though that does require a bit of extra work.)

    There are other editors on that page and also other community written editors in general out there. The Marp Editor lets you create presentation slides. The Mermaid Editor lets you create diagrams. Heck there’s even a Music Editor (for tablature, not for directly generating audio). There are a couple sketch / whiteboard apps. I’m not saying it has everything you could ever dream of, but there’s a lot and it’s easy to extend for anyone with front end web development experience.

    Regarding your point about Simplenote syncing faster: I assume this is because Standard Notes is end to end encrypted, but Simplenote is not (Unfortunately generally e2ee adds additional overhead to syncing operations as the server cannot optimize nearly as much). There may be more to it than that, though. I’ve looked at Standard Notes’s code a bit but haven’t looked at the server code for Simplenote - as far as I can tell, Simperium, the backend it uses, is not open source. (The frontend is, though.)

    That said, I’ve never noticed Standard Notes taking particularly long to sync. I don’t have thousands of notes but I do have several hundred (pretty close to a thousand). Were you seeing bad performance with Standard Notes or just worse (but still fine) performance? And if the latter, can you share some more details?

    For me, not being end to end encrypted is a dealbreaker for my private notes (unless I’m self-hosting the app, that is). I’m not comfortable with someone at the hosting company just being able to access my notes. But that’s not important to everyone, and if it’s not important to you and if Simplenote otherwise does everything you want, then by all means use it - it’s a great choice.


  • Standard Notes is fantastic, assuming that:

    • you don’t need to collaborate in real-time with your notes (you can share them after the fact and there is a way to give multiple accounts edit access to the same note, but it looked complicated and I haven’t explored it)
    • you primarily use a keyboard - mobile counts, even if you’re using speech to text or Scribble on iPad - rather than wanting a canvas to draw on.
    • you’re not trying to upload documents and annotate them

    StandardNotes has the following going for it:

    • it’s FOSS
    • it’s easily self-hostable
    • it’s also offered as SaaS, and if you use that your notes are e2ee
    • if you self-host you can still use the official mobile apps (but those are open source, too)
    • it has a web app, mobile apps, desktop apps on Windows, Mac, and Linux
    • there is a variety of editor plugins created by the community that can be used even if you use the free SaaS offering - check out https://github.com/jonhadfield/awesome-standard-notes for a list.

    I’ve been using StandardNotes for a few years at this point (as a paid user on their 5 year plan, which no longer exists as far as I know) and have also developed an editor plugin for it.


  • I picked up an Onyx Boox recently (specifically the Note Air 3C, which is a color e-ink tablet rather than just e-reader) and since it has the Google Play Store, I was able to just install the Kindle app. The Boox Page ($250) and Boox Poke5 ($170) make up their traditional sized e-reader lineup, and both appear to support the same thing. You could also install the Kobo Books app and make future purchases there, as well as library apps like Libby and Hoopla.




  • It is sexist to treat men and women differently without a good reason, and it doesn’t seem that there’s a good reason in this case, which means that doing so is sexist.

    Regardless of morals, from a biological perspective, treating male and female nipples differently is irrational, since male chests are also physical sexual characteristics. To be clear, I’m differentiating from the perspective of “these two body parts are shaped differently and therefore have different needs when fashioning clothing” perspective. There’s a good reason to do that (though there isn’t a good reason to enforce it). But from a “one is sexual, one is not, so one needs to be covered and the other doesn’t” perspective, what’s the reason? You indicated that they’re physical sexual characteristics but as I already pointed out, physical sexual characteristics aren’t generally required to be covered. People find both men’s and women’s chests (and other body parts) sexually attractive, so that isn’t it, either.

    If you’d say that society treats them differently because we’ve historically objectified and sexualized women (and continue to do so) and as a result women’s bodies are considered sexual in a way that men’s aren’t, and this is ingrained in our culture at this point then I would agree with you. I just don’t agree that that’s a “good reason.”





  • If you can tell the difference between well-compressed, high bitrate audio and lossless audio played on the same equipment, then you’re in the minority. However it’s pretty easy to accidentally end up with a combo of phone / app / app settings / headphones that results in a suboptimal listening experience, either because you’re using a bad codec (like SBC on any device or AAC on many Android phones) or because your music is being compressed twice. You can avoid the latter issue by streaming uncompressed music or by using a combo that doesn’t recompress your music (like Apple Music -> iPhone -> Airpods Pro/Max).

    It’s also possible that the reason Bluetooth headphones sound worse isn’t because of losing information but because the headphones just aren’t as good as your wired ones. If you get a portable Bluetooth DAC like the Qudelix 5k, you can connect it to your phone and connect your wired headphones to it.

    You don’t have to be happy with Bluetooth. You can buy a USB-C DAC for like $10. Apple’s “USB C to 3.5mm Headphone Jack Adapter” is 9 USD direct from Apple and it tested extremely well. You can use it on any modern phone or on your laptop or tablet, too. (You can also use the Qudelix 5k this way.)

    If that adapter isn’t good enough (maybe it doesn’t output enough power for your high impedance headphones), then most phone’s built-in DACs + headphone adapters would have the same problem. Basically only Sony and LG (RIP) phones ever had especially good onboard DACs and amps, and even with them it would often make more sense to get a dedicated portable setup.

    For anyone who is happy with Bluetooth, though, they don’t have to worry about all this and they get to reap the advantages of the headphone jack’s removal. The extra space can be used for more battery, if nothing else, and it’s easier to prevent dust/water ingress when you eliminate the headphone jack.

    Also, I think you’re thinking of LDAC (by Sony), not aptX (by Qualcomm). LDAC is not lossless, either, but it’s much higher bitrate than anything other than the very recently introduced aptX Lossless, which - under ideal conditions - features lossless compression.


  • In store, it’s hard to tell the difference. They run in a ”Store” / “Retail” mode that amps up the brightness and color saturation to a level that’s often unsustainable (it will damage the TV if you use it in this mode) and that doesn’t translate well to actual content because it’s too vivid.

    If you’re interested in understanding more about modern TV technology / which TVs are best, I recommend checking out Rtings and HDTVTest (there’s a site, a channel on Youtube, a subreddit, etc). The former because the reviews are great; the latter because Vincent explains these things well. He talks about specific technologies like types of OLED panels, different LED technologies, different settings on TVs and what they mean, calibration, etc…

    To answer your question, though: the more expensive technologies are what cost the most, and bigger versions (starting at 55”) also tend to cost more. Right now the best TVs you can buy are OLEDs - specifically, QD-OLEDs like the Sony A95L. A 55” is like $2500. By comparison, a traditional OLED (or “WOLED”) like the LG C3 is half the price - a 55” is $1300 - and nearly as good. (And a previous gen model, like the C2, will be even cheaper, if you can find one.)



  • If ads are inserted at random time stamps and the client reports the watched intervals, then the server doesn’t need to communicate which intervals are ads.

    That could still be bypassed by building a library of ads in the ad blocker, then examining the video feed when an ad is encountered, looking it up in the DB, and automatically jumping ahead as many seconds as its expected duration, but that would be a substantially heavier operation than what uBlock Origin currently does.

    It also wouldn’t enable forcing users to watch the ads, since the client wouldn’t know to enforce an unskippable segment from 1:38 to 2:08. And that’s probably the real reason it won’t be implemented - an executive probably has “must preserve these features” as a constraint, so an engineer wouldn’t even propose this feature to them.