0

Why Fast-Tracking Your Sleeping-Emperor Portfolio Leads to Catastrophic Realm Restructuring

LinkedIn Why Fast-Tracking Your Sleeping-Emperor Portfolio Leads to Catastrophic Realm Restructuring https://lnkd.in/gBZ4Ff34 In Q3 1631, facing a grueling 13-year operational drag during the Thirty Years’… | RPGnet www.linkedin.com
preview

I would like to point out that I only wrote the initial RPGNet post and did not create this summary, so I am only partially to blame.

I would like to point out that I only wrote the initial RPGNet post and did not create this summary, so I am only partially to blame.

0

Latino voters swing left in midterm elections, lifting Democrats to big wins in Texas and nationwide

preview

It’s a change for a demographic that had been leaning right for nearly a decade.

It’s a change for a demographic that had been leaning right for nearly a decade.

0

18 USD HALF-BODY Custom Anime Character Illustration | Anime Style

preview

💸MOP: Paypal, VGen, LiberaPay and Kofi ⏰TAT: 2-3 weeks (depends on the details) 📖Portfolio: luzeed.org/i/portfolio/astra.menae or vgen.co/astra_menae/portfolio

Includes -Cel shaded character illustration. HALF BODY. With solid color background. -Version without background (clean character) -Solid white background version -Transparent PNG version (character only)

Details -High-resolution files (PNG - RGB format) -Digital use only (social media, avatars, wallpapers, streaming, etc.)

Add-ons -Detailed Scene Background — +50% -Extra Characters — +100% per character -NSFW Version — +50% -Commercial Use — +100% / Merch +150%

Revisions & Workflow -3 Revisions included (Sketch, Lineart/Flat Color, and Final Product) for minor fixes and small adjustments. -Up to 2 major changes allowed (pose, scene composition, etc.), permitted only during the Sketch and Lineart stages.

Important -Visual references or character sheets are required. -Personal use by default unless Commercial Use add-on is purchased. -Armor / Cybernetic parts: Allowed (simple designs). -100% Full Mecha / Robots: Not accepted.

💸MOP: Paypal, VGen, LiberaPay and Kofi ⏰TAT: 2-3 weeks (depends on the details) 📖Portfolio: luzeed.org/i/portfolio/astra.menae or vgen.co/astra_menae/portfolio

Includes -Cel shaded character illustration. HALF BODY. With solid color background. -Version without background (clean character) -Solid white background version -Transparent PNG version (character only)

Details -High-resolution files (PNG - RGB format) -Digital use only (social media, avatars, wallpapers, streaming, etc.)

Add-ons -Detailed Scene Background — +50% -Extra Characters — +100% per character -NSFW Version — +50% -Commercial Use — +100% / Merch +150%

Revisions & Workflow -3 Revisions included (Sketch, Lineart/Flat Color, and Final Product) for minor fixes and small adjustments. -Up to 2 major changes allowed (pose, scene composition, etc.), permitted only during the Sketch and Lineart stages.

Important -Visual references or character sheets are required. -Personal use by default unless Commercial Use add-on is purchased. -Armor / Cybernetic parts: Allowed (simple designs). -100% Full Mecha / Robots: Not accepted.

0

1000 Distro servono davvero all'utente base?

preview

1000 Distro servono davvero all’utente base?
Sicuri che #Linux sia così complicato?

Oggi rispondiamo a un po’ di domande che mi vengono fatte spesso, ma che non sempre affrontiamo. Trovate tutto nel mio ultimo video🔽
https://youtu.be/i2n7UyGOC4g

@lealternative

1000 Distro servono davvero all’utente base?
Sicuri che #Linux sia così complicato?

Oggi rispondiamo a un po’ di domande che mi vengono fatte spesso, ma che non sempre affrontiamo. Trovate tutto nel mio ultimo video🔽
https://youtu.be/i2n7UyGOC4g

@lealternative

0

Wizards of the Lost Kingdom (1985) - Mastodon watch party this Sunday evening!

A movie poster of Wizards of the Lost Kingdom
preview

In the peaceful kingdom of Axeholme lives the teenage boy Simon, son of Wulfrik, the king’s court wizard. The evil sorcerer Shurka starts a coup d’état, aided by the King’s wife, killing the king, and imprisoning the princess, Aura. Before he is slain by Shurka, Wulfrik teleports Simon and his friend Gulfax to safety and gifts him his powerful magic ring. However, unbeknownst to all, Simon loses the ring during his escape.

…

The film re-used a large amount of stock footage from Sorceress (1982) and Deathstalker (1983). Ed Naha, who wrote the script, later recalled:

I don’t think this movie was so much shot as it was beaten to death. When they whittled it down to what was useful from the footage, it only ran 58 minutes. Now [producer] Roger [Corman] had done a lot of sword-and-sorcery films, and so he told a couple of the editors to pull all they could from them and edit that footage in. So now the finished movie has a 15 or 20-minute prologue that has nothing to do with rest of the film!

en.wikipedia.org/…/Wizards_of_the_Lost_Kingdom

3.0 out of 10 on imdb! 21% on rottentomatoes! And yet, Wizards of the Lost Kingdom (1985) is the movie for this Sunday’s “monsterdon” watch party over on Mastodon, our fediverse sibling!

  • Just start watching that movie this Sunday, November 8 at 9pm ET / 8pm CT / 6pm PT which is 1am Monday UTC
  • and follow #monsterdon over on mastodon for live text commentary. For example, you can follow that hashtag here: mastodon.social/tags/monsterdon
  • I usually open two web browser windows side-by-side on a computer. But you could follow the mastodon commentary on a phone app while watching the movie on TV or something.

How to watch the movie:

In the peaceful kingdom of Axeholme lives the teenage boy Simon, son of Wulfrik, the king’s court wizard. The evil sorcerer Shurka starts a coup d’état, aided by the King’s wife, killing the king, and imprisoning the princess, Aura. Before he is slain by Shurka, Wulfrik teleports Simon and his friend Gulfax to safety and gifts him his powerful magic ring. However, unbeknownst to all, Simon loses the ring during his escape.

…

