

if it is signed by a key used in public repos of the commiter, or otherwise known to possess the key, that is proof, yes


if it is signed by a key used in public repos of the commiter, or otherwise known to possess the key, that is proof, yes


I think copyparty can handle partial transfers both ways


unencrypted, unauthenticated, unverified, and not just hard but impossible on phones.


I’m not sure that’s needed, but the firewall on your PC is likely to be blocking the connection by default


why another wifi standard? we already have wifi adhoc mode, and at least 2 different wifi directs. why couldn’t they just build upon that?


btw localsend has some plans for supporting google’s somewhat common but proprietary quickshare functionality, but it seems the app hasn’t received an update in almost a year


but it’s still an alternative insofar as two people can transfer files to each other
after painfully figuring out (or not) how to make a hotspot with a somewhat secure password and get the other phone to connect to it.


thanks! also, I think as things are now, it’s fine to keep using lemmy for your server. but keep in mind that in the future they could implement features that are not for the benefit of your community. anything can be reverted with some custom development, but you may not want that.
there are some lemmy instances that are planning a switch to piefed, with a database migration so that existing content and users are kept. the one I use is among them.
updates to lemmy can make such a migration harder in the future, even unintentionally.


they recommend people to donate to lemmy devs in the reddit post, though.
I am not blaming them, they probably didn’t know it, but it’s worth mentioning.


the commiter name in the repo is not ironclad proof, anyone can upload commits to their repo in Linus Torvalds’ name. but github probably has the capabilities to find out who was the original uploader of the commit, or what was the upstream repo of a fork


oh that’s good to know, thanks!


Tracker-free? There’s literally no way anyone could track you through RSS. It’s just an XML file and can’t run any arbitrary code.
there is actually. the user agent string, ip address, when do the images get loaded. if clients can user server provided CSS, that too can do some conditional reports. but yes the possibilities are much fewer, they are easier to fix.
Advice of the Day
Honestly? Turn off that analytics completely. Who needs it? What insights will logflare give you when the server can barely breathe? It’s like buying a fitness tracker when you’re in the ICU. Or at least drop that memory limit to 1GB and let it die faster.
LOL!!!


installing the carrier app is the same as contacting the carrier. it’ll work until they allow it


I was using it all the time when I was daily driving windows, mostly for ssh, starting from when it was just beta with no settings menu but only the config file. I remember that like the standard powershell shell, powershell tabs of wt too had a blue background, but opening a default new tab always opened a black tab, a cmd based tab.


and how do you enable shizuku? you need a PC for that too


that would be fine, without the login and sim card requirement


edit: this is an article from November, its not something new…
bullshit! if this is actually what the “new” rule is, the exact same thing was already part of their unacceptable original plans.
To accommodate educational and noncommercial development, Google will introduce a new limited developer account type aimed at students and hobbyists. These accounts will not undergo full identity verification but will instead allow app installations on a restricted number of registered devices.
no to any kind of accounts, to any kind of developer registration, and any kind of install limits! its none of google’s business what apps people install outside their store, and so they shouldn’t be able to enforce a global installation limit for any apps!
was duplicate