User talk:ShakespeareFan00

Archives: User talk:ShakespeareFan00/Sfan00 IMG

I II III IV User talk:ShakespeareFan00/Archive 5 User talk:ShakespeareFan00/Archive6 User talk:ShakespeareFan00/Archive 7 User talk:ShakespeareFan00/Archive8 User talk:ShakespeareFan00/Archive 9

Font-size:smaller

I'm a bit wrong, but I still don't recommend it. Got to thinking after I adjusted a few that it looked like it was working the same, but never see it used, so I asked. Sharing as an FYI. Apologies for my error. Zinnober9 (talk) 01:54, 30 October 2024 (UTC)

weird style problem and more

I came here to ask what you think is going on with this page Page:Arabian Nights Entertainments (1728)-Vol. 6.djvu/1. It has no style, yet it is rendering as if it does.

Then I read your message to consider leaving. To me it means "they win" "they have everything now".

I think that users of your software should each have their own name and not this name.--RaboKarbakian (talk) 08:14, 30 October 2024 (UTC)

I haven't edited that page seemingly. Can you explain more cleanly what's going on?
What is the exact error you are seeing? ShakespeareFan00 (talk) 08:16, 30 October 2024 (UTC)

1 Stat. R. 50

Page:Ruffhead - The Statutes at Large, 1763.djvu/96

Took a stab at it and removed the problematic status. I couldn't spot what made it problematic, so would appreciate your feedback on this one. Foofighter20x (talk) 16:44, 3 November 2024 (UTC)

I can't recall, Maybe I marked it problematic as an incomplete format, and forget to remove the status. Keep going. BTW if you want to standardise the formatting and make some notes on the talk page. This volume's formatting is a little convoluted, and probably need someone to make it consistent across all pages.
ShakespeareFan00 (talk) 16:56, 3 November 2024 (UTC)

If I had to guess, I think it was probably the footnotes within the footnotes. I have been going through all the prior pages to try and get used to what's already been done and touching up/standardizing across all pages, but I think this one was the first page I recall seeing footnoted footnotes. Foofighter20x (talk) 13:27, 7 November 2024 (UTC)

Another thing: I've decided to include the untranslated text of the chapters in Latin and law-French in the template pages within the frame box, but I am wrapping those untranslated portions in noinclude tags (i.e., when the template is called, those untranslated portions will not render in the calling page). This way, they are at least typed up somewhere, and it's been proofread and is easy to access until we have actual pages to where we can place them on the other language wikis. Foofighter20x (talk) 04:17, 8 November 2024 (UTC)

Check the equivalent pages at French and Latin Wikipedia, as I did an initial transcription of some of that text a while back. :) , By looking at those (and use of {{iwpages}} and {tl|IwPageSection}} you might save some time. I did this one transcription already.

Another note: In building for mainspace: On a longer acts the intention was to try and use the actual Short Title as the Work name if defined. The convention otherwise seems to be <Subject> (taken from the The Chronologicial Table of The Statutes)> <year>. Finding official short titles can be an involved process for early Statutes though.

Elsewhere on Wikisource/Commons , there are scans of Statutes Of The Realm, which might assist Translation efforts. ShakespeareFan00 (talk) 09:00, 8 November 2024 (UTC)

I know enough Latin and French that I can make passable attempts at directly translating them myself, but I'm not exactly sure where the translation I would produce should go. Would it be considered original research and thus need to be independenty published? I've got a little editing experience here, but in the main I guess I'm still kind of a noob. Foofighter20x (talk) 10:30, 8 November 2024 (UTC)

Wikisource supports user translations of Non English works, but they should be clearly marked as Trabnslated by Wikisource, and seperate from other transcription efforts. As mentioned some of the Non English in Ruffhead was translated in "Statutes of The Realm" , but if you want to attempt your own Law translation feel free, Don't use GoogleTranslate as what it produces isn't quite the samewhen tested with a short section where Ruffhead has both the origianl and English translation. Please note that the French is Law French not Modern French. Also some translation of early statutes aren't always literal translation (as some of the parrallel printing indciates.) The reason why the Non English wasn't included here was to do with Wikisource policy at the time the work was started.

If you want to attempt translations, feel free, but bear in mind other works on Law might have done so already. For some items (although less likely for repealed items) a semi-official translation might be on legislation.gov.uk BTWShakespeareFan00 (talk) 10:39, 8 November 2024 (UTC)

