u/lukmly013 💾 (lemmy.sdf.org)

I like computers, trains, space, radio-related everything and a bunch of other tech related stuff. User of GNU+Linux.
I am also dumb and worthless.
My laptop is ThinkPad L390y running Arch.
I own RTL-SDRv3 and RSP1 clone.

SDF Unix shell username: user224

  • 5 Posts
  • 43 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle

  • I just realized I sound way too paranoid but it’s an interesting question

    Nope. Not paranoid enough. If school/work requires such software, that goes onto a separate device only for those purposes, which will then be considered untrustworthy environment like any public computer.

    Although perhaps in a sense it is paranoid compared to what others do. Recently I’ve had to get something printed without having own printer. I’ve found out people have no problem logging into their Google or Microsoft account on public PCs.
    I brought the PDF on a CD.
    There’s a certain small chance that something malicious could be written to a USB, and I don’t know about all the possible vulnerabilities. If mounted, perhaps the automatic media thumbnail generator could be exploited. That is probably paranoid, worrying about random software installed on your own computer is certainly not.









  • I think we just have to accept that no solution is 100%. You just need some balance between success and side effects.

    As long as people can communicate, it will to some extent spread. So really, the only truly 100% solution would be a couple of nuclear bombs all around the world. Look at that, crime rates went to 0!

    I am not really intelligent or knowledgeable enough to provide best-balance solutions.

    Anyway, as far as limiting access to porn, perhaps it could be done privately. You could have some trusted verification platform, perhaps even government provided, deal with it with cryptographic signature, maybe as I said, I am too dumb for solutions.
    My idea is, the website that wants to verify your age knows the public key of the government provided service used for this purpose (who already has your data anyway), and generates some random data in base64. You copy that, paste it into the verification website, they sign it, and give you the base64-encoded response. You then paste the response into website that wants to verify your age, it verifies the signature and then that you’re 18+.

    Basically just trusted authority saying “verified being 18+”. The website doesn’t know who you are, verification system doesn’t know what you wanted that verification for.

    Of course, you could verify that for anyone else, but I can also walk into a shop, buy cigarettes, alcohol and give them to a kid. Not 100%, but good enough.







  • Phone acting as tablet. Settings “smallest width” to 600dp or more triggers tablet mode on Android, which changes certain UI elements to, in my opinion, make more sense on average near 7" smartphones. At least for me as I am a landscape-first user.

    So, since I already screwed up my homescreen layout by toggling this now, I’ll give you screenshots to compare between 423 (smallest in regular settings) and 705dp (what I use). 423 on left, 705 on right.

    Took me longer than I anticipated, but anyway:

    Sorry for the JPEG, original was 18MB.

    Notice the difference in keyboard layout, and 3 button navigation with app icons and app drawer.

    You should be able to click the image to open it, at least on LemmyUI.


  • Release doesn’t even have tab bar yet.

    Beta does, but only has the new menu and homepage doesn’t count as tab like on desktop and doesn’t support DoH, like on desktop.

    Nightly is most feature-complete.

    But I’ll have to figure out how to check existing and report new bugs. Search may not work when I hit enter, opening links with Firefox just opens the homepage, only when I click back does it actually open the link, screenshots sometimes don’t work, but only after I go to tab menu and then back, and the bottom-most thing in homepage is cut-off, so I use the stories as padding (might be related to custom high system-wide DPI).





  • I think the eID should be unique and gets transmitted.

    That’s probably the ID that forbids me from installing (another) speedtest eSIM, though “ID” could also refer to IMEI perhaps. I’d have to try another phone.

    Error code: ES10B_ERROR_REASON_UNDEFINED
    
    Last HTTP response (from server):
    
    {
    	"header": {
    		"functionExecutionStatus": {
    			"status": "Failed",
    			"statusCodeData": {
    				"subjectCode": "8.2.6",
    				"reasonCode": "3.8",
    				"subjectIdentifier": "Matching ID",
    				"message": "Refused"
    			}
    		}
    	},
    	"transactionId": "[You don't need this]"
    }
    
    Last APDU response (from SIM) is successful
    

    Based on this, it is a part of the transmitted information, if I understand it right: https://www.sharetechnote.com/html/Handbook_LTE_eSIM.html