The film re-used a large amount of stock footage from Sorceress (1982) and Deathstalker (1983). Ed Naha, who wrote the script, later recalled:

I don’t think this movie was so much shot as it was beaten to death. When they whittled it down to what was useful from the footage, it only ran 58 minutes. Now [producer] Roger [Corman] had done a lot of sword-and-sorcery films, and so he told a couple of the editors to pull all they could from them and edit that footage in. So now the finished movie has a 15 or 20-minute prologue that has nothing to do with rest of the film!

en.wikipedia.org/…/Wizards_of_the_Lost_Kingdom

3.0 out of 10 on imdb! 21% on rottentomatoes! And yet, Wizards of the Lost Kingdom (1985) is the movie for this Sunday’s “monsterdon” watch party over on Mastodon, our fediverse sibling!

  • Just start watching that movie this Sunday, November 8 at 9pm ET / 8pm CT / 6pm PT which is 1am Monday UTC
  • and follow #monsterdon over on mastodon for live text commentary. For example, you can follow that hashtag here: mastodon.social/tags/monsterdon
  • I usually open two web browser windows side-by-side on a computer. But you could follow the mastodon commentary on a phone app while watching the movie on TV or something.

How to watch the movie:

0

Playing PC games on Android phones

GitHub GitHub - Droid-Deck/DroidDeck: DroidDeck brings the SteamOS experience to Android github.com
preview

I came across this on heise.de: it’s an app that lets you play games from Steam, Gog, Epic and elsewhere on many Android phones (Pixels excepted, apparently). I’ve tried a few that run fine and others that do not, but I think the idea is amazing, especially for older, less demanding games. I’m finding the controls the biggest challenge, but I’m sure this can be tweaked.

I came across this on heise.de: it’s an app that lets you play games from Steam, Gog, Epic and elsewhere on many Android phones (Pixels excepted, apparently). I’ve tried a few that run fine and others that do not, but I think the idea is amazing, especially for older, less demanding games. I’m finding the controls the biggest challenge, but I’m sure this can be tweaked.

0

llama.cpp v0.9.0

GitHub Release v0.9.0 · ggml-org/llama.cpp github.com
preview

Overview:

This release adds OCP FP8 E4M3 quantization support, a new flash_attn_ext_rows op that makes the unified KV cache efficient for multi-sequence inference, and a generic batched tensor copy API. Four new architectures are supported (Clover, Limite, Metis-1.6 and Mistral Large 4), audio generation and transcription expand with Chatterbox TTS, Nemotron 3.5 Transcribe and predefined Pocket TTS voices, and the Gemma 4 E2B/E4B models get major prefill optimizations. ggml is updated to v0.29.0, bringing FP8 E4M3, flash attention rows, NCCL-based multi-node tensor parallelism and performance work across the CPU, CUDA, SYCL, Metal, Vulkan, OpenCL and Hexagon backends. The server and UI receive a round of fixes and refinements.

Is the next release going to be v1.0? Maybe with all the MoE caching improvements that should be culminating with github.com/ggml-org/llama.cpp/pull/30966 and Qwen 4 support?

Overview:

This release adds OCP FP8 E4M3 quantization support, a new flash_attn_ext_rows op that makes the unified KV cache efficient for multi-sequence inference, and a generic batched tensor copy API. Four new architectures are supported (Clover, Limite, Metis-1.6 and Mistral Large 4), audio generation and transcription expand with Chatterbox TTS, Nemotron 3.5 Transcribe and predefined Pocket TTS voices, and the Gemma 4 E2B/E4B models get major prefill optimizations. ggml is updated to v0.29.0, bringing FP8 E4M3, flash attention rows, NCCL-based multi-node tensor parallelism and performance work across the CPU, CUDA, SYCL, Metal, Vulkan, OpenCL and Hexagon backends. The server and UI receive a round of fixes and refinements.

Is the next release going to be v1.0? Maybe with all the MoE caching improvements that should be culminating with github.com/ggml-org/llama.cpp/pull/30966 and Qwen 4 support?

0

Webtoon paywalls are surprisingly rarely circumvented through piracy

preview

I recently picked back up reading comics and webtoons after years of having mostly forgotten about them, mostly because I missed reading some of my older favorites. And oh dear the paywalling is so much worse than it was back when I left webtoon. If I want to read an ongoing comic on Originals, I have to use the app. Fine, whatever, I can wait until it’s over. But if I want to read a finished comic, I have to read it on the app and I have to watch ads or pay to unlock every episode, and paying the webtoon currency is absolutely impossible. 20 to 25 coins per episode. The coin prices are absolutely outrageous, which I wouldn’t mind paying if they actually went to the authors, but particularly webtoon sucks at giving creators a fair cut. So I give up and download the app to watch ads so I can read the 200+ comic I wanted to read but I come to find the ads don’t even work! They load for a full damn minute and then they just send me back to the start page. So I go through all the usual troubleshooting and still nothing works. I’ve had it up to here with their freebie scam crap so I try looking for other site versions of the webtoons I wanted to read, but there are none since most are not in english and they’re not popular enough. This has been a four day fight that has left me insanely frustrated at something that used to be a nice relaxing hobby. The only good thing that I think has come of my little adventure is that now I’m extremely curious if anyone else around here has noticed the lack of high seas alternatives to those money hungry shit habits. I couldn’t really find means to remove the paywall, either, so I also wanted to see if maybe some more experienced pirate has a direction to point me into; and if anyone may have anything they wanna discuss about webtoon’s practices and the ethics of pirating media that is primarily made by independent artists.

