Matija Nalis

@samuel@polymaths.social #Sideloading is a term - it is when you use another computer on the SIDE of your mobile device, connect them via cable (that is why it has to be on the SIDE) and use that other computer to remotely install the app on the mobile device, without mobile device having a choice. You know, like with "adb sideload" command. Using your web browser or app store of your choice on your mobile device to install apps is just regular "installing apps". @fdroidorg@floss.social

@Su_G@aus.social We've kidna had it implemented in Yugoslavia (until its wars). It was called "samoupravni socijalizam" ("self-governing socialism"). Workers were shareholders, and (when majority had same opinion of course) could override ANY managment board decision. While there were few disadvantages (think: not all workers being educated enough about all parts of the production), it worked remarkably fine in most cases (IMHO). Then came privatization and many great companies crumbled. @hosford42@techhub.social

@olberger @Doune Yes, the reference is about that Clippy in Microsoft Word, but being used for Pro-Consumer movement started by Louis Rossman. See https://www.youtube.com/watch?v=2_Dtmpe9qaQ for reference

@osm_tech @BalooUriza is it using ipset hashsets, or default rule-per-ip rules? raw namespace or? I don't know the details of implementation, but if it is L7 load that is problematic (instead of pure bandwidth DDoS), it might be worth to consider whitelisting instead. I.e. whitelist addresses (or /24s) that have *not* had excessive requests lately, and put them in priority network bucket, and the rest (which is not blacklisted) goes in best-effort bucket (to maybe migrate to whitelist later)

@IzzyOnDroid @thomas Yeah, I fully agree that google is also driven by capitalism towards more and more #enshitification 😢 . And ability to reach a human there was getting very hard even decades before #AI, nowadays it is nigh impossible and incredibly frustrating. I hope those "it is safe" reports would make it more likely for a problem to be fixed; but I worry it depends more on luck than that 😭

@vg @organicmaps @forgejo Yes, and Obtainium instructions and videos should be updated to new links... fixing all of it will take some time I guess. I'm more worried that git access is not working currently at all 😞

@samuel@polymaths.social @fdroidorg@floss.socia In other words, #Google is intentionally misusing the term, trying to redefine #sideloading to mean "using your phone in any way that prevents Google from collecting and selling your personal data, or having user having any ownership rights on their device". I would suggest #EU to bill Google 10€ for false advertising for each time they've thus misused the word "sideloading", multiplied by number of all Android phones ever sold, multiplied by number of days this continues

@SteveDuncan@mastodon.social to be truthful, when you think about it, people are hard part of any endeavor, even if it involves *just one* person (yourself). And that is much more widespread problem, not limited just to computing. @maaikees@sw-development-is.social

@PeterLG@theblower.au I believe the word you're looking for is "easier", and not "easy". Or more precisely, "less hard". It's much *easier* to get humans to Moon and back alive then to Mars and back, but it is by no measure "easy". Also, coding is only the small (and much easier) subset of programming. And nobody who ever did it properly would disagree about the hardest part - It's always humans that are the biggest problem, in one way or another. @maaikees@sw-development-is.social

@chris@mastodon.chrispelli.fun Unlikely. If there is next DNS address record, it is extremely likely going to be using a power of two (so at least "AAAAAAAA")... Originally "A" (address) DNS record is for IPv4 (which has 32 bits), and since IPv6 has 128 bits (i.e. 4 times as many bits as original one) its address record was named with 4 times as many A letters (i.e. "AAAA"). Yes, that's how we computer geeks have fun naming things! #IPv6 #DNS@cuu508@toot.lv @kevin@mastodon.km6g.us

@jerry their Fediverse posting bot is broken in that regard for some time now, and unfortunately they don't seem to read replies here either You should contact them on their webpage about that issue @letsencrypt

@everydoor Yes, I understand licensing is hard and not something most devs want to learn. For firmware analogy I'll point you to the difference between terms "covered work" and "aggregate" in #GPLv3 text if you want to read more yourself. But I'll drop the subject now, as you seem to dislike me trying to help, and I really don't want to antagonize you. I apologize again if I did. I can suggest fsf.org, fsfe.org or sfconservancy.org if you'd like to get authorative opinions on licensing. 2/2

@IzzyOnDroid @thomas Dunno if it is related, but it seems that besides Google, Ikarus is misdecting StreetMeasure APK from izzy as being infected by "Trojan-SMS.AndroidOS.FakeInst" e.g. I've downloaded de.westnordost.streetmeasure_7.apk from izzy, and it is exactly the same file as one downloaded ages ago from Google Play (with sha256sum 9711592efeab66fc47454a628abcb88d25356d24a80de34882b2ff4cd1f921af) and virustotal says this: https://www.virustotal.com/gui/file/9711592efeab66fc47454a628abcb88d25356d24a80de34882b2ff4cd1f921af

@everydoor That sounds great! Does that mean that https://github.com/Zverik/every_door/issues/975 has been resolved too in 8.0-alpha2?

@everydoor I know you're working on that (thanks!), so hopefully that will land soon too.

I'm mentioning it because AFAIK with Every Door code now being GPL, it is not legal for anyone (not only F-droid, but also GitHub, GooglePlay or anyone else) to legally distribute precompiled .apk files -- as they are derived work of both the GPLv3 code and GPLv3-incompatible code. (that is the main difference between GPLv3 and LGPLv3, as only the latter would allow for such mix to be distributed. IANAL)

@everydoor Any chance that 8.0 release of #EveryDoor might replace that non-FOSS dependencies that were inadvertently introduced in 7.0? https://github.com/Zverik/every_door/issues/975 I'm sticking with last fully-#FOSS 6.0 release from #Fdroid but would love to use the new features! (if the price is not installing proprietary blobs of non-free code on my phone) #OpenStreetMap

@darthnull@infosec.exchange if that was the case (only 32% growth), graph would've started at 100%, not at 0%, no? @SPF@hear-me.social @briankrebs@infosec.exchange

@jimkats@infosec.exchange @InsertUser@en.osm.town In #JOSM, you would just select the whole polygon and press "g" to detach it (thus effectively solving the issue as IIUC, as after that single keypress it would be just as if the original mapper had never attached that landuse to existing ways). Of course you'd still need to correct the geometry of the landuses if it is incorrect, but you'd have anyway even if user did not attach it to existing OSM elements)

@jimkats@infosec.exchange @InsertUser@en.osm.town Whoa, dude, I just wanted to help, no need to get all worked up! Not everybody knows your personal preferences and annoyances (and your Mastodon profile doesn't mention them). I mentioned solution in JOSM because I knew solution in JOSM. If I knew solution in SCEE, I would've mentioned that too, as that is the editor I prefer. If you don't want to hear of alternative ways to fix the original issue, please mention it in the post that you're looking for iD solutions only.

@organicmaps@mastodon.social @forgejo@floss.social Re: "Everything moved. Nothing left behind." -- what about GitHub discussions (not issues)? I don't see them (does Forgejo even support them?)