• 1 Post
  • 24 Comments
Joined 3 years ago
cake
Cake day: January 8th, 2024

help-circle


  • I think noster deserves to be part of this conversation too. Instead of users creating an account on a server that can remove them if it wants to, they create a public and private key pair and publish their notes to several servers, all of whom have a copy of it and can distribute it further.

    This adds redundancy because if one relay decides not to host your content anymore or goes offline, your content is still on like four or five other relays accessible to other people. And if for some reason every relay on planet Earth banned you, you could always run your own very easily.

    Spam mitigation measures exist in the form of some relays requiring a proof of work that calculates the hash of the content with a certain number of leading zeros to prove that you spent energy to create that hash. There are also a few paid relays where you submit your public key to the relay and pay a small fee, and then that relay will host your content when you publish to it.







  • I think this is really good. I personally am not against the use of AI, especially the open-weight or open-source models, preferably, when there’s a human directing the AI and checking what it does to make sure that it’s actually sane, because if a human makes a mistake at 3am, the AI can catch it, and if the AI makes a stupid mistake, there’s a human around to catch it.

    Just as an example, I asked one of the AI models to run a security audit on the Monero Wallet app I like to use on Android, and within about 30 seconds, it pointed out a critical vulnerability that had been unaddressed, and I confirmed manually that it actually existed and that it wasn’t being hallucinated, and when I did find out that it was actually true I told the developer in private about it, and it has now been fixed.


  • The other thing is that on Android, only one app needs to remain open at all times in order to receive push notifications. In default, Google Android, that would be Google Play Services. But on open source systems, that can be some sort of unified push thing like NTFY.

    That way you’re not keeping like 10 applications open checking for their own notifications over and over again. You’re only keeping one application open and when that receives a notification for whatever app, that app gets triggered to wake up and check for it.

    Another thing is that Android uses something they call Doze Mode, where, if your phone is locked and is not in motion at all, as detected by the accelerometer, it will progressively get longer and longer between checks for new content in order to save the battery.

    It uses the accelerometer because, for example, if you put your phone on your bed when you go to sleep, your movements during the night will still trigger some slight motion in the accelerometer, which would keep the device more active than it otherwise would be.









  • I have touched the fingerprint reader on accident with the incorrect finger when picking the device up or something because it’s on the side with the power button, but I have never had an issue where I’ve meant to unlock my device with the correct finger and used the wrong finger instead.

    I have used the wrong finger on purpose in order to press the power button in order to bring up my lock screen without actually unlocking the phone to see the time or whatever, though so perhaps a 3 strikes your out rule would be best where if you hit the fingerprint reader with the wrong finger 3 times in a row it would then wipe

    Let’s say my pointer finger is the registered finger for the reader. If I want to unlock my phone, I’ll just touch the fingerprint reader with my pointer finger and the phone is unlocked. If I wanted to say interact with a running media file, or check the time, I would deliberately press the power button with my middle finger, that way it registers it as a press to bring up the lock screen, but does not unlock the phone. And then, when I want into the phone next time, I would touch the fingerprint reader with my pointer finger to unlock it. If I am picking my phone up off of a table, for example, and my ring finger just happens to touch the fingerprint reader, it’s obviously not going to recognize, and then once I get the phone in my hand properly, I would use my pointer finger to unlock it.

    This is why I think perhaps a three-time rule might work, where if you deliberately touch the fingerprint reader three times within a short period of time with the incorrect finger, it would initiate a wipe.

    I’m thinking maybe like within 10 seconds.


  • The problem for screen reader users is that the better the voice sounds, the slower you have to use it at. And screen reader users generally like reading things at high rates of speed, and so generally are more willing to put up with the lower quality voices to get the faster speed.

    For something like your map application that says in 300 feet turn left onto X name of road it’s fine but for a screen reader user it’s a problem.