I recently picked back up reading comics and webtoons after years of having mostly forgotten about them, mostly because I missed reading some of my older favorites. And oh dear the paywalling is so much worse than it was back when I left webtoon. If I want to read an ongoing comic on Originals, I have to use the app. Fine, whatever, I can wait until it’s over. But if I want to read a finished comic, I have to read it on the app and I have to watch ads or pay to unlock every episode, and paying the webtoon currency is absolutely impossible. 20 to 25 coins per episode. The coin prices are absolutely outrageous, which I wouldn’t mind paying if they actually went to the authors, but particularly webtoon sucks at giving creators a fair cut. So I give up and download the app to watch ads so I can read the 200+ comic I wanted to read but I come to find the ads don’t even work! They load for a full damn minute and then they just send me back to the start page. So I go through all the usual troubleshooting and still nothing works. I’ve had it up to here with their freebie scam crap so I try looking for other site versions of the webtoons I wanted to read, but there are none since most are not in english and they’re not popular enough. This has been a four day fight that has left me insanely frustrated at something that used to be a nice relaxing hobby. The only good thing that I think has come of my little adventure is that now I’m extremely curious if anyone else around here has noticed the lack of high seas alternatives to those money hungry shit habits. I couldn’t really find means to remove the paywall, either, so I also wanted to see if maybe some more experienced pirate has a direction to point me into; and if anyone may have anything they wanna discuss about webtoon’s practices and the ethics of pirating media that is primarily made by independent artists.

0

Nura in 2026-10: OSC Tokio, statutes, and project updates

Nura Nura in 2026-10: OSC Tokio, statutes, and project updates nura.eco
preview

This month, Rob and Masanori (thanks both!) represented Nura at the Fall OpenSource Conference in Tokyo, Japan. They handed over close to 50 leaflets, and showcased a great variety of devices, with attendants being astonished with how well Plasma Mobile and Phosh worked on them. Attendants were also happy to learn about the project rename, which is great news!

This month, Rob and Masanori (thanks both!) represented Nura at the Fall OpenSource Conference in Tokyo, Japan. They handed over close to 50 leaflets, and showcased a great variety of devices, with attendants being astonished with how well Plasma Mobile and Phosh worked on them. Attendants were also happy to learn about the project rename, which is great news!

0

YSK that the Mississippi Free Press has live updates on the Mississippi Senate election

preview

Link is here. The Mississippi Free Press’ coverage has been better than anyone else’s that I’ve seen, and I think they deserve your attention for the work they’re doing here. They’ve been giving updates at least once per hour, sometimes much more, and they’re actually talking with as many election officials as they can get in touch with across the state.


Why YSK: This is a hanging thread of possibly one of the most pivotal elections in modern US history. It’s looking increasingly likely that Colom will win, and this might sate your residual desire to doomscroll while actually keeping you informed.

Link is here. The Mississippi Free Press’ coverage has been better than anyone else’s that I’ve seen, and I think they deserve your attention for the work they’re doing here. They’ve been giving updates at least once per hour, sometimes much more, and they’re actually talking with as many election officials as they can get in touch with across the state.


Why YSK: This is a hanging thread of possibly one of the most pivotal elections in modern US history. It’s looking increasingly likely that Colom will win, and this might sate your residual desire to doomscroll while actually keeping you informed.

0

Some news about the new 40k wiki

preview

Greetings everyone,

As a staff member of warhammer40k.wiki.gg, we unfortunately have to announce to you the sudden closure of our website. This announcement has already taken effect, and the website will not come back on this host. This part of the adventure is done.

The short version: this is due to legal threats made against our host, wiki.gg, by Bell of Lost Souls, LLC (owners of Lexicanum).

As for the longer version and now that we can speak freely, we want to set the record straight about what happened. First, a full timeline of events:

  • Bell of Lost Souls acquired the Lexicanum on September 5 2014. With time, conditions steadily degraded for both editors and visitors, in terms of technical performances, monetization, and administration. Things reached a tipping point in 2026 on all these subjects. A large number of editors slowed down their productive output or even abandoned editing entirely because they simply couldn’t take these conditions anymore.

  • The idea of a fork, a duplicate of the original website that will then evolve its own way, started floating around in summer 2026. This is a very common thing in wiki culture. If you enjoy a particular gaming wiki on wiki.gg or Weird Gloop, chances are that it started as a wiki on the dreaded Fandom platform, and then forked away from it, only to become best in class about its topic. In the case of the Lexicanum this was legally possible ever since they came up with their new Terms of Service in 2014, since they explicitly put the wiki under the CC-BY-NC (Creative Commons Attribution NonCommercial) license. Once again this is a very common thing in wiki culture, but it seems Lexicanum staff didn’t realize what they had written themselves until very recently. More on this later.

  • After contacting wiki.gg on June 9 2026, the company’s legal team gave the go-ahead for the fork on August 12 2026 (quite a long wait!) In the meantime, construction of a new community started outside of Lexicanum-managed channels. With the authoritarian streak they had already shown time and time again, there was little doubt they wouldn’t agree with losing their status and powers over the people that provided value to their business model for zero personal benefits.

  • The team then took several weeks to discuss its new mission statement, come up with new democratic processes in order to make sure the Lexicanum’s managerial woes would never repeat again, and make its first votes about both staff and hosting. Things then proceeded until the wiki was delivered in private-access mode on September 11th 2026. The team immediately went to work, making thousands and thousands of edits to adapt the content to their new vision. Many editors kept working on both sites as a show of good faith between communities. This is when Lexicanum upper management started learning of the project and started banning editors who spoke of it.

  • On the technical side of things, no AI was used in the process of forking away from them. Mediawiki provides, out of the box, the ability to export content. We used a public archiving tool and its dump generator to make backups of the site, a tool that has already been used countless times in such situations. The Lexicanum’s internal database was never copied, only its public content, like it happens in most wiki fork cases. This was done using the built-in export function from MediaWiki, the software Lexicanum is running on. Yes, the same MediaWiki Wikipedia runs on, it’s basic wiki culture.

  • The wiki left private-access mode around October 11 (wiki.gg’s onboarding process usually is exactly a month), until we publicly announced our existence on Reddit on October 15. Some were understandably doubtful about our appearance, but many in the 40k community were relieved they could finally access a wiki that had good performances, was readable on mobile devices, didn’t have Cloudflare blocking several entire countries at a time, was not monetized as heavily as Lexicanum, and was finally willing to stand for change and improvements.

  • Starting October 16, Lexicanum’s management prowled our wiki’s Recent Changes list in order to go back to Lexicanum and ban there absolutely everyone who contributed to the new site, even people who were 100% unrelated to the fork as a whole, or people who wanted to keep contributing to both sites. It was a blanket ban that resulted in those editor’s user and talk pages being erased, despite their reputation being the only tangible trace of their thankless contribution to the community. This can be seen in their public block logs: 12 of the community’s most productive editors were banned in a matter of days, including some people who had been contributing for 15 years. If you have ever read Lexicanum at some point, there is no doubt that you have read some of these people’s work.

  • After that, Bell of Lost Souls completely discarded their old Terms of Service and hastily came up with a new one, effective starting on October 18. At this point it must be said that old content can not retroactively be covered by a new ToS. This new ToS also notably contains the following: “Article text located within the Mediawiki Main Namespace will become subject to the CC-BY-NC licence at a date of exactly 5 calendar years after the creation date of the most recent modification.“ That’s right. Lexicanum actually removed itself from the free information sharing space. It wants to be able to keep copy pasting materials from sources such as Games Workshop or other websites by pretending to respect CC-BY-NC, but they are now forbidding anyone from doing anything with the work of their editors for five years after an article’s last update. Which basically means for life, since a simple edit takes seconds and can be done by anyone to renew Lexicanum’s copyright. They didn’t inform their own users of that change in any public channel whatsoever, which is understandable, considering these volunteers were turned overnight into unpaid Bell of Lost Souls interns.

  • Legal threats were then sent to wiki.gg on October 21 2026. We won’t enter details about this because there is much wiki.gg didn’t tell us, but as a show of good faith, measures were taken by wiki.gg on the 40k Wiki to comply with some of the demands, such as the erasure of user pages copied from the old website. Things stayed relatively quiet and gentlemanly during this time period as the 40k Wiki kept growing in content and editor count.

  • On October 27, renowned Black Library author Noah Van Nguyen, writer of books such as Elemental Council, discovered the website and enthusiastically posted a message about it on Bluesky. This metaphorically broke a dam, as Lexicanum staff on the same social media then started going after Noah Van Nguyen themselves, and then launched a campaign of harassment against our own staff, spreading slander and weird threats of doxing and physical assault pretty much non-stop ever since. This resulted in the launch of our own Bluesky account. While we didn’t want to get into a flamewar, we wanted to make public our initial mission statement, which even now we are still firmly holding on to. We still believe in the values of democracy, of treating editors fairly and respectfully, and of making sure readers from all over the world can access our content.

  • We thought things were going fine until, on November 5 2026, wiki.gg suddenly decided to drop their support of our community, despite having greenlighted every step of the process ever since June of the same year. The wiki was closed on November 6, leaving us very little time to handle the fallout of their decision.

