Dmitry Marakasov @AMDmi3@octodon.social
#FreeBSD developer and packager, F/OSS #gamedev enthusiast, #openstreetmap contributor, general libre sw/hw/data supporter
SourceForge is making the most fun of migration from #GitHub. The stuff most important to them is listed right in their site header: "Cloud Storage", "Business VoIP"... Then a nice set of social media buttons: twitter, facebook, google, linkedin. And right below that, a "Migrate from GitHub to SourceForge" banner, welcoming people who run from "proprietary" GitHub.
Not getting any new issues or pull requests on GH for more than a day depresses me.
Purism’s Security and Privacy Focused Librem 5 Smartphone Makes Major Strides in Manufacturing and Development. We're on schedule.
https://puri.sm/posts/librem5-smartphone-makes-major-strides-in-manufacturing-and-development/
TIL there are graphs of projects migrating from #GitHub to #GitLab:
https://monitor.gitlab.net/dashboard/db/github-importer?orgId=1&from=now-7d&to=now&refresh=1h
I myself am still boycotting any source code hosting facility apart from the most popular one. We'll see if that one changes over time.
I find all the floating cookie-"agree to me" messages annoying.
What's good:
They mostly don't ever pop up if you use the tor browser and disable javascript.
I hope the #gdpr will kill such messages. I believe most of them are not#gdpr compliant anyway, because they usually lack a "no, thanks, I want to surf your site without you collecting any personal data about me" button.
And no one can tell me that it is impossible to display a web page without collecting personal data.
#FreeBSD 11.1 is prone to sendfile related panics, even under moderate load. Had to disable sendfile for nginx and uwsgi for the host serving repology.org after 3 panics in 2 weeks.
Thankfully, it's fixed in 11.2.
Interested in PostgreSQL on FreeBSD? Try this OS patch which gives a substantial improvement in number of operations per second. Let us know how that works out for you. https://reviews.freebsd.org/D15430
I thought that #FreeBSD 12.0 is comming next year. Nice surprise: https://www.freebsd.org/releases/12.0R/schedule.html
Repology has support for history of version updates for all projects now. It's interesting to see how new software releases spread along the repositories (https://repology.org/metapackage/subversion/history for example).
Next step is per-maintainer histories and RSS/Atom feeds!
The aggregated history of ALL software releases is possible now too, but I don't find it practically usable, as there are A LOT of them.
How can we expect users to make a distinction between phishing and legit email when legit email can look as shitty as this?!?
Bean time lapse - 25 days soil cross section
Recently introduced #tor DOS protection seems to be working, after update to 0.3.3.3 my FreeBSD tor relay no longer sees spurious mbuf clusters usage spikes. Thanks for making tor more and more bulletproof!
Latest screenshot from Tanks of Freedom github. Notice HUD changes that will land in the next, big update.
I need an android app which allows doing something useful. Coz I'm tired of chatting, gaming or reading garbage from social media. Something:
- f/oss only
- plug and play (no need to manually search for a project to work on as with e.g. stringlate)
- simple (no need to edit huge texts, as it's a phone)
- developer oriented
Small string translations, code reviews, bug triaging, image classification, proofreading maybe.
Any suggestions?
#PostgreSQL has failed me for the first time. Being unable to optimize seemingly simple SELECT ... WHERE TRUE OR field IN (SELECT ...) and eliminate the join, it leaves me no choice but to shove template engine into my database handling code...
The next crazy idea for #poudriere run for all #FreeBSD ports: require license to be defined by all ports.
cat >>make.conf
LICENSE?=NONE
LICENSES_REJECTED=NONE
The end goal is to have license information filled for all ports. In particular, it's important to identify ports which do not have clearly defined license, as these cannot be legally packaged and redistributed by the project, and pose legal risks to users too. The intermediate goal is to fill licenses for ports with a lot of consumers.
Forgot to mention that there's a problem though, which is when a port installs python3-incompatible script which is not called in the build process of neither the port itself nor the ports that depend on it, so the build won't catch these.
I'll look for python3 compatibility checking tool, I guess I could run it on packages I now have to find unaccounted incompatibilities.
