Every time I see a C function longer than 100 lines, I start to automatically question the quality of the code.
Now I'm looking to a 800 lines one...... 🫠
...
...
@sergiodj Yeah, this particular one is pretty old (maybe 2002), but there are other newer ones (from 2022) that follow the same pattern. I'd say it might be a cultural thing in this project (not to refactor nor extract functions)
Added Spanish (default, Argentina and Uruguay) translation (contributed by gnemmi).
Added Czech translation (contributed by pmjv).
Added Brazilian Portuguese translation (contributed by daltux).
Added Finnish translation (contributed by inz).
Added French translation (contributed by Popolon).
Added Russian translation (contributed by sn4il).
Added Chinese translation (contributed by mistivia).
Added German translation (contributed by zen and Menel).
Added Greek translation (contributed by uhuru).
Added Italian translation (contributed by anzu).
Mastodon API: added support for /api/v1/custom_emojis (contributed by violette).
Improved Undo+Follow logic (contributed by rozenglass).
Reverted (temporarily) the Markdown code that converted text between underscores to italics, because it was causing more problems that what it was worth.
Fixed bug in bookmark CSV import.
Don't indent Twitter-like "threads" (i.e. chains of short posts from the same author that are self-replies).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
...
I've just uploaded 2.74 to Debian unstable. This one is a bigger upload because I took the opportunity to fix a few bugs, so I'll wait a few days before I upload the version to bookworm-backports.
The package now automatically installs the language files (under /var/lib/snac2/lang/), and also creates symlinks for configuration files from /var/lib/snac2 into /etc/snac2.
https://tracker.debian.org/news/1630180/accepted-snac2-274-1-source-into-unstable/
https://github.com/macports/macports-ports/pull/27956
3/3 of GitHub Continuous Integration checks completed successfully!
Thanks to you (and gnemmi, pmjv, daltux, inz, Popolon, sn4il, mistivia, zen, Menel, uhuru, anzu, violette, and rozenglass; hopefully I didn't miss anyone?) for the continued improvements!
As with previous PRs I have submitted, I am abstaining from commit access until I have less chaos in my life to be able to take on more responsibilities, so it's up to someone else to merge it.
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces
...
you miss out these fun chats when you are not in the #curl IRC channel
...
@bagder @charles_melara was telling us yesterday that there's a few deeply technical discussions going from time to time and it was a great selling point. Unfortunately I can't join as it's not on Matrix or OFTC (which is bridged to Matrix). @sergiodj was looking into this and will soon send you an email about it.
...
@samueloph you can use https://chat.sr.ht ... thank @ddevault
You, people, are GREAT. Thank you very much.
#curl release candidate 1 for the pending release is here: https://curl.se/rc/
We'll appreciate if you take it for a spin and report any problems you find.
...
@bagder Available in the Debian experimental repository, can be used easily with:
$ podman run debian:experimental /bin/bash -c 'apt install --update -t experimental -y curl && curl --version'
If you use docker:
$ docker run debian:experimental /bin/bash -c 'apt install --update -t experimental -y curl && curl --version'
Or by enabling the experimental repository and installing it in your machine, if you use Debian.
Note that someone created various CVEs for #elfutils based on (fixed and closed) bug reports without following our SECURITY policy: https://sourceware.org/cgit/elfutils/tree/SECURITY
These are NOT security issues according to our policy.
We request that people who report suspected security vulnerabilities report them through the contacts in our SECURITY policy and not through non-affiliated CNAs.
Creating random CVEs without coordinating with the upstream project and designated CNA just causes lots of make work.
We have a #DebConf25 logo, thanks to Juliana Camargo and all other participants! https://bits.debian.org/2025/02/debconf25-logo-contest-results.html #debian
Running #KDE in my work laptop.
First time using KDE again since the days of KDE... 2? Been a user since the days os KDE 0.x.
Getting a feel of what a modern Linux desktop experience feels like in 2025.
And... it's good! A bit more Mac-like than I expected, but I haven't taken the time to test its customization ability to its limits.
Notifications are now shown in a more compact way (i.e. all reactions are shown just above your post, instead of repeating the post ad nauseam for every reaction).
New command-line option unmute to, well, no-longer-mute an actor.
The private timeline now includes an approximate mark between new posts and "already seen" ones.
Fixed a spurious 404 error in the instance root URL for some configurations.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song The Answers to the Questions by #Christabell and #DavidLynch.
...
...
...
...
I submitted a Pull Request to update MacPorts' snac to 2.70 here:
https://github.com/macports/macports-ports/pull/27556
1 of 3 GitHub Continuous Integration checks has passed (which is a good sign the other two will as well, eventually).
It's up to someone else with commit access to merge it.
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces #snacizens
Fixed memory leak (contributed by inz).
Fixed crash.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
...
Older...
https://github.com/macports/macports-ports/pull/27571
GitHub Continuous Integration checks are running, hopefully without issues? If so, then it will be up to someone else with commit access to merge it.
Thanks for your (and inz's) continued improvements to snac!
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces #snacizens
...
...
...
@mjw sorry to read this - hoping you don't have to deal with serious symptoms.
...
@sergiodj opa, foi mal, só vi a mensagem agora e to de saída pra pegar o trem! vai ter que ficar pra uma próxima! vc mora onde?
...
The declarative & minimalistic computing track is the one track where ‘org-tree-slide-mode’ is the standard tool for presenters.
...
Related to ¹ let's please take a moment to appreciate the hilarity of the historical perspective here, where emacs was once considered absurdly profligate with computer system resources and performance and is now considered to be minimalistic
¹: https://toot.aquilenet.fr/@civodul/113934442061942103 / @civodul @dthompson
@civodul Too sophisticated and distracting ... 😀 !
A collegue of mine got a permanent position, after a 20 min talk, hands in his pockets: this is minimalism.
Nice talk, by the way !
I just ran a 5K in 29:57. Crazy to think that I set a sub-30 5K time as a goal for 2025, but achieving it was easier than I imagined. I guess I'll just do easy runs until 2026 then :^)
...
...
@sergiodj everyone knows that a 29:57 aspect ratio is the best for hardcore coding
...
Added support for subscribing to LitePub (Pleroma-style) Fediverse Relays like e.g. https://fedi-relay.gyptazy.com to improve federation. See snac(8) (the Administrator Manual) for more information on how to use this feature.
Added support for following hashtags. This is only useful if your instance is subscribed to relays (see above).
Added support for a Mastodon-like /authorize_interaction webpoint entry, that allows following, liking and boosting from another account's Mastodon public web interface. To be able to use it, you must reconfigure your https proxy to redirect /authorize_interaction to snac (see snac(8)).
Some fixes to accept Event objects properly (like those coming from implementations like https://gancio.org/ or https://mobilizon.fr).
Added some caching for local Actor objects.
Hashtags that are not explicitly linked in a post's content are shown below it.
Fixed broken NetBSD build (missing dependency in Makefile.NetBSD).
The user profile can now include longitude and latitude data for your current location.
Mastodon API: implemented limit= on notification fetches (contributed by nowster), implemented faster min_id handling (contributed by nowster), obey the quiet public visibility set for posts, other timeline improvements (contributed by nowster).
Reduced RSA key size for new users from 4096 to 2048. This will be friendlier to smaller machines, and everybody else out there is using 2048.
If the SNAC_BASEDIR environment variable is defined and set to the base directory of your installation, you don't have to include the base directory in the command line.
Fixed a bug in the generation of the top page (contributed by an-im-dugud).
Added support for Markdown headers and underlining (contributed by an-im-dugud).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song Nine Hundred Miles by #BarbaraDane.
...
Older...
You nailed it again, well done! Thanks for your continuous development on snac! The LitePub integration will make many lives of snac operators much easier and improve the overall fedi network where posts will be more visible to everyone!
...
...
2.68-1~bpo12+1 yet.BTW Thank you all for the amazing work.
...
Also, it seems as if all the repeated boosts have the same username? I am guessing, whomever last boosted it (it was Jay Hannah previously I think, but now since I boosted the release announcement toot, I see my handle on all the repeat boosts). I don't remember observing behavior like that before, so I thought I would mention it.
2025:
- A fascist is the president of USA (United States of NORTH America ;-)
- We can't agree on a default branch name for packaging (really debian/latest or debian/unstable should be fine, do we really need 40 replies discussing that ?!)
- I almost lost my bus to the airport
Really unbelievable!
...
...
@sergiodj it's going ... well. I'll have a lot of stories for next weekend :-)
Some of these bots are clearly running on a bunch of machines on the same net. I have been able to reduce the traffic significantly by treating everything as a class-C net and doing subnet-level throttling. That and simply blocking a couple of them.
But that leaves a lot of traffic with an interesting characteristic: there are millions of obvious bot hits (following a pattern through the site, for example) that all come from a different IP. An access log with 9M lines as over 1M IP addresses, and few of them appear more than about three times.
So these things are running on widely distributed botnets, likely on compromised computers, and they are doing their best to evade any sort of recognition or throttling. I don't think that any sort of throttling or database of known-bot IPs is going to help here...not quite sure what to do about it.
What a world we have made for ourselves...
...
@corbet I recently dealt with something similar, a million IP addresses scraping my gitweb
I wonder if you're seeing hits to individual comment pages on LWN? That would match the pattern I was seeing.
How I dealt with it was noticing that the bots were hitting deep links that were only occasionally used by regular users. (Like LWN comment pages I imagine.) So a small degradation in an edge case that affected regular users was acceptable.
So I rate limited access to those urls. When over rate limit, my server serves up a response that says "Please wait..." and refreshes after a few seconds. The bots didn't refresh. When the server is not being swarmed by bots, regular users will see only a brief interruption. This cleared the botswarm for me in a couple of days, so it was apparently only incompetent spidering and not malicious.
I could imagine you doing something similar with lwn.net/Articles/* pages of type comment, and similarly not affecting most LWN users most of the time.
@corbet I'm trying to think of the AI training that would be using compromised hosts for scraping; I thought for training you had to do the training part on one or a small number of tightly coupled hosts; so then what is it?
...
This is beyond unsustainable. We are going to have to put time into deploying some sort of active defenses just to keep the site online. I think I'd even rather be writing about accounting systems than dealing with this crap. And it's not just us, of course; this behavior is going to wreck the net even more than it's already wrecked.
Happy new year :)
...
@corbet @LWN I think we should start doing what the internet can do best: Collaborate on these things.
I see this on my services, Xe recently saw the same. https://xeiaso.net/notes/2025/amazon-crawler/ (and build a solution https://xeiaso.net/blog/2025/anubis/)
There is https://zadzmo.org/code/nepenthes/
I would love to see some kind of effort to map out bot IPs and get a public block list. I'm tired of their nonsense.
Debuginfod project update 2024 by Aaron Merey
https://developers.redhat.com/articles/2025/01/14/debuginfod-project-update-2024
- Metrics and scale of debuginfod servers #prometheus
- New tools and features in debuginfod #elfutils
- IMA verification support
- Addressing kernel VDSO extraction bottlenecks @osandov
- Lazy debug info downloading in #Valgrind and #GDB
...
...
Fixed regression in link verification code (contributed by nowster).
Added ipv6 support for the https frontend connection (contributed by hb9hnt).
New "Like by URL" operation (contributed by dheadshot).
Added support for a Mastodon-like /share link sharing URL, like the one provided by sites like https://mastodonshare.com/ and such. To be able to use it, you must reconfigure your https proxy to redirect /share to snac (see snac(8)).
New linux landlock (sandboxing) support for enhanced security (contributed by shtrophic). It's still a bit experimental, so you have to enable it explicitly by recompiling with the WITH_LINUX_SANDBOX directive (e.g. make CFLAGS=-DWITH_LINUX_SANDBOX).
Some search fixes regarding repeated matches.
The export_csv cmdline operation now exports the CSV files inside a user's export/ subdirectory instead of the current directory.
All CSV files to be imported must now be stored inside a user's import/ subdirectory instead of the current directory.
Mastodon API: more timeline paging tunings (contributed by nowster), post language selected in apps is properly set.
The command-line operation note new reads the LANG environment variable to set the post's language.
A new command-line operation, note_unlisted, allows posting "unlisted" or "quiet public" posts.
The maximum number of entries in users' RSS feeds and in outboxes can now be set via the max_public_entries variable in the server.json file.
Fixed broken support for Audio objects.
Made xmpp and mailto URLs clickable.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the painting Judith Slaying Holofernes by #ArtemisiaGentileschi.
...
...
I thought about enabling sanboxing, but I'll wait until https://codeberg.org/grunfink/snac2/issues/267 is figured out.
...
I submitted a Pull Request to update MacPorts' snac to 2.68 here:
https://github.com/macports/macports-ports/pull/27332
GitHub Continuous Integration checks are running (two out of three completed successfully, which is a good sign, here's hoping the last one has no issues as well).
As usual, it's up to someone else with commit access to merge it.
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces
The search box also accepts post URLs; the post is requested and, if it's found, can be interacted with (liked, boosted, replied to, etc.).
IP addresses for failed logins are tracked and throttled to mitigate brute force attacks (see snac(8) for more information).
Fixed a bug regarding repeated attachments when editing a post.
Mastodon API: Improved timeline pagination in some clients (details: an HTTP Link header has been added), fixed missing audio attachments, fixed an incorrect value for the bot field in newly created accounts, fixed a crash, implemented markers (contributed by nowster).
When running in server mode, the pidfile is locked to avoid concurrent running of the same server instance.
Added documentation and some tweaks to enable static compilation with musl (contributed by Shamar).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
In the northern half we'll celebrate #SolInvictus by listening to the song One Perfect Sunrise by #Orbital.
...
Older...
https://github.com/macports/macports-ports/pull/27188
Two of three GitHub Actions Continuous Integration checks passed, which is a good sign; hopefully the others will pass without issues.
As usual, it's up to others with commit access to merge it!
Thanks again for your and others' continued improvements to snac! Specifically I noticed shout outs to nowster and Shamar in the RELEASE_NOTES.md and I seem to recall watching the discourse about the PID locking suggested and discussed rather collaboratively too!
(My apologies for the delay. The Makefile was slightly modified, which in turn broke the $files/Makefile.patch applied by MacPorts so I needed to rework that which took me a bit longer than usual given other work obligations I have had today.
Though not a concern for upstream, for MacPorts users I also noticed the following warning when running % port test:
"Warning: violation by /opt/local/man
Warning: snac violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended), it will be an error in future releases!"
Though, it appears as if the man pages are where I think they should be for MacPorts? I have never seen that Warning before, so my guess is something about MacPorts intended prescriptive behavior has been changed but I am not exactly certain what the expected behavior is supposed to be now? I will look into it further, but hopefully it isn't a concern for users at the moment; just thought I would mention it for the sake of being thorough!
However, it's entirely possible I messed something up too; so if others with greater wisdom than I see that Warning and know what to do to correct it, or if they encounter any other issues with MacPorts' snac, others are more than welcome to submit Pull Requests with improvements! Or feel free to open up an issue on MacPorts Trac instance at https://trac.macports.org and I'll look into it.)
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither#NotMuchBullShit #snacAnnounces
...
I've discovered a thing, though; if I have the ntfy app and Tusky running at the same time, Tusky adds 3 or 4 additional notifications to Ntfy (don't know why), and then chaos insues (I get repeated notifications all the time).
...
...
If I don't open Tusky, Ntfy works like a charm on my phone.
...
I'm not a big fan of FSF's policy on copyright assignment myself (although I understand the historical context), but I disagree with the advice of not contributing to the GNU project because of that. (Caveat emptor: I've been a GNU contributor myself for a number of years)