So now that the timeline is done, let’s address some specific points.

Are you doing this for money?

No. We are simply a group of editors who heavily contributed to the old Lexicanum, some of us for 5 years, some of us for 15, and who left for a better alternative because we couldn’t take it anymore. We just took our own work with us.

Lexicanum explicitly followed the CC-BY-NC licence between 2014 and October 2026, as shown in their own Terms of Service. CC-BY-NC explicitly allows copy, redistribution, transformation, and the building upon of material as long as appropriate credits are given, which we did, and as long as content is not monetized, which we weren’t. None of us is getting any dime for our work, unlike the Bell of Lost Souls staff, who are happy having ads overload with a Patreon-walled ad-free experience for what is essentially summarized Games Workshop content written by unpaid and poorly-treated volunteers.

Lexicanum’s new Terms of Service are essentially turning it into a closed-off moneymaking machine, but those terms can’t be retroactively applied to content that was forked before they were written.

Then what happened?

We don’t know. We can only surmise wiki.gg compared the projected cost of our legal defense and decided not to take the risk.

This is as far as we know an unprecedented example in wiki history. As explained earlier, tons of wikis fork away on the regular, and even the global corporation Fandom never tried to go legal over it. We can only theorize that Bell of Lost Souls would have lost the trial had it gone to court, but that wiki.gg preferred not to try it, since once again this is a first for the wiki editing community.

What did you achieve?

In the three weeks of its public existence, warhammer40k.wiki.gg’s stats absolutely soared. We recruited about 10 more editors, becoming the biggest and most active 40k wiki community, created about 300 new articles, uploaded around 500 new files and updated loads more, and made around 20k verifiable, human-made edits. What we were most proud of, was our ability to service readers from all over the world, unlike the old Lexicanum which heavily restricts readers by their countries or devices of choice, with a bias against regions such as South America, the Middle East, or Asia. A thing that Lexicanum management seems to find very funny in private channels.

Analytics showed us getting 25k active users and 163k views in these short three weeks, showing a clear interest from the community in our project. Fair and free elections were held, resulting in the democratic election of 2 new Administrators (including me yay!). The frontpage and many templates were heavily overhauled, resulting in a streamlined user interface. We started writing summaries for all Horus Heresy and Warhammer 40k novels. We even made RTS pages about Dawn of War IV. We had extremely cool icons made by one of our members.

We weren’t just a lore website, we intended to become a full and complete hub about Warhammer 40k and home wiki for games such as Dawn of War and Total War 40k, something similar to what the Warcraft Wiki is in relation to Warcraft as a setting. We were even in the process of voting a policy that would allow us to cover selected community content, wanting to preserve and safeguard 40k culture as a whole.

How does this impact the wider 40k community?

Rather terribly, we’d say. Since they banned the large majority of their own editors, Lexicanum has become a shell of a website, only useful as a money-making tool for Bell of Lost Souls. Most of the wiki was already written around the times of 4th edition, so prepare for things to get even more outdated, while you are served slowdowns, ads, Patreon messages and video shorts generated out of unpaid volunteer-written content. Also, if you are visiting from a country on Lexicanum’s blocklist, you have no alternative solution anymore.

What’s next for you?

We are exploring options for what is coming next. One of the things we can tell, is that we would like to remind Lexicanum staff that doxing is punishable by a prison sentence of up to two years in their own country.

We are all very proud of what we managed to offer the community in less than a single month of public existence. Shame about wiki.gg dropping us out.

The Planet broke before the Guard did. We hope to see you all again soon.

The 40k Wiki team

Greetings everyone,

