resist1984 @resist1984@social.privacytools.io
Joined Mar 2019
@werwolf @fedeproxy @dachary Once there is enough momentum, developers of GH project will feel pressure to cooperate.
@dachary @fedeproxy @werwolf when i find a bug, i'm disturbed not only that i can't tell the devs, but that no one else sees it either. Posting it to forums doesn't get much exposure. But if fedeproxy gives an easy way collect & publish bug reports in a way that aggregates them by project, i'm satisfied that users have a common place to report bugs and see what others have reported.
@werwolf @fedeproxy @dachary For me it's good enough to be able to publish a bug report where others can see, discuss, & reference, even if the project devs neglect it.
@dachary @fedeproxy @werwolf Crowd-sourcing accounts could work for a while, but it's anyone's guess whether MS robotically detects and suspends shared accounts. If the bug reporting fails to reach Github in a sustainable way, will fedeproxy still accept bug reports that don't make it over to Github?
@werwolf @fedeproxy @dachary looks like it can (https://fedeproxy.eu/blog/2021/01/16/what-is-fedeproxy/) but wouldn't that require some action from the owner of the github project? If so, that's really limiting. I'm sitting on unfiled bug reports because the only way to file them is to work with Github, and often I can't reach the authors (who assume people will reach them in the GH #bug tracker).
@dachary @fedeproxy @werwolf does fedeproxy give a way to submit bug reports on Github projects without having a Github account?
@werwolf @dachary For cloning Github projects, there already is a privacy-respecting frontend: git. To clone over Tor, do something like "git clone --config http.proxy=http://127.0.0.1:8118 https://github.com/nasa/fprime"
@dachary @werwolf a frontend to #Github would only be a marginal improvement, and in the end you're still bringing business to a socially irresponsible privacy offender. Luckily there are tens of good alternatives that make it easy to ditch github: https://git.sdf.org/humanacollaborator/humanacollabora/src/branch/master/forge_comparison.md
@boud @VickyRampin Thanks! I didn't know about zenodo.org but it looks very useful.
@boud @codeberg @switchingsoftware @VickyRampin If it were my paper, I would list the archive.org URL alone & omit the original site because the archive.org URL includes the original URL.
@VickyRampin @switchingsoftware @codeberg @boud I suppose you might have chosen archive.today over archive.org because of the shorter URL. Archive.today is an exclusive walled garden, while archive.org is a #ALA (american library assoc.) member that respects ALA principles & grants access to all. Note as well that archive.today is protectionist & blocks the archive.org bot, yet #archive.org does not block the archive.today bot.
@boud @codeberg @switchingsoftware @VickyRampin the best would be to have a software heritage link, but unfortunately SWH has not archived sdf.org yet
@VickyRampin @switchingsoftware @codeberg @boud i think it would go along with your thesis. Couple anomalies: the superscripts use the same numbering system as the citations, and there are conflicts (citation 38 can be confused with superscript 38). Starting citation numbers at 100 would fix that. It's good that you give an archive link on 38, but archive.today is a cloudflare site that redirects to another. I suggest archive.org
@boud @codeberg @switchingsoftware @VickyRampin i love the way you did your footnotes, using superscripts for hyperlinks at the bottom of the page & bracketed references to MLA/APA citations at the end. A also love the code listings; great idea to color the comments gray inside of a verbatim environment. Is the tex file published anywhere? It would be cool to use the attachfile pkg to embed a copy of the latex code in the pdf.
resist1984
boosted
resist1984
boosted
#Siteground redirects #Tor users to a ".well-known/captcha" link using "meta http-equiv" in the body instead of a normal 301/302 server redirect & instead of giving a 403 status, it gives a 200. E.g., run this:
curl --ssl --socks4a 127.0.0.1:9050 -L -w $'\n''(effective URL => "%{url_effective}")' 'https://www.samsonbanking.com/'
It seems they are trying to conceal their detection of bots from bots. But it's just another thing for the bot to check.
Is this an example of #securityByObscurity?
@protonmail @Decentralize_today The marketing dept. for #Protonmail may say aesthetics have high importance, but that shit should be kept internal, not announced. Whenever I read that a service is spending time on aesthetics, it's a signal that they are wasting time fiddling with appearances instead of fixing and improving -- and there's a lot that needs to be done in that regard.
@Decentralize_today That @protonmail announcement says "Focus on what really matters", then they follow with "The new ProtonMail offers a modern look and feel". Look & feel is not in the slightest "what really matters". The "too many access attempts" error that I often get even when I've not attempted to login for days-- fixing that #bug matters. Look & feel should be a bottom priority.
@lnx It's not the consumer's fault. It's the maker's fault. They designed the heating element to be non-removable so cleaning under the heating element requires full disassembly of the whole machine. No one is disassembling these things after each use. The fan & the heating element should be designed for easy removal w/out taking anything else apart. I wonder if any models got that right
Joined Mar 2019
