Grande-Marlaska said migrants who entered irregularly would not be allowed to stay in the territory, travel to mainland Spain or obtain legal status, except in rare cases involving extreme vulnerability. Those without a right to remain would be returned to Morocco, he added.
Earlier this week, Rabat said it was monitoring “the circulation of social media posts and messages of unknown origin” calling for a mass crossing on 15 August, warning it would prosecute organisers and participants.
A Reuters witness saw reinforced security near the border, including police vans with wire shields and road checkpoints. Local media reported similar measures near Melilla, another Spanish territory in north Africa.
If you’re wondering why I’m crossposting .ml content or for an account listing of accounts used for it, please see the bottom of this megathread
- 77 posts
- 2 comments
What do you think it’ll happen and what do you want to happen?
Debian developers have been considering a general resolution over LLM usage within the project. After collecting a variety of proposals, voting has now commenced for Debian developers to decide how comfortable they are with AI / Large Language Model contributions in the project or not.
The choices being considered for this Debian general resolution (GR) include:
[ ] Choice 1: Ban LLM contributions from Debian via Social Contract
[ ] Choice 2: Allow AI-Assisted Contributions with conditions
[ ] Choice 3: Reject LLMs as far as practical, update Code of Conduct
[ ] Choice 4: Accept AI contributions for Debian specific work
[ ] Choice 5: Responsible Use of Generative AI
[ ] Choice 6: A cautious approach to generative AI
[ ] Choice 7: Debian is created by humans
[ ] Choice 8: Avoid the use of LLM: climate destruction is a deal breaker
[ ] Choice 9: None of the above
All the details on each of those choices can be found via the Debian.org vote page.
Additional details in this mailing list post with the voting details on the general resolution. The voting period began at midnight and is set to run through end of day 28 August.
I guess Goish might be hated by many Rust fans and Go fans. Anyway, below is the example taken from its website.
use goish::{go, KB}; use goish::sync::WaitGroup; #[goish::main] fn main() { let wg = &WaitGroup::new(); wg.Add(1_000_000); for i in 0..1_000_000 { // Explicit 2 KiB stack, sub-page allocated from the >chunked // stackpool - the opt-in for extreme spawn density. >Everyday // code just writes go!(move || ...) and never sizes a >stack. go!(stack(2 * KB), move || { do_work(i); wg.Done(); }); } wg.Wait(); }
I guess Goish might be hated by many Rust fans and Go fans. Anyway, below is the example taken from its website.
use goish::{go, KB}; use goish::sync::WaitGroup; #[goish::main] fn main() { let wg = &WaitGroup::new(); wg.Add(1_000_000); for i in 0..1_000_000 { // Explicit 2 KiB stack, sub-page allocated from the >chunked // stackpool - the opt-in for extreme spawn density. >Everyday // code just writes go!(move || ...) and never sizes a >stack. go!(stack(2 * KB), move || { do_work(i); wg.Done(); }); } wg.Wait(); }
Concerning





















Thanks! Updated