As a staff member of warhammer40k.wiki.gg, we unfortunately have to announce to you the sudden closure of our website. This announcement has already taken effect, and the website will not come back on this host. This part of the adventure is done.

The short version: this is due to legal threats made against our host, wiki.gg, by Bell of Lost Souls, LLC (owners of Lexicanum).

As for the longer version and now that we can speak freely, we want to set the record straight about what happened. First, a full timeline of events:

  • Bell of Lost Souls acquired the Lexicanum on September 5 2014. With time, conditions steadily degraded for both editors and visitors, in terms of technical performances, monetization, and administration. Things reached a tipping point in 2026 on all these subjects. A large number of editors slowed down their productive output or even abandoned editing entirely because they simply couldn’t take these conditions anymore.

  • The idea of a fork, a duplicate of the original website that will then evolve its own way, started floating around in summer 2026. This is a very common thing in wiki culture. If you enjoy a particular gaming wiki on wiki.gg or Weird Gloop, chances are that it started as a wiki on the dreaded Fandom platform, and then forked away from it, only to become best in class about its topic. In the case of the Lexicanum this was legally possible ever since they came up with their new Terms of Service in 2014, since they explicitly put the wiki under the CC-BY-NC (Creative Commons Attribution NonCommercial) license. Once again this is a very common thing in wiki culture, but it seems Lexicanum staff didn’t realize what they had written themselves until very recently. More on this later.

  • After contacting wiki.gg on June 9 2026, the company’s legal team gave the go-ahead for the fork on August 12 2026 (quite a long wait!) In the meantime, construction of a new community started outside of Lexicanum-managed channels. With the authoritarian streak they had already shown time and time again, there was little doubt they wouldn’t agree with losing their status and powers over the people that provided value to their business model for zero personal benefits.

  • The team then took several weeks to discuss its new mission statement, come up with new democratic processes in order to make sure the Lexicanum’s managerial woes would never repeat again, and make its first votes about both staff and hosting. Things then proceeded until the wiki was delivered in private-access mode on September 11th 2026. The team immediately went to work, making thousands and thousands of edits to adapt the content to their new vision. Many editors kept working on both sites as a show of good faith between communities. This is when Lexicanum upper management started learning of the project and started banning editors who spoke of it.

  • On the technical side of things, no AI was used in the process of forking away from them. Mediawiki provides, out of the box, the ability to export content. We used a public archiving tool and its dump generator to make backups of the site, a tool that has already been used countless times in such situations. The Lexicanum’s internal database was never copied, only its public content, like it happens in most wiki fork cases. This was done using the built-in export function from MediaWiki, the software Lexicanum is running on. Yes, the same MediaWiki Wikipedia runs on, it’s basic wiki culture.

  • The wiki left private-access mode around October 11 (wiki.gg’s onboarding process usually is exactly a month), until we publicly announced our existence on Reddit on October 15. Some were understandably doubtful about our appearance, but many in the 40k community were relieved they could finally access a wiki that had good performances, was readable on mobile devices, didn’t have Cloudflare blocking several entire countries at a time, was not monetized as heavily as Lexicanum, and was finally willing to stand for change and improvements.

  • Starting October 16, Lexicanum’s management prowled our wiki’s Recent Changes list in order to go back to Lexicanum and ban there absolutely everyone who contributed to the new site, even people who were 100% unrelated to the fork as a whole, or people who wanted to keep contributing to both sites. It was a blanket ban that resulted in those editor’s user and talk pages being erased, despite their reputation being the only tangible trace of their thankless contribution to the community. This can be seen in their public block logs: 12 of the community’s most productive editors were banned in a matter of days, including some people who had been contributing for 15 years. If you have ever read Lexicanum at some point, there is no doubt that you have read some of these people’s work.

  • After that, Bell of Lost Souls completely discarded their old Terms of Service and hastily came up with a new one, effective starting on October 18. At this point it must be said that old content can not retroactively be covered by a new ToS. This new ToS also notably contains the following: “Article text located within the Mediawiki Main Namespace will become subject to the CC-BY-NC licence at a date of exactly 5 calendar years after the creation date of the most recent modification.“ That’s right. Lexicanum actually removed itself from the free information sharing space. It wants to be able to keep copy pasting materials from sources such as Games Workshop or other websites by pretending to respect CC-BY-NC, but they are now forbidding anyone from doing anything with the work of their editors for five years after an article’s last update. Which basically means for life, since a simple edit takes seconds and can be done by anyone to renew Lexicanum’s copyright. They didn’t inform their own users of that change in any public channel whatsoever, which is understandable, considering these volunteers were turned overnight into unpaid Bell of Lost Souls interns.

  • Legal threats were then sent to wiki.gg on October 21 2026. We won’t enter details about this because there is much wiki.gg didn’t tell us, but as a show of good faith, measures were taken by wiki.gg on the 40k Wiki to comply with some of the demands, such as the erasure of user pages copied from the old website. Things stayed relatively quiet and gentlemanly during this time period as the 40k Wiki kept growing in content and editor count.

  • On October 27, renowned Black Library author Noah Van Nguyen, writer of books such as Elemental Council, discovered the website and enthusiastically posted a message about it on Bluesky. This metaphorically broke a dam, as Lexicanum staff on the same social media then started going after Noah Van Nguyen themselves, and then launched a campaign of harassment against our own staff, spreading slander and weird threats of doxing and physical assault pretty much non-stop ever since. This resulted in the launch of our own Bluesky account. While we didn’t want to get into a flamewar, we wanted to make public our initial mission statement, which even now we are still firmly holding on to. We still believe in the values of democracy, of treating editors fairly and respectfully, and of making sure readers from all over the world can access our content.

  • We thought things were going fine until, on November 5 2026, wiki.gg suddenly decided to drop their support of our community, despite having greenlighted every step of the process ever since June of the same year. The wiki was closed on November 6, leaving us very little time to handle the fallout of their decision.

So now that the timeline is done, let’s address some specific points.

Are you doing this for money?

No. We are simply a group of editors who heavily contributed to the old Lexicanum, some of us for 5 years, some of us for 15, and who left for a better alternative because we couldn’t take it anymore. We just took our own work with us.

