social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

502
active users

#sourceforge

0 posts0 participants0 posts today

Does #gnuplot project <gnuplot.info/> not believe in providing SHA(512|256) checksums of download files? Or, PGP/GPG signature of the file (along with public key)?

The downloading behaviour on #SourceForge <sourceforge.net/projects/gnupl> <sourceforge.net/projects/gnupl> in itself creeps me out for having a fucking redirection. Why.

And I just realized that the project website itself uses "HTTP" without the "S". Yeah😐

I would not have to look into installing v5.4.10 on someone's request if it was available as a package for #RockLinux 8 that work has in use.

It has not moved to v9+ due to lack of support for NIS; moving to LDAP is planned in 1+ years.

www.gnuplot.infognuplot homepage

I manage #passwords in an encrypted text file which, when opened in #emacs, is decrypted after I provide the password. When I need a password, I run a decrypting grep on any snippet of the site where I want to log in.

But: the en/decryption is handled by ccrypt, which looks like ancient, abandoned as it is on sourceforge😩 . Then I found passwordstore.org/ .

Looks really nice. Passwords plus other data in small text files, encrypted in a git repo.
#pass #sourceforge #linux

www.passwordstore.orgPass: The Standard Unix Password ManagerPass is the standard unix password manager, a lightweight password manager that uses GPG and Git for Linux, BSD, and Mac OS X.

@deflarerOfClouds #GitHub has hosted #PerlTidy development for a long time. Please continue to file bug reports there: GitHub.com/perltidy/perltidy/i

You might even consider making a reasonable case to move the project’s remaining assets off #SourceForge. Impotently whinging about it here doesn’t change anything.

/ @ChristosArgyrop @ovid @perl #Perl

Perl::Tidy, a source code formatter for Perl. Contribute to perltidy/perltidy development by creating an account on GitHub.
GitHubIssues · perltidy/perltidyPerl::Tidy, a source code formatter for Perl. Contribute to perltidy/perltidy development by creating an account on GitHub.
Replied to Mark Gardner

@mjgardner @Perl @ChristosArgyrop @ovid Certainly it’s an embarrassment considering #Sourceforge has recently joined the exclusive walled-garden of #Cloudflare. I cannot reach any sourceforge.net/* pages. But I can reach perltidy.sourceforge.net because it’s CF with Tor whitelisted. However, I’ll still avoid it on principle. I don’t think I’ve filed bug reports there but certainly I will not in the future.

[2208.04259] First Come First Served: The Impact of File Position on #CodeReview
arxiv.org/abs/2208.04259

arXiv logo
arXiv.orgFirst Come First Served: The Impact of File Position on Code ReviewThe most popular code review tools (e.g., Gerrit and GitHub) present the files to review sorted in alphabetical order. Could this choice or, more generally, the relative position in which a file is presented bias the outcome of code reviews? We investigate this hypothesis by triangulating complementary evidence in a two-step study. First, we observe developers' code review activity. We analyze the review comments pertaining to 219,476 Pull Requests (PRs) from 138 popular Java projects on GitHub. We found files shown earlier in a PR to receive more comments than files shown later, also when controlling for possible confounding factors: e.g., the presence of discussion threads or the lines added in a file. Second, we measure the impact of file position on defect finding in code review. Recruiting 106 participants, we conduct an online controlled experiment in which we measure participants' performance in detecting two unrelated defects seeded into two different files. Participants are assigned to one of two treatments in which the position of the defective files is switched. For one type of defect, participants are not affected by its file's position; for the other, they have 64% lower odds to identify it when its file is last as opposed to first. Overall, our findings provide evidence that the relative position in which files are presented has an impact on code reviews' outcome; we discuss these results and implications for tool design and code review. Data and materials: https://doi.org/10.5281/zenodo.6901285

After the #XZ attack, I have a suggestion for all #software forges (#Forgejo, #GitHub, #Gitea, #Sourceforge, etc.):
Have some way to visualize binary files better, including diffs to such files. Cuz now, we have basically nothing except byte counters.
Since they're binary files, it must be as generic as possible. But even *some* rendering or analysis is better than nothing.

The idea is to expose weird patterns in binary files that could be a sign of an attack.

It's not just #Apple's consumer-facing software that is frustratingly obtuse. I downloaded their package of HTTP Live Streaming tools from the developer downloads site, only available for #macOS and #CentOS 7. Tried running CentOS via both #Docker and #DigitalOcean, and get the same error about a missing library. There are zero Google results for the name of the file the tools are looking for, while searching for the specific library (libifs) turns up a #SourceForge project last updated in 2004 documented only in Polish. Guess I'll be running them on the Mac instead, then.