I would suggest initially doing the translation in you Userspace, and then ask how to possibly link them on the Scriptorum:) ShakespeareFan00 (talk) 10:39, 8 November 2024 (UTC)

rh/1

Hello. May I ask what is the benefit of edits like this? -- Jan Kameníček (talk) 22:58, 5 November 2024 (UTC)

A long term goal to simplify the running header code used across wikisource. Currently there are around 86,000 single content running headers that are preventing the simplification. If you think alternately Rh/1 can be replaced with left/right/center appropriately, I have no objections provided that it's done consistently across a work, which is what the focus of some recent editing efforts is. ShakespeareFan00 (talk) 23:02, 5 November 2024 (UTC)

Talk page watcher, just stopping by to endorse this simplification of the running header code used across Wikisource. It is a broadly good thing to do. BD2412 T 14:17, 8 November 2024 (UTC)

Won't be following this up just yet, (but you are welcome to review Rh/1 usage) I am running a check-back on my delinting efforts outside content namespace over the last 10 years or so. If you want to review my past delints as well feel free. Currently looking at Talk namepsace. :) ShakespeareFan00 (talk) 14:20, 8 November 2024 (UTC)

Indexes

The remaining pages of Index are free of Obsolete tags, and linthint's green when I scan these pages after publishing my edits, but I'm unable to clear Wikisource's claim of an obsolete tag remaining. I've tried purging page, hard purging, null editing, and got no change. Is it a wait it out situation, or am I overlooking something? Zinnober9 (talk) 14:08, 17 November 2024 (UTC)

@Zinnober9: Not just you, same issue. Consider raising a Phabriactor ticket as it's a headscratcher for me as well. ShakespeareFan00 (talk) 14:29, 17 November 2024 (UTC)

Explanation for edit?

Hi there! I noticed you made a couple edits to my userpage — however, I don't see any difference in the page before and after. Can you clarify what those are about? Thanks! Waldyrious (talk) 23:36, 21 November 2024 (UTC)

@Waldyrious: The edits are to do with night-mode: If you set the background color, you alos have to set the text color. If the repair worked would shouldn't see any changes. ShakespeareFan00 (talk) 23:38, 21 November 2024 (UTC)

Ah, got it! Thank you :) Waldyrious (talk) 23:44, 21 November 2024 (UTC)

suggestion

change "Apologies for the intteruption, but this was showing up on a list ofLints, missing style" to "Ignore this (I'm making a minor change to fix a list of missing style problems. sorry for the interuption"

It took me a while to realise that I needed to do nothing.

cheers Victuallers (talk) 14:48, 23 November 2024 (UTC)

your assistance please...

You left a note on my user talk page on commons, with a link [1] here, which, unfortunately, wasn't helpful...

I saw it started with Lint errors: Missing end tag, and I started looking through the output on those pages, until I got to a page that listed some pages in user space I worked on. I took a look at them, trying to figure out which tags were missing, without success. Can you help me determine this? Geo Swan (talk) 13:26, 24 November 2024 (UTC)

@Geo Swan: What's missing is for the most part italic and bold, which must be paired on a single line. I.e you typed ''' or '' at the start of a line, but forget to type the equivalent at the end of the line. I was also asking if these were drafts you'd later migrated to scan backed Pages.

I also use a script when editing pages - https://en.wikipedia.org/wiki/User:PerfektesChaos/js/lintHint - it provides a button in the top of pages which when expanded gives a list of unpaired tags. ShakespeareFan00 (talk) 13:58, 24 November 2024 (UTC)

filtering the list even more - https://en.wikisource.org/w/index.php?title=Special:LintErrors/missing-end-tag&exactmatch=&tag=all&template=all&titlecategorysearch=User%3AGeo+Swan&wpNamespaceRestrictions=2 ShakespeareFan00 (talk) 14:16, 24 November 2024 (UTC)

• Thanks for your heads-up, and for this example.
• What is ns104? Geo Swan (talk) 17:52, 24 November 2024 (UTC)

Page: namespace . ShakespeareFan00 (talk) 17:53, 24 November 2024 (UTC)

span and color

Where is the wiki documentation is "color" now required to be explicitly specified in a span tag? --EncycloPetey (talk) 02:39, 26 November 2024 (UTC)