Lexicanum explicitly followed the CC-BY-NC licence between 2014 and October 2026, as shown in their own Terms of Service. CC-BY-NC explicitly allows copy, redistribution, transformation, and the building upon of material as long as appropriate credits are given, which we did, and as long as content is not monetized, which we weren’t. None of us is getting any dime for our work, unlike the Bell of Lost Souls staff, who are happy having ads overload with a Patreon-walled ad-free experience for what is essentially summarized Games Workshop content written by unpaid and poorly-treated volunteers.

Lexicanum’s new Terms of Service are essentially turning it into a closed-off moneymaking machine, but those terms can’t be retroactively applied to content that was forked before they were written.

Then what happened?

We don’t know. We can only surmise wiki.gg compared the projected cost of our legal defense and decided not to take the risk.

This is as far as we know an unprecedented example in wiki history. As explained earlier, tons of wikis fork away on the regular, and even the global corporation Fandom never tried to go legal over it. We can only theorize that Bell of Lost Souls would have lost the trial had it gone to court, but that wiki.gg preferred not to try it, since once again this is a first for the wiki editing community.

What did you achieve?

In the three weeks of its public existence, warhammer40k.wiki.gg’s stats absolutely soared. We recruited about 10 more editors, becoming the biggest and most active 40k wiki community, created about 300 new articles, uploaded around 500 new files and updated loads more, and made around 20k verifiable, human-made edits. What we were most proud of, was our ability to service readers from all over the world, unlike the old Lexicanum which heavily restricts readers by their countries or devices of choice, with a bias against regions such as South America, the Middle East, or Asia. A thing that Lexicanum management seems to find very funny in private channels.

Analytics showed us getting 25k active users and 163k views in these short three weeks, showing a clear interest from the community in our project. Fair and free elections were held, resulting in the democratic election of 2 new Administrators (including me yay!). The frontpage and many templates were heavily overhauled, resulting in a streamlined user interface. We started writing summaries for all Horus Heresy and Warhammer 40k novels. We even made RTS pages about Dawn of War IV. We had extremely cool icons made by one of our members.

We weren’t just a lore website, we intended to become a full and complete hub about Warhammer 40k and home wiki for games such as Dawn of War and Total War 40k, something similar to what the Warcraft Wiki is in relation to Warcraft as a setting. We were even in the process of voting a policy that would allow us to cover selected community content, wanting to preserve and safeguard 40k culture as a whole.

How does this impact the wider 40k community?

Rather terribly, we’d say. Since they banned the large majority of their own editors, Lexicanum has become a shell of a website, only useful as a money-making tool for Bell of Lost Souls. Most of the wiki was already written around the times of 4th edition, so prepare for things to get even more outdated, while you are served slowdowns, ads, Patreon messages and video shorts generated out of unpaid volunteer-written content. Also, if you are visiting from a country on Lexicanum’s blocklist, you have no alternative solution anymore.

What’s next for you?

We are exploring options for what is coming next. One of the things we can tell, is that we would like to remind Lexicanum staff that doxing is punishable by a prison sentence of up to two years in their own country.

We are all very proud of what we managed to offer the community in less than a single month of public existence. Shame about wiki.gg dropping us out.

The Planet broke before the Guard did. We hope to see you all again soon.

The 40k Wiki team

0

NestJS rate limiting: in-memory vs Redis vs Postgres (two instances break memory)

Waseem Anjum NestJS Rate Limiting: Memory vs Redis vs Postgres | Waseem Anjum fabwaseem.com
preview

I wrote this (my own blog). I shipped Nest with the default @nestjs/throttler storage and only noticed the hole when a second instance sat behind the load balancer — each process kept its own counter, so a client that should stop at 100/min quietly got closer to 200.

Retested on Nest 12.3 / throttler 6.7 with limit 100/60s on one box. One process: memory, Redis and Postgres all 429 on request 101. Two processes alternating the same IP: memory allowed all 130; Redis and Postgres stopped at 100. Localhost p50 was 0.36 ms memory, 0.38 ms Redis, 1.00 ms Postgres.

Storage code and tables are in the post. Curious what people use in production when they already have Postgres and don’t want Redis just for counters.

I wrote this (my own blog). I shipped Nest with the default @nestjs/throttler storage and only noticed the hole when a second instance sat behind the load balancer — each process kept its own counter, so a client that should stop at 100/min quietly got closer to 200.

Retested on Nest 12.3 / throttler 6.7 with limit 100/60s on one box. One process: memory, Redis and Postgres all 429 on request 101. Two processes alternating the same IP: memory allowed all 130; Redis and Postgres stopped at 100. Localhost p50 was 0.36 ms memory, 0.38 ms Redis, 1.00 ms Postgres.

Storage code and tables are in the post. Curious what people use in production when they already have Postgres and don’t want Redis just for counters.

0

Own Your Phone - a European Citizens' Initiative (ECI)

Own Your Phone They take your phone. We fight back. | Own Your Phone www.ownyourphone.org
preview

Join the action now! Help draft demands and proposals, add more languages to the website, and spread the word!

Join the action now! Help draft demands and proposals, add more languages to the website, and spread the word!

0

Thick Paint Blossoms

An impasto floral painting fills the composition against a textured cream-colored canvas background. On the left side, a blue flower blooms from a green bud. On the right side, two large white-and-blue blossoms curve outward among elongated green leaves rendered with sweeping strokes of emerald, teal, turquoise, and yellow. Thick ridges of paint create pronounced texture across the petals, leaves, and stems. Broad, energetic brushstrokes weave throughout the composition, with traces of blue, green, yellow, and orange paint visible between the foliage.
preview

(Buerz) (2026)

Image description: An impasto floral painting fills the composition against a textured cream-colored canvas background. On the left side, a blue flower blooms from a green bud. On the right side, two large white-and-blue blossoms curve outward among elongated green leaves rendered with sweeping strokes of emerald, teal, turquoise, and yellow. Thick ridges of paint create pronounced texture across the petals, leaves, and stems. Broad, energetic brushstrokes weave throughout the composition, with traces of blue, green, yellow, and orange paint visible between the foliage.

