The approvals were required under Israel’s Land Law because Nvidia is a foreign-controlled company. The deal will allow the global technology giant to establish a new development campus on state land, allocated without a public tender and at a 51% discount.
The proposed 51% land discount is valued at tens of millions of shekels. Officials cited the significant economic impact on northern Israel, noting that thousands of employees would work directly at the campus and that hundreds of additional businesses are expected to benefit from providing services to the site.
According to the plan, Nvidia will build a unique, large-scale campus unlike any previously seen in Israel, modeled in part on the company’s headquarters in Santa Clara, California. The project is expected to span approximately 160,000 square meters and employ about 8,000 workers.
The Israel Land Authority says a deal granting Nvidia discounted land in Kiryat Tivon for a massive new development campus will be signed within days, after receiving required approvals due to the company’s foreign ownership
The Memorial to the Victims of Communism has already been the focus of multiple controversies over its exact purpose, location, size and cost over the last 15 years. The price tag for the project has ballooned to an estimated $7.5 million — including $6 million in public funds — from an original budget of $1.5 million. The memorial, originally started by the Conservative government of then-prime minister Stephen Harper, was supposed to be funded entirely through private donations.
But taxpayers are now footing most of the bill as that private fundraising initiative fell far short when significant public financial support did not materialize.
The memorial was opened on Dec. 12, 2024. At that time, Ludwik Klimkowski, who leads Tribute To Liberty, the organization behind the memorial, said names would be added within a year.
But, when Klimkowski spoke at the official
... show more
The Memorial to the Victims of Communism has already been the focus of multiple controversies over its exact purpose, location, size and cost over the last 15 years. The price tag for the project has ballooned to an estimated $7.5 million — including $6 million in public funds — from an original budget of $1.5 million. The memorial, originally started by the Conservative government of then-prime minister Stephen Harper, was supposed to be funded entirely through private donations.
But taxpayers are now footing most of the bill as that private fundraising initiative fell far short when significant public financial support did not materialize.
The memorial was opened on Dec. 12, 2024. At that time, Ludwik Klimkowski, who leads Tribute To Liberty, the organization behind the memorial, said names would be added within a year.
But, when Klimkowski spoke at the official opening about adding the names, a protester shouted “No Nazis.”
Several hours later, the Liberal government issued a statement claiming that no specific timeline about the names had been agreed to by the federal government.
The memorial, originally started by the Conservative government of then-prime minister Stephen Harper, was supposed to be funded entirely through private donations.
But taxpayers are now footing most of the bill as that private fundraising initiative fell far short when significant public financial support did not materialize.
this is so on brand for cons…
this was yet another shit gift by Harper that Trudeau chose to step on
The controversial Victims of Communism memorial in downtown Ottawa will no longer feature the names of specific individuals after federal officials determined a significant number could be linked to the Nazis.
It's pretty common for victims of communism initiatives given who the communists fought.
The Soviet Union lost somewhere between 20,000,000 and 27,000,000 lives fighting the Nazis in WW2. Canada lost 43,600, and the US 419,400. But it's never been popular to talk about the Soviet contribution to the war because that makes you a tankie.
Victims of Communism organization is a nazi/CIA group who exists to justify war. Canadian establishment that gives standing ovations to Ukrainian nazis is very supportive, but this is a small victory for rationality even if Zionist hate groups were involved in blocking it.
Besides of stuff like this, another problem with this kind of performative anti-communist activism is that they make it look like the problems of "communist" regimes were exclusive and inalienable part of communism. The great takeaway of Lysenkoism isn't "politicization of science is bad" for many, but that "we need a good politicization of science", and we then got RFK Jr.
I’ve been setting up a new Proxmox server and messing around with VMs, and wanted to know what kind of useful commands I’m missing out on. Bonus points for a little explainer.
[code]Journalctl | grep -C 10 'foo'[/code] was useful for me when I needed to
I've been setting up a new Proxmox server and messing around with VMs, and wanted to know what kind of useful commands I'm missing out on. Bonus points for a little explainer.
Journalctl | grep -C 10 'foo' was useful for me when I needed to troubleshoot some fstab mount fuckery on boot. It pipes Journalctl (boot logs) into grep to find 'foo', and prints 10 lines before and after each instance of 'foo'.
I'm not much of a one-liner collector but I like this one:
vim +copen -q <(grep -r -n <search> .)
which searches for some string and opens all instances in vim's quickfix list (and opens the quickfix window too). Navigate the list with :cn and :cn. Complex-ish edits are the obvious use case, but I use this for browsing logs too.
Neovim improves on this with nvim -q - and [q/]q, and plenty of fuzzy finder plugins can do a better version using ripgrep, but this basic one works on any system that has gnu grep and vim.
Edit:
This isn't exactly a command, but I can't imagine not knowing about this anymore:
$ man grep
/ -n # double space before the dash!
brings you directly to the documentation of the -n option. Not the useless synopsis or any other paragraphs that mention -n in passing, but the actual doc for this option (OK, very occasionally it fails due to word wrap, but assuming the option is documented then it works 99% of the time).
Something that really improved my life was learn to properly use find, grep, xargs and sed. Besides that, there are these two little 'hacks' that are really handy at times...
1- find out which process is using some local port (i.e. the modern netstat replacement):
$ ss -ltnp 'sport = :<port-number>'
2- find out which process is consuming your bandwidth:
You can do "ss -aepni" and that will dump literally everything ss can get its hands on.
Also, ss can't find everything, it does have some limitations. I believe ss can only see what the kernel can see(host connections), but tcpdump can see the actual network flow on the network layer side. So incoming, outgoing, hex(?) data in transit, etc.
I usually try to use ss first for everything since I don't think it requires sudo access for the majority of its functionality, and if it can't find something then I bring out sudo tcpdump.
parallel, easy multithreading right in the command line. This is what I wish was included in every programming language's standard library, a dead simple parallelization function that takes a collection, an operation to be performed on the members of that collection, and optionally the max number of threads (should be the number of hardware threads available on the system by default), and just does it without needing to manually set up threads and handlers.
inotifywait, for seeing what files are being accessed/modified.
tail -F, for a live feed of a log file.
script, for recording a terminal session complete with control and formatting characters and your inputs. You can then cat the generated file to get the exact output back in your terminal.
screen, starts a terminal session that keeps running after you close the window/SSH and can be re-accessed with screen -x.
Finally, a more complex command I often find myself repeatedly hitting the up arrow to get:
find .
... show more
parallel, easy multithreading right in the command line. This is what I wish was included in every programming language's standard library, a dead simple parallelization function that takes a collection, an operation to be performed on the members of that collection, and optionally the max number of threads (should be the number of hardware threads available on the system by default), and just does it without needing to manually set up threads and handlers.
inotifywait, for seeing what files are being accessed/modified.
tail -F, for a live feed of a log file.
script, for recording a terminal session complete with control and formatting characters and your inputs. You can then cat the generated file to get the exact output back in your terminal.
screen, starts a terminal session that keeps running after you close the window/SSH and can be re-accessed with screen -x.
Finally, a more complex command I often find myself repeatedly hitting the up arrow to get:
Recursively lists every file in the current directory and uses parallel to perform some operation on them. The {} in the parallel string will be replaced with the path to a given file. The '*' part can be replaced with a more specific filter for the file name, like '*.txt'.
should be the number of hardware threads available on the system by default
No, not at all. That is a terrible default. I do work a lot on number churning and sometimes I have to test stuff on my own machine. Generally I tend to use a safe number such as 10, or if I need to do something very heavy I'll go to 1 less than the actual number of cores on the machine. I've been burned too many times by starting a calculation and then my machine stalls as that code is eating all CPU and all you can do is switch it off.
nc is useful. For example: if you have a disk image downloaded on computer A but want to write it to an SD card on computer B, you can run something like
user@B: nc -l 1234 | pv > /dev/$sdcard
And
user@A: nc B.local 1234 < /path/to/image.img
(I may have syntax messed up--also don't transfer sensitive information this way!)
Similarly, no need to store a compressed file if you're going to uncompress it as soon as you download it---just pipe wget or curl to tar or xz or whatever.
I once burnt a CD of a Linux ISO by wgeting directly to cdrecord. It was actually kinda useful because it was on a laptop that was running out of HD space. Luckily the University Internet was fast and the CD was successfully burnt :)
I could very easily, I've just only use rsync a handful of times for one-off files or small directories. Thinking of using it for several Tbs scares me 😅
Journalctl | grep -C 10 'foo' was useful for me when I needed to troubleshoot some fstab mount fuckery on boot.
Ha! Remember back when there was no fstab fuckery? Good times. But you have a massive init blob slowly eating other services and replacing them with shitty replicants like this embarrassment (ohai root NFS) and all of us Unix people are chuckling in our reduced-fuckery 'hell'.
When transfering large amounts of data I'd most definitely advise using rsync. Something fails, connection falls and everything is okay as it'll pick up where it left off.
I usually set vi mode to have vi(m)-like line editing but I've always liked Ctrl+u over Esc d d. Thankfully it still works even with vi mode enabled. Seems to also be implemented as a shortcut for a lot of login managers and in DEs for settings menus, dialog boxes and such.
Sometimes starting a service takes a while and you're sitting there waiting for the terminal to be available again. Just add --no-block to systemctl and it will do it on the background without keeping the terminal occupied.
I have my .bashrc print useful commands with a short explanation. This way I see them regularly when I start a new session. Once I use a command enough that I have it as part of my toolkit I remove it from the print.
You can use M-. instead of $_ to insert last param of last command. You can also access older commands' param by repeated M-. just like you would do for inserting past commands with up arrow or C-p
For interactive editing, the keybind alt+. inserts the last argument from the previous command. Using this instead of $_ has the potential to make your shell history a little more explicit. (vim $_ isn't as likely to work a few commands later, but vim actual_file.sh might)
I'm sure it'll be fine, I'm no expert but i use it it sync/clone my music storage with my music player. There's thousands of songs, lyrics, and album art getting synced and backed up regularly in my case.
Worst thing that happened to me happened when I was new to the tool and accidentally overwrote my source directory (luckily I had backups)
No. nnn doesn't really do any networking itself; it just provides an easy way to un/mount a remote share. nnn is just a TUI file manager.
For transfering 5TB of media, I'd acquire a 5TB USB 3.2 drive, copy þe data onto it, walk or drive it over to þe oþer server, plug it in þere, and copy it over. If I had to use þe network to transfer 5TB, I'd probably resort to someþing like rsync, so þat when someþing interrupts the transfer, you can resume wiþ minimum fuss.
Ok. Let’s go with it being ads. It’s a free open source project that’s absolutely worth using. Are you going to crucify them for it? Wanna donate for its development?
The number is the signal you send to the program. There's a lot of signals you can send (not just 15 and 9).
The difference between them is that 15 (called SIGTERM) tells the program to terminate by itself (so it can store its cached data, create a save without losing data or corrupting, drop all its open connections gracefully, etc). 9 (called SYGKILL) will forcefully kill a program, without waiting for it to properly close.
You normally should send signal 15 to a program, to tell it to stop. If the program is frozen and it's not responding or stopping, you then send signal 9 and forcefully kill it. No signal is "better" than the other, they just have different usecases.
Tmux is good because I can have a little window with a bonsai in it and another little window for the matrix. Sometimes I even leave a window for typing in commands.
Scrolling is tmux is what I hate about it. I would prefer to use tmux since I'm use to it. But if someone can explain to me why I can't just use my scroll wheel on my mouse.
To add to this one, it also supports more than just the previous command (which is what !! means), you can do like sudo !453 to run command 453 from your history, also supports relative like !-5. You can also use without sudo if you want which is handy to do things like !ls for the last ls command etc. Okay one more, you can add :p to the end to print the command before running it just in case like !systemctl:p which can be handy!
I routinely have to find a bunch of files that match a particular pattern and then do something with those files, and as a result, find with -exec is one of my top commands.
If you're someone who doesn't know wtf that above command does, here's a breakdown piece by piece:
find - cli tool to find files based on lots of different parameters
/path/to/starting/dir - the directory at which find will start looking for files recursively moving down the file tree
-type f - specifies I only want find to find files.
-regextype egrep - In this example I'm using regex to pattern match filenames, and this tells find what flavor of regex to use
-regex 'regex.here' - The regex to be used to pattern match against the filenames
I routinely have to find a bunch of files that match a particular pattern and then do something with those files, and as a result, find with -exec is one of my top commands.
If you're someone who doesn't know wtf that above command does, here's a breakdown piece by piece:
find - cli tool to find files based on lots of different parameters
/path/to/starting/dir - the directory at which find will start looking for files recursively moving down the file tree
-type f - specifies I only want find to find files.
-regextype egrep - In this example I'm using regex to pattern match filenames, and this tells find what flavor of regex to use
-regex 'regex.here' - The regex to be used to pattern match against the filenames
-exec - exec is a way to redirect output in bash and use that output as a parameter in the subsequent command.
mv {} /path/to/new/directory/ - mv is just an example, you can use almost any command here. The important bit is {}, which is the placeholder for the parameter coming from find, in this case, a full file path. So this would read when expanded, mv /full/path/of/file/that/matches/the/regex.file /path/to/new/directory/
\; - This terminates the command. The semi-colon is the actual termination, but it must be escaped so that the current shell doesn't see it and try to use it as a command separator.
fabien@debian2080ti:~$ history | sed 's/ ..... //' | sort | uniq -c | sort -n | tail
# with parameters
13 cd Prototypes/
14 adb disconnect; cd ~/Downloads/Shows/ ; adb connect videoprojector ;
14 cd ..
21 s # alias s='ssh shell -t "screen -raAD"'
36 node .
36 ./todo
42 vi index.js
42 vi todo # which I use as metadata or starting script in ~/Prototypes
44 ls
105 lr # alias lr="ls -lrth"
fabien@debian2080ti:~$ history | sed 's/ ..... //' | sed 's/ .*//' | sort | uniq -c | sort -n | tail
# without parameters
35 rm
36 node
36 ./todo
39 git
39 mv
70 ls
71 adb
96 cd
110 lr
118 vi
so if youre in a working dir and need to go work in a different dir, you can pushd ./, cd to the new dir and do your thing, then popd to go back to the old dir without typing in the path again
There are a lot of great commands in here, so here are my favorites that I haven't seen yet:
crontab -e
&& and || operators
">" and >> chevrons and input/output redirection
for loops, while/if/then/else
Basic scripts
Stdin vs stdout vs /dev/null
Need to push a file out to a couple dozen workstations and then install it?
for i in $(cat /tmp/wks.txt); do echo $i; rsync -azvP /tmp/file $i:/opt/dir/; ssh -qo Connect timeout=5 $i "touch /dev/pee/pee"; done
Or script it using if else statements where you pull info from remote machines to see if an update is needed and then push the update if it's out of date. And if it's in a script file then you don't have search through days of old history commands to find that one function.
Or just throw that script into crontab and automate it entirely.
The watch command is very useful, for those who don't know, it starts an automated loop with a default of two seconds and executes whatever commands you place after it.
It allows you to actively monitor systems without having to manually re-run your command.
So for instance, if you wanted to see all storage block devices and monitor what a new storage device shows up as when you plug it in, you could do:
watch lsblk
And see in real time the drive mount. Technically not "real time" because the default refresh is 2 seconds, but you can specify shorter or longer intervals.
Obviously my example is kind of silly, but you can combine this with other commands or even whole bash scripts to do some cool stuff.
Yeah, it's a neat little tool. I used it recently at my work. We had a big list of endpoints that we needed to make sure were powered down each night for a week during a patching window.
A sysadmin on my team wrote a script that pinged all of the endpoints in the list and returned only the ones that still were getting a response, that way we could see how many were still powered on after a certain time. But he was just manually running the script every few minutes in his terminal.
I suggested using the watch command to execute the script, and then piping the output into the sort command so the endpoints were nicely alphabetical. Worked like a charm!
i do not know if this counts as a command but you might want to check Atuin, what it does is help you find, manage and edit the commands you used in your shell history saves you a lot of time
pkilljournalctl -bnvtoptail are great but I like: LANGUAGE=en_GB LC_ALL=en_GB.UTF-8 LANG=en_GB.UTF-8 <your GUI program> to run a GUI program in English for more universal compatibility for helping newbies and creating/reading non-terminal based documentation
atuin.sh/ does one better. history with context: $PWD, $HOST, time. There's a bunch of other bells and whistles, but they're easy to ignore to get an noninvasive upgrade to ctrl+R
A couple I use (concept of not exact), that I haven't seen in the thread yet:
Using grep as diff: grep -Fxnvf orig.file copy.file
Using xargs -
xargs reads items from the standard input, delimited by blanks (which can be protected with double or single quotes or a backslash) or newlines, and executes the command (default is /bin/echo) one or more times with any initial-arguments followed by items read from standard input.
EG: $ find ~/Pictures -name "*.png" -type f -print0 | xargs -0 tar -cvzf images.tar.gz
As I understand it, the issue is that tmux invents its own terminal emulator functionality that conflicts with the existing terminal it runs within, while screen simply defers scroll functionality to the terminal emulator.
redshift -O 5000: 'redshift' is a utility that adjusts the color temperature of your display, '-O' allows you to set a specific temperature, and '5000' is what I like.
Edit: I also like xkill. xkill lets you click on a window or program and kills it. I need to do this frequently every time exit Kodi; the program stops, but the window is still there.
I think vipe is underrated; it takes whatever is on its stdin, shoves it in a temp file, opens your favorite text editor (EDITOR environment variable) and waits in the background until you finish editing the file and close it. Then it outputs the edited text to its stdout.
It's useful in all kinds of pipes, but personally I use it tons of times a day in combination with xclip, in something like this:
(I actually have a bit fancier version of this pipe wrapped in a Bash function named xvxx.)
On my setup, this takes my current text selection, opens it in vim, and lets me edit it before it sends it to the "traditional" Ctrl+C clipboard. It's super handy for editing comments like this one.
If you often find yourself writing complex Bash pipelines involving generating some output and then running set of commands per line (perhaps in a while loop), sometimes replacing the "selection part" wi
... show more
I think vipe is underrated; it takes whatever is on its stdin, shoves it in a temp file, opens your favorite text editor (EDITOR environment variable) and waits in the background until you finish editing the file and close it. Then it outputs the edited text to its stdout.
It's useful in all kinds of pipes, but personally I use it tons of times a day in combination with xclip, in something like this:
(I actually have a bit fancier version of this pipe wrapped in a Bash function named xvxx.)
On my setup, this takes my current text selection, opens it in vim, and lets me edit it before it sends it to the "traditional" Ctrl+C clipboard. It's super handy for editing comments like this one.
If you often find yourself writing complex Bash pipelines involving generating some output and then running set of commands per line (perhaps in a while loop), sometimes replacing the "selection part" with vipe can be easier than coming up with right filter.
find_or_ls_or_grep_something | vipe | for while read -r foo; do some_action "$foo"; done
And if you are really confident with Bash, you can go even a step further and do:
you might find something like this useful sometimes:
find_or_ls_or_grep_something | vipe | bash
and just create a large dumb one-off script, manually curating what's exactly done. Remember that editing large lists in vim can be made much easier by utilizing vim's ability to invoke unix filter commands (those greps and uniqs and seds et al.) on the buffer, and /or block editing mode using Ctrl+V (that last one method goes really well with column -t).
Hah I am glad it was helpful! Glad to share, I always felt like half the point of learning is to share what you learned. That is one of my favorite “hidden gems” for lack of a better term that can be a real time saver.
Bonus just for more fun: you can use cd - to switch back to the directory you were last in after changing directories, it toggles the top two paths in the stack. It is similar to how pushd/popd work if you have you used those. I use that one a ton, there are fancier tools now but that one works everywhere.
Oh also, anyone on a Mac needs to know about pbcopy, Linux has xclip and I don’t remember what the Wayland analog is.
This is generally my view on Android handhelds but for some reason N64 emulation simply refuses to work on my Fairphone 6 so I've ordered a Mangmi instead.
Annoncé en grandes pompes jeudi 11 décembre lors du temps fort associatif d'Open Source Experience, Projets Libres devient le podcast de LinuxFr.org. Depuis avril 2023, le podcast Projets Libres vous apporte un éclairage sur les projets, communautés et le
Annoncé en grandes pompes jeudi 11 décembre lors du temps fort associatif d’Open Source Experience, Projets Libres devient le podcast de LinuxFr.org. Depuis avril 2023, le podcast Projets Libres vous apporte un éclairage sur les projets, communautés et les individus qui composent l’écosystème libre et open source. Les épisodes sont régulièrement promus sur LinuxFr. Tout en conservant son nom d’origine, il s’intègre désormais à la galaxie du site LinuxFr pour proposer, en plus des dépêches, journaux, liens… un format audio régulier consacré au logiciel libre, à ses actrices et acteurs et à ses projets. Ce rapprochement ne changera pas la ligne éditoriale d
... show more
Annoncé en grandes pompes jeudi 11 décembre lors du temps fort associatif d’Open Source Experience, Projets Libres devient le podcast de LinuxFr.org. Depuis avril 2023, le podcast Projets Libres vous apporte un éclairage sur les projets, communautés et les individus qui composent l’écosystème libre et open source. Les épisodes sont régulièrement promus sur LinuxFr. Tout en conservant son nom d’origine, il s’intègre désormais à la galaxie du site LinuxFr pour proposer, en plus des dépêches, journaux, liens… un format audio régulier consacré au logiciel libre, à ses actrices et acteurs et à ses projets. Ce rapprochement ne changera pas la ligne éditoriale du podcast, mais inscrit ce travail dans le temps long. À court terme, il inclut un nouveau logo et générique pour le podcast, et un lien d’accès au podcast depuis LinuxFr.org.
LinuxFr.org, de son côté, n’a plus vraiment besoin d’être présenté ici : le site communautaire francophone consacré au libre depuis 1998 regroupe dépêches, journaux, liens, forums, sondages, tribunes et autres contenus publiés par la communauté. L’arrivée d’un format audio s’inscrit donc comme une évolution naturelle pour enrichir encore les contenus mis en avant. Mais si vous voulez en savoir plus sur LinuxFr.org, sachez que nous avons eu droit à notre épisode dédié il y a deux ans et que nous vous invitons à l’écouter !
Le podcast a connu une accélération en 2025, et le besoin d’avoir une entité légale s’est fait sentir. L’idée étant de récolter des fonds pour financer notre travail, mais aussi de préciser le but non lucratif et les motivations de l’équipe. Plutôt que de créer une n-ième association dont il allait falloir s’occuper, au détriment du temps passé à la réalisation de podcasts.
De plus, nous pressentons clairement que les deux communautés se recoupent et aiment découvrir des projets libres en écoutant des retours d’expérience, des interviews ou des discussions techniques… et LinuxFr.org dispose justement d’une communauté intéressée par ce type de contenus. Le rapprochement permettra :
d’augmenter la visibilité des épisodes existants et futurs ;
de favoriser des synergies entre la rédaction des dépêches et la production audio (interviews associées à une dépêche, compléments audio d’articles, discussions prolongées, etc.) ;
de proposer un point d’entrée unique vers le contenu éditorial écrit et audio du site.
Pas d’inquiétude : le podcast garde sa ligne éditoriale, son nom et son style.
Concrètement, ça va se passer comment ?
Un nouveau générique et un nouveau logo vont très vite faire leur apparition, mais pour le reste, pas grand-chose ne change pour les personnes qui écoutent déjà Projets Libres :
les épisodes restent disponibles sur le site historique du podcast ;
le flux RSS existant continue de fonctionner dans vos lecteurs de podcast habituels ;
les archives restent accessibles.
Côté LinuxFr.org,
Un lien dans l’en-tête va apparaître aux côtés des Dépêches, Journaux, Liens, Forum, etc.
Chaque nouvel épisode fera l’objet d’une dépêche un peu plus étoffée permettant de continuer la discussion
La création d’une liste de diffusion dédiée
Le tout reste sous licence libre ou ouverte, dans la continuité de ce que pratiquaient déjà LinuxFr.org et le podcast.
Et pour la suite ?
Nous allons travailler à une intégration plus poussée, mais elle reste encore à imaginer. Et comme tout ce qui touche à LinuxFr.org, ce rapprochement se veut avant tout communautaire. Vous avez une idée de sujet ? Vous maintenez un projet libre et souhaitez en parler au micro ? Vous aimeriez participer à un enregistrement, proposer une chronique, ou simplement donner votre avis ? N’hésitez pas à le signaler dans les commentaires, ou à contacter l’équipe du podcast.
Bonne écoute, et à bientôt pour un nouvel épisode ! 🎙️
Walid : Chères auditrices, chers auditeurs, bienvenue sur cet épisode un peu particulier qui a été enregistré en direct lors du salon Open Source Experience à Paris le jeudi 18 décembre 2025 lors de la conférence nommée l’associal Club, qui est la conférence communautaire organisée par LinuxFr.org. Je vous laisse avec ce court extrait qui parle de l’avenir du podcast Projets Libres. Bonne écoute. OSXP 2025 – L’associal Club, animé par Florent Zara (crédits : William Jezequel) Florent : Et donc, breaking news, LinuxFr.org se met au podcast, pour ceux qui ne le sauraient pas ! Donc LinuxFr, site web collaboratif d’informations, d’actualités sur le logiciel libre en mode contributif, sous licence libre. Donc n’hésitez pas à venir contribuer, mais on s’est dit voilà, on va faire de l’audio, parce qu’il faut se diversifier un peu, il faut se renouveler. Alors, pourquoi, où, quand, comment ? On va essayer de répondre à ces questions-là.
On va commencer par le comment. Alors, on a regardé, on a fait un petit benchmark. On s’est dit, est-ce qu’on fait nous-mêmes ? Est-ce qu’on regarde ce qui existe ? Qui sont les bons ? Qui sont les moins bons ? Et donc, on s’est dit : « fusion, acquisition, FUSAC ! ». On va lancer une grosse FUSAC. On s’est dit, et on a fait une offre, vous ne pouvez pas résister.
Et donc là, on a dit : « le meilleur, c’est Projets Libres ». Désolé pour Libre à vous mais les meilleurs c’est Projets Libres. Donc Projets Libres et LinuxFr.org s’associent pour proposer maintenant des podcasts. Et donc Projet Libre devient le podcast officiel de LinuxFr.org ! Ce que je vous propose c’est de prendre 5 bonnes minutes 5-10 minutes pour faire une petite interview croisée du président de LinuxFr Benoît Sibaud et sur le porteur du podcast Projets Libres, Walid Nouh.
Mettez vous là, prenez chacun un micro. Je vais te donner le micro il y en a que deux, c’est pas grave je vais vous poser deux petites questions on va pas faire trop long parce qu’il y a le quizz derrière.
Pourquoi le rapprochement ?
Florent : Déjà la petite question Benoît pourquoi ? Et aussi pourquoi en deux minutes chacun.
Benoît : C’est facile : vous avez remarqué on est une association de bénévoles et grâce à notre super trésorier et notre sens inné de comment on génère de la thune, on est capable d’avoir plein de sponsors qui offrent plein de trucs et d’exister depuis 1998.
On s’est dit : « ouais, OK, on a un site web en ligne, on est capable de faire du texte, on est capable d’avoir des images. Ça se trouve, on peut rentrer dans le nouveau millénaire et se lancer dans l’audio, un truc novateur, et poursuivre notre conquête du monde francophone ». Là, l’idée était née. On s’est dit : « ouais, c’est ça qu’il faut faire. La fusion acquisition, c’est l’avenir. Et plus rien ne nous arrêtera maintenant, on est parti, on est à fond ». Benoît Sibaud, président de l’association LinuxFR.org et Walid Nouh, créateur du podcast Projets Libres (crédits : William Jezequel) Walid : Tu vends ça bien quand même (rire). Du côté LinuxFr… c’est déjà parti… Du côté Projets Libres, c’est beaucoup plus simple. Ça fait deux ans et demi que le podcast existe. Et on commençait à avoir des questions de « Ok, vous êtes qui ? » « C’est quoi ? » « Comment ça marche ? » Donc on s’était dit, avec Raphaël, on bosse ensemble tous les deux sur le podcast, on va monter une association, une énième association du libre.
L’idée aussi derrière, c’était d’une manière ou d’une autre d’arriver à avoir des dons et à pouvoir faire un peu perdurer le podcast qui a commencé il y a deux ans et demi. Et de manière totalement fortuite, dans une discussion, qui n’était pas encore de fusion-acquisition, avec le Florent ici présent, on a évoqué l’idée qu’on voulait monter une asso et il nous a dit « en fait pourquoi vous voulez monter une asso ? On en a une, elle est là ».
Et donc je fais un petit coucou à une personne qui s’appelle Nÿco alias Nicolas Vérité que j’ai rencontré sur des spots de roller il y a 20 ans et qui m’a donné mes premiers CD Linux Mandrake, qui faisait déjà partie de LinuxFr à l’époque je pense et donc quelque part c’est grâce à lui qu’on est là donc voilà un peu pourquoi on est là.
Benoît : Et comme ils font un super boulot et que leurs podcasts sont vraiment super bravo pour tout le boulot qui a été abattu bienvenue dans la famille.
A quoi s’attendre maintenant ?
Florent : Et alors deuxième question rapide avant de continuer comment est-ce que ça va se faire concrètement À quoi s’attendre ?
Walid : Doit-on répondre à cette question ? Non, concrètement, dans les heures, jours qui viennent, on va mettre un premier logo un peu plus représentatif du rapprochement et ensuite, on va réfléchir à la manière dont on croise les contenus puisque déjà, LinuxFr est une de nos sources principales quand on prépare les podcasts. Donc là, l’idée, dans les mois qui viennent, ça va être de réfléchir à la manière dont on intègre plus finement le podcast à travers LinuxFr c’est pas encore complètement défini
Benoît : Globalement on va améliorer la partie affichage, visibilité de manière croisée donner des liens les uns sur les autres avoir des logos qui représentent ça. Et puis on part pas de zéro on relaie déjà les podcasts on relaie de manière générale les transcriptions qu’il peut y avoir sur les podcasts on a déjà de l’actualité dessus l’idée c’est d’aller un cran plus loin de faciliter cette partie multimédia, d’avoir le texte, l’audio tout disponible, qu’on puisse le trouver par le même moyen et de rendre ça beaucoup plus facile.
C’est vrai pour l’accès au contenu, c’est vrai pour faciliter la vie du podcast c’est vrai au niveau de l’association là c’est pratique de pouvoir gérer, pas avoir besoin de créer une asso séparée, c’est déjà une aide, ça permet de lancer des projets et de faire des choses plus facilement et c’est aussi vrai en termes d’idées de capacités à s’entraider et à produire des choses en croisé, on a du texte et un historique sur plein d’années.
Walid : Et une communauté.
Benoît : Les podcasts, c’est super intéressant comme moyen de communication. On a plein de contenus qu’on peut valoriser de cette manière-là. On a des tas de manières de travailler ensemble et il n’y a plus qu’à.
Walid : Juste pour terminer, la communauté, c’est quelque chose d’important. Ce qu’il faut comprendre, c’est que les podcasts, tel qu’on les fait, c’est-à-dire avec un enregistrement à distance, on en parle beaucoup avec Raphaël, mais ça reste un travail qui est très, comment dire, très solitaire.
Et là, l’idée, c’est de pouvoir bénéficier aussi de tout le système de rédaction, des news qui sont écrites de manière collaborative, pour essayer d’enrichir le podcast, de trouver des idées, voire même de faire des news à travers de l’audio qu’on aurait fait. Donc voilà, il y a plein de choses différentes qu’on va pouvoir faire. Donc on est super contents. Et puis pour ceux qui ne connaissent pas le podcast, je ne sais pas s’il y a déjà des gens qui écoutent le podcast ici. Oui, on peut…
Florent : Et dernière question mon cher Walid au niveau habillage sonore tu vas faire quelque chose de précis ou pas ?
Walid : Alors on va refaire l’habillage sonore qui date d’il y a deux ans et demi, donc il a besoin d’être refait et l’habillage sonore va être a priori très certainement la chanson que vous venez d’entendre de KPTN. Clément Oudot, alias KPTN (crédits William Jezequel) Florent : Voilà, le pouvoir du libre et des licences libres.
Walid : et on peut faire des dons dès maintenant sur EnVenteLibre.org pour le podcast
Florent : en attendant, il faut quand même un contrat ça rigole pas là…
Walid : on a signé un accord de non-divulgation avant au départ
Florent : y’a quand même fusion acquisition
Benoît : on a confiance dans le trésorier
Florent : le trésorier t’offre [des pièces de monnaie en chocolat]…
DÉCOUVREZ LE LOGICIEL LIBRE ET L’OPEN SOURCE !
Écoutez les retours d’expériences des acteurs du libre et de l’open source : comment financer un projet open source ?
Comment concilier liberté d’usage et viabilité économique ?
Comment organiser son pro…
Annoncé en grandes pompes jeudi 11 décembre lors du temps fort associatif d’Open Source Experience, Projets Libres devient le podcast de LinuxFr.org. Depuis avril 2023, le podcast Projets Libres vous apporte un éclairage sur les projets, communautés et les individus qui composent l’écosystème libre et open source. Les épisodes sont régulièrement promus sur LinuxFr. Tout en conservant son nom d’origine, il s’intègre désormais à la galaxie du site LinuxFr pour proposer, en plus des dépêches, journaux, liens… un format audio régulier consacré au logiciel libre, à ses actrices et acteurs et à ses projets. Ce rapprochement ne changera pas la ligne éditoriale du podcast, mais inscrit ce travail dans le temps long. À court terme, il inclut un nouveau logo et générique pour le podcast, et un lien d’accès au podcast depuis LinuxFr.org.
LinuxFr.org, de son côté, n’a plus vraiment besoin d’être présenté ici : le site communautaire francophone consacré au libre depuis 1998 regroupe dépêches, journaux, liens, forums, sondages, tribunes et autres contenus publiés par la communauté. L’arrivée d’un format audio s’inscrit donc comme une évolution naturelle pour enrichir encore les contenus mis en avant. Mais si vous voulez en savoir plus sur LinuxFr.org, sachez que nous avons eu droit à notre épisode dédié il y a deux ans et que nous vous invitons à l’écouter !
Le podcast a connu une accélération en 2025, et le besoin d’avoir une entité légale s’est fait sentir. L’idée étant de récolter des fonds pour financer notre travail, mais aussi de préciser le but non lucratif et les motivations de l’équipe. Plutôt que de créer une n-ième association dont il allait falloir s’occuper, au détriment du temps passé à la réalisation de podcasts.
De plus, nous pressentons clairement que les deux communautés se recoupent et aiment découvrir des projets libres en écoutant des retours d’expérience, des interviews ou des discussions techniques… et LinuxFr.org dispose justement d’une communauté intéressée par ce type de contenus. Le rapprochement permettra :
d’augmenter la visibilité des épisodes existants et futurs ;
de favoriser des synergies entre la rédaction des dépêches et la production audio (interviews associées à une dépêche, compléments audio d’articles, discussions prolongées, etc.) ;
de proposer un point d’entrée unique vers le contenu éditorial écrit et audio du site.
Pas d’inquiétude : le podcast garde sa ligne éditoriale, son nom et son style.
Concrètement, ça va se passer comment ?
Un nouveau générique et un nouveau logo vont très vite faire leur apparition, mais pour le reste, pas grand-chose ne change pour les personnes qui écoutent déjà Projets Libres :
les épisodes restent disponibles sur le site historique du podcast ;
le flux RSS existant continue de fonctionner dans vos lecteurs de podcast habituels ;
les archives restent accessibles.
Côté LinuxFr.org,
Un lien dans l’en-tête va apparaître aux côtés des Dépêches, Journaux, Liens, Forum, etc.
Chaque nouvel épisode fera l’objet d’une dépêche un peu plus étoffée permettant de continuer la discussion
La création d’une liste de diffusion dédiée
Le tout reste sous licence libre ou ouverte, dans la continuité de ce que pratiquaient déjà LinuxFr.org et le podcast.
Et pour la suite ?
Nous allons travailler à une intégration plus poussée, mais elle reste encore à imaginer. Et comme tout ce qui touche à LinuxFr.org, ce rapprochement se veut avant tout communautaire. Vous avez une idée de sujet ? Vous maintenez un projet libre et souhaitez en parler au micro ? Vous aimeriez participer à un enregistrement, proposer une chronique, ou simplement donner votre avis ? N’hésitez pas à le signaler dans les commentaires, ou à contacter l’équipe du podcast.
Bonne écoute, et à bientôt pour un nouvel épisode ! 🎙️
Russia has officialy signed Reciprocal Exchange of Logistics Agreement (RELOS) with India, which gives both countries access to their bases and facilities for logistical support and even deployment.
If you want to know about it in detail and its implications and my point of view, visit my main comunity "BharatDefense" where I have uploaded about this in detail. and discussed everything
Russia has officialy signed Reciprocal Exchange of Logistics Agreement (RELOS) with India, which gives both countries access to their bases and facilities for logistical support and even deployment.
If you want to know about it in detail and its implications and my point of view, visit my main comunity "BharatDefense" where I have uploaded about this in detail. and discussed everything
Putin Signs Law Ratifying Reciprocal Exchange of Logistics Agreement (RELOS) With India
Recently, as a landmark decision, Vladmir Putin Signed the Reciprocal Exchange of Logistics Agreement (RELOS) with India, ratifying it legally and enhancing bilateral military cooperation with India.
The agreement is now included legally in Russia's legal acts website, and it establishes clear procedures for deployments of soldiers, warships and aircrafts in each other's respective regions.
India for long has depended substantially on Russian Military Hardware and this agreement paves way for smoother logistical support during joint exercises and operations and enhances rapid response capabilities.
According to RELOS, Russian Warships could berth at Indian Ports for supplies while Indian Airforce aircrafts gain reciprocal access to Russian facilities.This reciprocity extends to army units, enabling seamless sustainment of operations without the need for ad-hoc permissions, a boon for interoperability in multinational scenarios.
There is also another deeper angle to it regarding why both countries made this agreement. India since a long time wanted to enhance its presence in the South-China sea and North Pole, not only that India also wanted to reduce the rising US influence in Indian Ocean and Russia on the other hand wanted to expand its influence to Indian Ocean, due to these coinciding interests, both nations agreed on this RELOS agreement.
I think in context of both the nations as through this, both the nations will be able to counter their respective rivals.
What do you think about this agreement, do let me know in the comments.
If you like this content join "BharatDefense" to support us.
Nearly two months into the cease-fire between Israel and Hamas, Israel continues to bar journalists from freely entering the Gaza Strip to report, despite a longstanding petition brought by journalists seeking access to the territory.
On Sunday, the Israeli Supreme Court gave the government an extension in responding to the petition, the ninth such delay since the case was filed in September 2024.
The Israeli government, which has yet to fully explain why it continues to bar journalists, is slated now to give its latest response on Dec. 21, according to court filings, a delay that could be extended further.
I think this compartmentalization doesn't go far enough.
I think every post should be posted in its own unique community containing only that single one post.
That way everything would be perfectly divided and nothing would ever go into the wrong sub, and online forums would no longer consist of 50% whining about whether something is a perfect fit.
I do generally enjoy political memes, but the constant Trump Trump Trump of both news comms and meme comms can get a bit much. For obvious reasons, but sometimes you just want to take a break y'know? This is why I generally don't sub to these types of comms, I just have them open in separate tabs when I want to torture myself a bit.
Knob cheese, aka smegma is one of the reasons that some scientists recommend male circumcision (genital mutilation). There are political groups both for and against male circumcision, some of which have scientific and in other cases religious affiliations.
Along the recent medical history there is an ubiquitous myth surrounding smegma; its nature, composition, its beneficial role or deleterious effects either in health or in diseases.
Nice try, but just because there are political groups that support one side or another does not, alone, make knob cheese a political topic. Unless, knob cheese is the primary focus of said political groups.
sometimes they aren't even memes, this morning was just some dingdong posting about American president approval ratings in shitposts. WE POSTED CORN ABOUT THIS
Isaac Nellist argues that Labor’s refusal to tackle the growing divide between the haves and have-nots has paved the way for One Nation’s popularist non-solutions to the cost-of-living and housing crises.
Isaac Nellist argues that Labor's refusal to tackle the growing divide between the haves and have-nots has paved the way for One Nation's popularist non-solutions to the cost-of-living and housing crises.
I thought it was an interesting addition to Where Winds Meet to make the NPCs seem dynamic. It didn't change my opinion of AI nor would I call it a selling point, but it was interesting.
Through the key points outlined in this guide—from material selection to channel choices, from reputation research to maintenance planning—you are fully capable of finding the ideal torso sex doll that meets your emotional and physical needs without causing financial strain.
"Less is more"—this saying holds true in the world of sex toys too.
Read more...
People use sex dolls for different reasons: some seek companionship, while others have a particular fondness for specific body parts.
The Carney government is making good on a promise to help tackle one of the most potent forms of climate pollution, as it announces new measures to address methane emissions from the oil and gas industry.
CBC News obtained an early copy of the announcement that Environment, Climate Change and Nature Minister Julie Dabrusin is expected to deliver in Metro Vancouver Tuesday afternoon.
It contains significant emission reductions but offers more leeway to oil and gas producers to comply after many complained the original proposal was too strict. It also addresses methane released by landfills, which are responsible for a smaller portion of emissions.
"Canada is seriously concerned by the Chinese Coast Guard aggressive actions against Filipino civilian fishing vessels near Sabina Shoal," Canada's ambassador to the Philippines, David Hartman, posted on social media.
"These actions jeopardize regional peace and stability. Disputes must be resolved peacefully and in accordance with international law.”
Canada joins Western allies like the EU, Germany, Australia, Japan, and others condemning China's actions.
The Philippine Coast Guard [PCG] earlier said about 20 Filipino fishing boats were targeted on December 12 while engaged in lawful fishing activities. Chinese Coast Guard and maritime militia vessels used water cannons and dangerous blocking maneuvers, injuring at least three fishermen and causing significant damage to two boats, the PCG said.
The Philippine coast guard vessels it deployed to aid the injured fishermen were also blocked repeatedly from reaching Escoda Shoal, the Philippines says.
The Philippine Coast Guard says nearly two dozen Filipino fishing boats near Escoda Shoal were targeted with water cannon and blocking maneuvers on December 12
Cyborganism
in reply to geneva_convenience • • •eldavi
in reply to geneva_convenience • • •