You raise a reasonable point, I'm not sure the requirement that backgroound/background-color must now be accompanied by (foreground) color is adequately documented at Wikisource. It is however documented alongside the description of the relevant Lint Error in the documentation at Meta. Migration of FONT to span may alos have simmilar issues. If you want me to start reverting every single coonversion I can do that, but I feel strongly it would create far more noise than it solves. ShakespeareFan00 (talk) 09:51, 26 November 2024 (UTC)

@EncycloPetey: In relation to 'night-mode' - https://www.mediawiki.org/wiki/Help:Lint_errors/night-mode-unaware-background-color

@EncycloPetey: In reltaion to FONT->SPAN , https://www.mediawiki.org/wiki/Help:Lint_errors/obsolete-tag

Finding dumb typos

How do you find errors like this so quickly? Do you somehow subscribe to Special:LintErrors? I'd like to reduce your overhead by at least quickly cleaning up my own mistakes. Thanks. —Justin (koavf)❤T☮C☺M☯ 21:26, 30 November 2024 (UTC)

@Koavf: I just monitor to the list of LintErrors on a regular basis. ShakespeareFan00 (talk) 21:28, 30 November 2024 (UTC)

Need help

Please take a look here: https://en.wikisource.org/wiki/Talk:War_of_the_Classes#Duplication_of_chapter_heading -- Valjean (talk) 16:10, 13 December 2024 (UTC)

I think it's fixed now. -- Valjean (talk) 18:13, 16 December 2024 (UTC)

Old transcriptions in User Space..

I apologize for my late reply to your request regarding some old transcriptions in user space. The reason is I have been only rarely online recently due to being very busy in my offline life. However, I am not really sure what action is requested from me. If you think they should be deleted, it would probably be best to propose their deletion via the usual process. I am afraid I cannot just speedy a page from a user's space without any serious reason. -- Jan Kameníček (talk) 10:35, 24 December 2024 (UTC)

The message was that I was asking if you had time to rescue any of them as potential POTM or Monthy Challanges, duplicates could be courtesy blanking, but that might be contentious, so would have to go through the normal 'Proposed Deletion' process.. ShakespeareFan00 (talk) 10:57, 24 December 2024 (UTC)

I see. Not sure if I will have time for that, but you may try to write directly to the POTM or Monthly Challenges talk pages. --Jan Kameníček (talk) 11:02, 24 December 2024 (UTC)

Scribners jpegs

I almost undid your undo. I need a few minutes to think about it. You correct me too quickly, I learn by my little bits of clean up. 14:50 and 14:52

You gave me less than what, less than 3 minutes to figure it out?

Your edits recently have been mostly bogus (meaning I did not make that mistake) and creepy. I am already cringing when I see you have been on my work.

But that was a good template. Some one has to figure out how to separate this from the google spam, I think.

ShakespeareFan00 should always be very credible with anything css.

Okay so

1. More time between my edit and yours.
2. Always have credible edits.
3. Detach from my google spam

And a large part of my life would be better, great even. I learned a lot from you.--RaboKarbakian (talk) 15:13, 31 December 2024 (UTC)

Okay so you are concerned that putting the suggested fix back in was done to quickly? None of my recent edits were anything other than good faith attempts to make reapirs to resolve lint concerns and related issues. Do you have a specific list of other edits you have concerns about? If you have getting stressed from having your efforts 'reapaired' than I strongly suggest taking a few days away from contributing. Are you using AI or a a transaltion tool because your comments above sound like a generated response BTW ShakespeareFan00 (talk) 15:25, 31 December 2024 (UTC)

Ppoem native rules

Would you mind spelling out what spec exactly you have in mind? Two things need to be defined: input, what the user enters, and output, what it should produce. The input format at {{ppoem/testcases}} could be criticized because it looks kinda like HTML, with the angle brackets, especially when you compare comment start: <!-- and that: <- (maybe not a real problem). It's mostly about the output that I don't know what to do. If we want to be semantically correct, it's a kind of <hr>, taking some care to arrange the stanzas around it. This would mean that it would always separate stanzas in two, which semantically may be meh. If that isn't too bad, this'd be option #1 for me. There are plenty of ways to fake horizontal lines, e.g. a span with height:0px;border-top:1px solid black;display:inline-block;, but that is surely bad semantic-wise. — Alien  3
3 3 15:27, 1 January 2025 (UTC)