(Buerz) (2026)

Image description: An impasto floral painting fills the composition against a textured cream-colored canvas background. On the left side, a blue flower blooms from a green bud. On the right side, two large white-and-blue blossoms curve outward among elongated green leaves rendered with sweeping strokes of emerald, teal, turquoise, and yellow. Thick ridges of paint create pronounced texture across the petals, leaves, and stems. Broad, energetic brushstrokes weave throughout the composition, with traces of blue, green, yellow, and orange paint visible between the foliage.

0

Takayashiki Matsuri -Kazoku Keikaku

A young woman standing in a doorway holding the brim of a straw hat with both hands while leaning forward and looking upward toward the viewer with an open-mouthed expression. She has long, purple hair, blue eyes, and a wide-brimmed woven straw hat adorned with a white criss-cross ribbon pattern and bow. Her attire consists of a white short-sleeved sailor-style school uniform shirt with dark-grey collar and cuff trim featuring red stripes, a red neck kerchief tied at the front, and a dark-grey pleated skirt. The background features a traditional Japanese doorway with wooden sliding door frames, an entryway floor, and wooden clogs visible in the background background on the left.
preview

(azrakuC) (2026)

Image description: A young woman standing in a doorway holding the brim of a straw hat with both hands while leaning forward and looking upward toward the viewer with an open-mouthed expression. She has long, purple hair, blue eyes, and a wide-brimmed woven straw hat adorned with a white criss-cross ribbon pattern and bow. Her attire consists of a white short-sleeved sailor-style school uniform shirt with dark-grey collar and cuff trim featuring red stripes, a red neck kerchief tied at the front, and a dark-grey pleated skirt. The background features a traditional Japanese doorway with wooden sliding door frames, an entryway floor, and wooden clogs visible in the background background on the left.

Full Generation Parameters:

masterpiece, best quality, absurdres, general, <lora:takayashikimatsuri_ANMCM_v1-3-000008:0.8>, takayashiki matsuri, 1girl, solo, blue eyes, eyelashes, blue hair, very long hair, sidelocks, flat chest, small breasts, sun hat, straw hat, hat ribbon, white ribbon, school uniform, serafuku, black sailor collar, red neckerchief, collarbone, white shirt, short sleeves, black trim, red line, black skirt, pleated skirt, hands on headwear, open mouth, :o, parted lips, looking at viewer, cowboy shot, looking up, from above, indoors, entrance, sliding doors, wooden door, geta, shaded Negative prompt: worst quality, low quality, out of focus, ugly, bad anatomy, jpeg artifacts, lowres, error, missing limb, bad hands, missing fingers, extra digit, fewer digits, malformed hands, disconnected limbs, inaccurate limb, extra fingers, bad fingers, poorly drawn fingers, liquid fingers, artist logo, patreon logo Steps: 25, CFG scale: 4, Sampler: ER SDE, Seed: 2168545162, RNG: CPU, Model: waiANIMA_v10Base10, Shift: 3, width: 960, height: 1280, Version: neo-2.28, Module 1: qwen_image_vae, Module 2: qwen_3_06b_base, Model hash: 9d5a1e1393, Schedule type: Beta, Beta schedule beta: 0.6, Beta schedule alpha: 0.6

(azrakuC) (2026)

Image description: A young woman standing in a doorway holding the brim of a straw hat with both hands while leaning forward and looking upward toward the viewer with an open-mouthed expression. She has long, purple hair, blue eyes, and a wide-brimmed woven straw hat adorned with a white criss-cross ribbon pattern and bow. Her attire consists of a white short-sleeved sailor-style school uniform shirt with dark-grey collar and cuff trim featuring red stripes, a red neck kerchief tied at the front, and a dark-grey pleated skirt. The background features a traditional Japanese doorway with wooden sliding door frames, an entryway floor, and wooden clogs visible in the background background on the left.

Full Generation Parameters:

masterpiece, best quality, absurdres, general, <lora:takayashikimatsuri_ANMCM_v1-3-000008:0.8>, takayashiki matsuri, 1girl, solo, blue eyes, eyelashes, blue hair, very long hair, sidelocks, flat chest, small breasts, sun hat, straw hat, hat ribbon, white ribbon, school uniform, serafuku, black sailor collar, red neckerchief, collarbone, white shirt, short sleeves, black trim, red line, black skirt, pleated skirt, hands on headwear, open mouth, :o, parted lips, looking at viewer, cowboy shot, looking up, from above, indoors, entrance, sliding doors, wooden door, geta, shaded Negative prompt: worst quality, low quality, out of focus, ugly, bad anatomy, jpeg artifacts, lowres, error, missing limb, bad hands, missing fingers, extra digit, fewer digits, malformed hands, disconnected limbs, inaccurate limb, extra fingers, bad fingers, poorly drawn fingers, liquid fingers, artist logo, patreon logo Steps: 25, CFG scale: 4, Sampler: ER SDE, Seed: 2168545162, RNG: CPU, Model: waiANIMA_v10Base10, Shift: 3, width: 960, height: 1280, Version: neo-2.28, Module 1: qwen_image_vae, Module 2: qwen_3_06b_base, Model hash: 9d5a1e1393, Schedule type: Beta, Beta schedule beta: 0.6, Beta schedule alpha: 0.6

0

Vetternwirtschaftsaffäre der AfD – Wikipedia

Vetternwirtschaftsaffäre der AfD – Wikipedia de.wikipedia.org
preview

cross-posted from: sh.itjust.works/post/69523931

Bis zur Hälfte der AfD-Bundestagsfraktion könnte in Überkreuz-Anstellungen von Verwandten stecken – Ehepartner, Kinder, Geschwister, bezahlt von der öffentlichen Hand, dazu dubiose Abrechnungen und Spielbank-Besuche auf Dienstreisen. Die „Anti-Establishment"-Partei regiert wie eine Beutegemeinschaft – und wird weiter gewählt. Ich verstehe die Wähler nicht.

cross-posted from: sh.itjust.works/post/69523931