Hmm. Do you have an alternate syntax.. ? We need to be able to do {{rule}} inside ppoem though.

Standard wikitest would be ---- for a rule on a single line , but that doesn't allow for the additional paramaters {{rule}} did.

<-:x> Outputs the same as {{tlx|rule|4em}} , but appropriately centered within the ppoem outer container, using an HR, which breaks stanzas if encountered. Is it possible to have a means of adding addition params stop set style? or do he have something like <-:width:height:style> ?  hmm...

<--:x>  Was intended to be a double rule (essentially a style change). with the same params.

Note: The rules need to collapse, I.e each <hr /> must be it's own line, with appropriate spacing. And obviously rules need to be outside the 'stanzas' (The implied Stanza break you were favouring.

ShakespeareFan00 (talk) 15:38, 1 January 2025 (UTC)

On input syntax, maybe the same thing replacing the angle brackets by something else? IDK. I wouldn't die on that hill anyhow

The hr's are not line content, and so would not in fact be inside any lines, it would be outside lines and stanzas.

On default params, I think {{rule}}'s way of putting full height when nothing given is better, because 4em wasn't used any more than 3em, or 6em, or 5em (and also, if it's default it's easier to find, with <-:100%>(the way to get it if it's not default) maybe being not intuitive, unlike the ems).

On multiple rules, it'd maybe be better, as very often when there are multiple they are not the same size, to allow putting something like <-:8em:4px><-:6em:2px> on a single line (in the input) for these two hrs to be right after each others in the output, with nothing in between. — Alien  3
3 3 15:45, 1 January 2025 (UTC)

Oh, also, on rule inside ppoem: this would get all of rule's functionalities, and it trying to parse where the p tag will autoclose, to try and make a cleaner stanza break around it, would be an absolute nightmare. Remaking a specialized parser is a pain, and it's likely to not understand code exactly the same way mw does (I've done it once, for a simplified parser), and if we try and rely on mediawiki parsing, we'll have to match the output to the input, which is also complicated.

There are very few of these 600 invalid uses that should've been valid. There were the {{rule}} ones, and {{cr}} can hopefully be made inline-block (intend to look into it sometime soon), and apart from that, I don't remember any (the rest was things like FI, nesting ppoem, cblock, &c). Once this is done, there'll be no use for {{rule}} inside ppoem, and normally we don't have another template to replicate. — Alien  3
3 3 15:52, 1 January 2025 (UTC)

I'm not set on the angle brackets, If you can find something that is wasy to parse for, feel free to use it. I support your idea width:height btw ;).. Do we have custom rules which set a style attrib on the <hr /> ?

ShakespeareFan00 (talk) 15:49, 1 January 2025 (UTC)

(width:height was your idea, not mine, I just shamelessly stole it from your answer.) Custom styles is just {{rule|...|style=...}}, I think. — Alien  3
3 3 15:53, 1 January 2025 (UTC)

So we would need a way to have the style in the syntax, or better would be the classing approach already supported for lines and stanzas...  ;)

Oh. very good idea. So <-:width:height:class1 class2 class3 ...>, with classes separated by spaces, adding .ws-poem-[name]. — Alien  3
3 3 16:05, 1 January 2025 (UTC)

Exactly . ShakespeareFan00 (talk)

And output, it would be an hr, with class ws-poem-rule and user-added classes, and with style height:what the user gave or 1px if they didn't give anything, and width:what they gave or 100%. (The ws-poem-rule class would permit work-scale styling, e.g. if all rules inside ppoems are in this book 4em or 6em or whatever. Will get at work in sandbox and show you end result when I'm done. — Alien  3
3 3 16:12, 1 January 2025 (UTC)

Well, I guess this is all made moot now, apart maybe from the use it would still have of better semantics (the rules not being line content)? I'd like your opinion on that. What do you think?

Again, I cannot tell you how sorry I am for dragging you into that mess, essentially for nothing. — Alien  3
3 3 09:14, 3 January 2025 (UTC)

The Night Born

Thanks for your edits there. I see now how fine block is supposed to work across pages. (I wonder if it is worth mentioning that on the template page). I don't see what nopf is doing - would you be so kind as to explain ? -- Beardo (talk) 02:59, 5 January 2025 (UTC)

The {{nopf}} is there to stop the last line of the page becoming it's own paragraph. (Known glitch in Proofread page/Mediawiki ShakespeareFan00 (talk) 07:54, 5 January 2025 (UTC)

fsn and (all)smallcaps

Last january, {{fsn}} was changed by you to normalise not only italic, as was its purpose till then, but also smallcaps. This breaks some stuff, as up to 2024 it did not remove smallcaps. Moreover, this duplicates the purpose of {{fvn}}. Do you agree that normalising smallcaps should be left to that template, and removed from {{fsn}}? — Alien  3
3 3 06:32, 7 January 2025 (UTC)

Do what you think is appropriate, but remember to check usages. ShakespeareFan00 (talk) 09:40, 7 January 2025 (UTC)

In re Eng. Rep.

Just a heads up: since I reloaded the 1 ER base file with an assembled pdf of clearer and less-distorted scans from CommonLII (which is why I stopped editing for a few days: was figuring out how to use Python to grab all those files), the default OCR that Wikimedia is using to prefill the body block when loading an uncreated page has been producing worse quality OCR prefills.

However, above the page display window on the right, I've found that changing to the Google OCR in the "Transcribe Text" dropdown and then punching that button that prior to any editing works miracles. You probably already noticed/knew this, but in case you hadn't/didn't, I'd loathe myself if I didn't save you lots of editing time by not mentioning it. --- Foofighter20x (talk) 22:35, 11 January 2025 (UTC)

I was aware of the Google OCR, it was my standard goto. Thanks for the new scans.. If you can assemble a PDF for the volumes we don't have that would be very useful.. ShakespeareFan00 (talk) 23:26, 11 January 2025 (UTC)

Yep, that's very much on my radar. The catch in pulling the better scans from Common LII has been that I have to combine all the files in Acrobat Pro and then go through the compiled volume page by page to eliminate all the duplicate pages (i.e., where one case ends and the next begins on the same page, that page will be in each file, hence will be present twice in the assembled Acrobat binder; there's simply no way to automate that process in AAP). On top of that, I still have to find scans of the Eng. Rep. volumes proper that have been posted online so I can also include the front and back matter, which isn't available at Common LII. Still, now that I have the Python code working the way I want it, I've got it on my short term to-do list. --- Foofighter20x (talk) 00:03, 12 January 2025 (UTC)

Always more work to do: Have started to put together the front page for the set and for each volume. I'm also trying to include corrections and date conversions as I go along (within tooltips; see here as to R v. Visc. Purbeck, in re its purported year of decision). --- Foofighter20x (talk) 21:02, 15 January 2025 (UTC)

You might need to fork the template which was designed primarly for US cases, not British ones? ShakespeareFan00 (talk) 23:19, 15 January 2025 (UTC)

Sounds like a good idea, but I'm an American, so I'm not exactly sure what all info should be mandatory/required, and what else should be includable. I could always start with what's in Table 2.43 of The Bluebook, but a little specialized knowledge from a Brit would be beneficial before I'm so bold to start. Also, at least as far as the Eng. Rep. editors put in references to Mews Dig., I'd think including those snippets from Mews as quasi-headnote in the case page, as I did in R v. Viscount Purbeck. --- Foofighter20x (talk) 23:58, 15 January 2025 (UTC)

Generally, if it isn't the original scan, adding headnotes from another source, is an 'annotation' which is generally discouraged, also the headnotes source might not be under a compatible license, unlike the text in the scans. ShakespeareFan00 (talk) 00:03, 16 January 2025 (UTC)

I guess I should clarify what I mean by "adding headnotes": I'm only thinking of putting that Mews material in the notes block of the header template at the top of the transcluded presentation pages (again, see R v. Viscount Purbeck toward the top in the gray). In support of that, I'll add that I think the only parts of the Eng. Rep. that weren't published before Jan. 1, 1930 are the two index volumes; if that's the case and they are still copyrighted (which I'm not sure they ever were), they'll be out of copyright in a year... Given that all those substantive volumes are public domain, their references to Mews necessarily implies that such Mews material is also public domain. --- Foofighter20x (talk) 00:40, 16 January 2025 (UTC)

Front matter page numbers

I've noticed several recent books where you've set of the from matter page numbering with errors. You seem to be assuming the title page is i, but for the books you've set up, that isn't the case. When there is a half-title, that's usually page i (except in cases where some arbitrary earlier page is the starting point). --EncycloPetey (talk) 14:11, 12 January 2025 (UTC)

Thanks, I'll take another look. ShakespeareFan00 (talk) 14:20, 12 January 2025 (UTC)

Can you list some specific examples, as the ones I've had another look at seem to do the front matter from the Half title? ShakespeareFan00 (talk) 14:27, 12 January 2025 (UTC)

See for example Index:Rainbow Valley text.djvu, where the Half-title is the start page, and there is a leaf for the Frontispiece inserted between pages ii and iii. Plate-beating leaves are usually inserted after the printed pages are folded. Or see Index:Red Harvest.pdf. --EncycloPetey (talk) 14:38, 12 January 2025 (UTC)

Already corrected. and I am finding some others as I check. Thanks for the heads up, List anymore you find below :).

(Aside) A lot of the Duplicate Page-ID's seems to be front matter with duplicative ID's. The intent was (with checks) to replace some of these with 'roman' numerals from the works concerned? , For image plates I was considering amending them to use "(sp<djvupage>)" or "(fp<adjacent pageid>)" depending on the work. What are your suggestions? ShakespeareFan00 (talk) 14:44, 12 January 2025 (UTC)

Two issues to consider: (1) Our recommendations explicitly allow for named pages when the work in question does not have a clear numbering system for pages in the front matter. (2) Changing page numbers / naming can break page links, so it shouldn't happen unless it's absolutely necessary.

Why "sp"? And where was the change to image page naming discussed? --EncycloPetey (talk) 15:05, 12 January 2025 (UTC)

sp=Scanpage. I hadn't raised the issue on Scriptorum yet, so will not be changing existing numbering (other than the Half/Title confusion you pointed out.). Something needs to be done about the 'linter noise' though. ShakespeareFan00 (talk) 15:07, 12 January 2025 (UTC)

Quick question

Hey ShakespeareFan00. On Index:Monthly Weather Review, Volume 1, Issue 4, STORMS.pdf, I noticed made an edit changing a X to a C, and as I have seen this done by several editors before, I wanted to know why? I don't even know what the C or X stands for, so hopefully you can explain them as well for a newbie. WeatherWriter (talk) 21:06, 12 January 2025 (UTC)

It means someone checked the uploaded file was complete. Carry on proofreading. ShakespeareFan00 (talk) 22:25, 12 January 2025 (UTC)

Orphaned categories

Hi, these categories that you created have no parents and so are lost in the tree. Can you please review and determine their best position?

• Category:Malformed identifer for numbered div
• Category:Parameter3(Numbered Div)

Thanks, Beeswaxcandle (talk) 07:19, 15 January 2025 (UTC)

Pagelists

Thanks for adding pagelists to some of my recently added indexes. (I am still quite new at doing these.)

Is there an easy way to get those lists ? Or do you have to go through the scans to see what is there ? -- Beardo (talk) 01:08, 22 January 2025 (UTC)

You have to go through the scans, but an easy and fun way of doing it is at the top right. It's the "wikisource page game", and it figures it out pretty well.

For some reason, when I upload a new document, the scan is not properly available. It always throws an error up, at least for a few hours. Then I remember a day later and come back to it, and @ShakespeareFan00 has already done it for me. FPTI (talk) 06:48, 22 January 2025 (UTC)

(This "Invalid interval" problem can be fixed by purging the file at commons.) — Alien  3
3 3 08:00, 22 January 2025 (UTC)

@FPTI, @Alien333 - thanks guys. I'll have to have a go at that some time. -- Beardo (talk) 00:46, 23 January 2025 (UTC)

@Alien333 How does one purge a file at commons? I'm having the same problem with Index:Demonology and Devil lore volume 1, conway.djvu. Please don't do it for me, I want to learn how to do it so I can stop being bothersome about it. Unless it's something that only a mod or privileged editor can do? — FPTI (talk) 09:16, 25 January 2025 (UTC)

Never mind. Found it. FPTI (talk) 09:19, 25 January 2025 (UTC)

Nah, it's easy. There's a "purge clock" (or perhaps "UTC clock", I don't remember exactly) gadget. Once you activate it, you should get a blue clock in the top left menu. Click it to purge. — Alien  3
3 3 09:19, 25 January 2025 (UTC)