Bis zur Hälfte der AfD-Bundestagsfraktion könnte in Überkreuz-Anstellungen von Verwandten stecken – Ehepartner, Kinder, Geschwister, bezahlt von der öffentlichen Hand, dazu dubiose Abrechnungen und Spielbank-Besuche auf Dienstreisen. Die „Anti-Establishment"-Partei regiert wie eine Beutegemeinschaft – und wird weiter gewählt. Ich verstehe die Wähler nicht.

0

Warum ist Merz so unbeliebt? Suche weitere Details.

preview

cross-posted from: sh.itjust.works/post/63332619

Sicher, jeder hat eine Meinung dazu, ich suche aber statistische Details warum Friedrich so unbeliebt ist, was sagen die Befragten?

cross-posted from: sh.itjust.works/post/63332619

Sicher, jeder hat eine Meinung dazu, ich suche aber statistische Details warum Friedrich so unbeliebt ist, was sagen die Befragten?

0

Ultra.cc - SSH Password Security Updates

preview

(I’m not affiliated with Ultra.cc. I’m copying and pasting from https://ultra.cc/announcements/ssh-password-security-updates. Last updated on November 6, 2026)

We’re introducing stronger password checks and a new password generator to help protect your services and data. All customers must updated their SSH password by December 15, 2026.

SSH and SFTP/FTP passwords

The Change Password option for SSH will generate a random 24-character password containing letters and numbers. This password is shared by SSH and SFTP/FTP. Symbols are intentionally excluded to avoid compatibility issues with FTP links and scripts.

Application passwords, HTTP/proxy passwords, your UCP login and SSH keys are unaffected by this change.

Transition period: November 6–December 15, 2026

During this period, you can generate a password or use Choose Your Own Password, provided it scores Strong or above.

Until you generate a password, your UCP service page will display an “Update your SSH password by December 15, 2026” reminder.

On December 15, 2026, we will forcibly replace any SSH password that does not meet the new requirements. From that date, generating a password will be the only option for SSH and SFTP/FTP.

Stronger checks for newly set passwords

We’re also introducing a password strength meter across the UCP. New passwords must score Strong or above.

Common passwords, predictable patterns, and details such as your username, email address or app name can reduce the score. A long, unique passphrase can meet the requirement without symbols.

If you encounter any issues, or your newly generated password does not work, please contact our support team for assistance.

Best regards,

The Ultra.cc Team

(I’m not affiliated with Ultra.cc. I’m copying and pasting from https://ultra.cc/announcements/ssh-password-security-updates. Last updated on November 6, 2026)

We’re introducing stronger password checks and a new password generator to help protect your services and data. All customers must updated their SSH password by December 15, 2026.

SSH and SFTP/FTP passwords

The Change Password option for SSH will generate a random 24-character password containing letters and numbers. This password is shared by SSH and SFTP/FTP. Symbols are intentionally excluded to avoid compatibility issues with FTP links and scripts.

Application passwords, HTTP/proxy passwords, your UCP login and SSH keys are unaffected by this change.

Transition period: November 6–December 15, 2026

During this period, you can generate a password or use Choose Your Own Password, provided it scores Strong or above.

Until you generate a password, your UCP service page will display an “Update your SSH password by December 15, 2026” reminder.

On December 15, 2026, we will forcibly replace any SSH password that does not meet the new requirements. From that date, generating a password will be the only option for SSH and SFTP/FTP.

Stronger checks for newly set passwords

We’re also introducing a password strength meter across the UCP. New passwords must score Strong or above.

Common passwords, predictable patterns, and details such as your username, email address or app name can reduce the score. A long, unique passphrase can meet the requirement without symbols.

If you encounter any issues, or your newly generated password does not work, please contact our support team for assistance.

Best regards,

The Ultra.cc Team

0

[FO Friday] hand-dyed hat

preview

Wanted to make a hat in school colors, but couldn’t find a variegated yarn I liked. So like a crazy person I got some undyed yarn and acid dye, and dyed my own. This was my first time dyeing yarn, and I’m hooked.

I did take about 5g of yarn off the skein first to test different dye strengths for the purple to get it the shade I wanted before dyeing the whole skein. I used zip ties to create white spaces, then added yellow in those resist spots while the yarn was still wet.

I tried doing a yarn with a yellow main color and purple speckles, but for some reason I forgot color theory and put the purple on top of the yellow. Whoops! So I used some yarn from that skein to make the pom pom.

Pattern: Classic ribbed hat

Edit: I can’t spell Friday

Wanted to make a hat in school colors, but couldn’t find a variegated yarn I liked. So like a crazy person I got some undyed yarn and acid dye, and dyed my own. This was my first time dyeing yarn, and I’m hooked.

I did take about 5g of yarn off the skein first to test different dye strengths for the purple to get it the shade I wanted before dyeing the whole skein. I used zip ties to create white spaces, then added yellow in those resist spots while the yarn was still wet.

I tried doing a yarn with a yellow main color and purple speckles, but for some reason I forgot color theory and put the purple on top of the yellow. Whoops! So I used some yarn from that skein to make the pom pom.

Pattern: Classic ribbed hat

Edit: I can’t spell Friday

40

America turns on Donald Trump’s tech cheerleaders

preview

Companies including Palantir and Meta also rushed to hire Washington lobbyists with closer ties to Democrats ahead of their anticipated victory. OpenAI hired Jessica Schumer, daughter of Senate minority leader Chuck Schumer.

Since the election, AI companies have talked about rebranding data centres as “compute campuses” and promised a suite of incentives such as school funding, power investments and environmental concessions to entice local residents.

https://archive.ph/20261106125419/https://www.ft.com/content/bda53f77-f391-4750-ab5d-55e09cbbdb7c

Companies including Palantir and Meta also rushed to hire Washington lobbyists with closer ties to Democrats ahead of their anticipated victory. OpenAI hired Jessica Schumer, daughter of Senate minority leader Chuck Schumer.

Since the election, AI companies have talked about rebranding data centres as “compute campuses” and promised a suite of incentives such as school funding, power investments and environmental concessions to entice local residents.

https://archive.ph/20261106125419/https://www.ft.com/content/bda53f77-f391-4750-ab5d-55e09cbbdb7c