« first day (3781 days earlier)      last day (335 days later) » 
00:00 - 15:0015:00 - 00:00

15:00
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, blacklisted website in body, potentially bad asn for hostname in body, potentially bad keyword in body (289): Hotkey for Skipping to the Next Song in Spotify: Unveiling the Shortcut Secrets‭ by Yalani Yalani‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in title (1): If you're gonna die, die with your boots on(?)‭ by Harry‭ on chess.SE
@SmokeDetector tp Plagiarized from other answer on same site magento.stackexchange.com/a/103951
@GeneralGrievance Registered answer as true positive. If you want to blacklist the poster, use trueu or tpu.
@GeneralGrievance User blacklisted (23793037 on stackoverflow.com).
!!/test www.smhdiamondclean.com.au
15:24
> Potentially bad ns for domain in body, potentially bad ns for domain in title
----------
Potentially bad ns for domain in body - smhdiamondclean.com.au NS suspicious ns45.domaincontrol.com.,ns46.domaincontrol.com.
Potentially bad ns for domain in title - smhdiamondclean.com.au NS suspicious ns45.domaincontrol.com.,ns46.domaincontrol.com.
!!/watch smhdiamondclean\.com\.au
@GeneralGrievance You don't have blacklist manager privileges, but I've created PR#10488 for you.
PR#10488 ("General Grievance: Watch smhdiamondclean\.com\.au") opened by SmokeDetector
@GeneralGrievance User blacklisted (23793169 on stackoverflow.com).
15:26
!!/test www.locallockscbr.com
> Potentially bad ip for hostname in body, potentially bad ip for hostname in title, potentially bad ns for domain in body, potentially bad ns for domain in title
----------
Potentially bad ip for hostname in body - www.locallockscbr.com suspicious IP address 151.101.194.159
Potentially bad ip for hostname in title - www.locallockscbr.com suspicious IP address 151.101.194.159
Potentially bad ns for domain in body - locallockscbr.com NS suspicious ns27.domaincontrol.com.,ns28.domaincontrol.com.
Potentially bad ns for domain in title - locallockscbr.com NS suspicious ns27.domaincontrol.com.,n
!!/watch locallockscbr\.com
@GeneralGrievance You don't have blacklist manager privileges, but I've created PR#10489 for you.
PR#10489 ("General Grievance: Watch locallockscbr\.com") opened by SmokeDetector
15:27
@GeneralGrievance User is not blacklisted (23576369 on stackoverflow.com).
@GeneralGrievance User blacklisted (23576369 on stackoverflow.com).
!!/test klabs.kairostech.com
> Potentially bad ns for domain in body, potentially bad ns for domain in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Potentially bad keyword in body - Position 6-20: kairostech.com
Potentially bad keyword in title - Position 6-20: kairostech.com
Potentially bad keyword in username - Position 6-20: kairostech.com
Potentially bad ns for domain in body - kairostech.com NS suspicious ns76.domaincontrol.com.,ns75.domaincontrol.com.
!!/watch klabs\.kairostech\.com
15:28
@GeneralGrievance That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
Oops. Missed the keyword.
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ee0f84fecd (Makyen: Log as debug MS WebSocket messages) (running on Makyen/MS-Relay, Python 3.11.3)
[ SmokeDetector | MS ] Mostly punctuation marks in body (26): Python two lists using input and random‭ by Sergios‭ on stackoverflow.com
15:58
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Using Datepicker In Razor Form - ASP.NET MVC‭ by BR - Faria Netto‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, username similar to website in answer (75): Should a job application research statement include a "research plan"?‭ by Time Agency Group‭ on mathoverflow.net
@SmokeDetector tpu
@GeneralGrievance Registered answer as true positive and blacklisted user.
16:11
[ SmokeDetector | MS ] Link at beginning of answer, mostly non-latin answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (90): Is describing something as 'detailed and concise' an oxymoron?‭ by user500718‭ on english.SE
!!/watch- wmcasino\.cc
PR#10490 ("Vickel: Watch wmcasino\.cc") opened by SmokeDetector
Makyen/EC2-linux: Executing automatic scheduled reboot.
Makyen/EC2-num02 received failover signal.
Restart: API quota is 99999.
Unable to launch scan thread due to exhausted general thread limit of 2 for 180.45 seconds.
!!/approve 10490
16:37
!!/watch time[\W_]*+agency[\W_]*+group(?!\.com(?<=timeagencygroup\.com))
@Vickel You don't have blacklist manager privileges, but I've created PR#10491 for you.
PR#10491 ("Vickel: Watch time[\W_]*+agency[\W_]*+group(?!\.com(?<=timeagencygroup\.com))") opened by SmokeDetector
@Vickel You don't have blacklist manager privileges, but I've created PR#10492 for you.
PR#10492 ("Vickel: Watch time[\W_]*+agency[\W_]*+group(?!\.com(?<=timeagencygroup\.com))") opened by SmokeDetector
sorry about the double PR, please bin the 1st one (10491)
16:42
Makyen/EC2-num02: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev d5518f0 (SmokeDetector: Merge pull request #10490 from Charcoal-SE/auto-blacklist-1711383115) (running on Makyen/EC2-num02, Python 3.11.2)
Restart: API quota is 99897.
naa- feedback received on [MS] Near-future series, maybe four novels‭
@JeffSchaller Closed pull request #10491.
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How can I log into Heroku?‭ by Suraj Patel‭ on stackoverflow.com
17:00
Feature request: Being able to !!/close or !!/reject our own pull requests even without blacklist manager privs.
@Makyen uhh, did something chnage that'd break websocket handling of datetimes?
Thoth died hard due to typeerror of offset-native and offset-aware datetimes being subtracted
Mar 25 17:03:26 smokedetector-thoth systemd[1]: Started SmokeDetector StackOverflow Anti-Spam ChatBot.
Mar 25 17:03:26 smokedetector-thoth nocrash.py[833244]: 2024-03-25 17:03:26,272:INFO:[NoCrash] Starting with persistent_arguments ['/home/smokey/SmokeDetector/nocrash.py', '--loglevel=debug']
Mar 25 17:03:29 smokedetector-thoth nocrash.py[833246]: [17:03:29.170] Global blacklists loaded
Mar 25 17:03:29 smokedetector-thoth nocrash.py[833246]: [17:03:29.464] ChatExchange username loaded from config
ye so that's the hard deaths being introduced.
not sure if anyone's changed anything @Makyen
Thoth is offline until that's resolved
i'm not sure if that's because of an introduced change or not
@ThomasWard if it's datetime related, that's probably my PR
yeah that's a datetime related thing, did your PR get merged @JeffSchaller?
if so I may have to go hunting and do a revert because of the hard-breakage
17:08
Yes, then unmerged and ... I don't know the current status. github.com/Charcoal-SE/SmokeDetector/pull/8552
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body (2): Has anyone invested with Unique Options FX ✏️‭ by Charles Rennaker‭ on money.SE
Looking at just the chat history, I think Makyen reverted it, but maybe that was on a different instance
well i did a full git pull so it's still in the repository if Makyen didn't revert it.
I may have to do a manual revert if git revert doesn't work here
prepares for hell
so
No good deed :( sorry
@Makyen you merged, reverted, then reverted the revert
so now, I have to fix things
@Makyen github.com/Charcoal-SE/SmokeDetector/commit/… - HARD revert, don't put the PR back in until we have a harder review of this, because we have TZ-unaware dates, etc. coming from the Websocket
and that in turn breaks SD with the TZ-awareness added on startup
nope, still busted
this is a problem
prepares to fully clone a new SmokeDetector for testing
17:20
Whew, how little I know about how Smokey works! I was just trying to shut up the deprecation warning :/
yeah well even reverting that didn't fix it
so now i'm doing a test
does a chaotic evil
[ SmokeDetector ] GitHub Actions: success on a00ff32 by teward in the master branch
I seem to remember that pickles are/were an issue; do those need to be flushed somehow?
they can be nuked
(Assuming they're cached somehow)
17:22
but the issue i'm seeing is one related to ws.py and datahandling.py
@tripleee no resource starvation
CI on a00ff32 succeeded.
[ SmokeDetector | MS ] Link at end of answer, potentially bad keyword in answer (63): Hide/Disable SRP warning message‭ by Ibrahim Shaik‭ on superuser.com
okay, so a clean SD works
Restart: API quota is 99999.
17:31
so ye it's probably pickles
i can erase the mall or I can just let Cerberus run
i'm just going to let Cerberus run for now
until i know that nuking pickles is the way to go here
@ThomasWard thank you for cleaning up my mess!
[ SmokeDetector | MS ] Link at end of answer, potentially bad keyword in answer (63): Hide/Disable SRP warning message‭ by Ibrahim Shaik‭ on superuser.com
@JeffSchaller well i put us back into the last-known-working state. If ultimately those changes don't break anything, and we simply have to nuke all pickles, then we're golden.
but thankfully compute is no longer expensive with the dedicated system so :p
@SmokeDetector tpu
@GeneralGrievance Registered answer as true positive and blacklisted user.
@GeneralGrievance Registered answer as true positive and blacklisted user.
17:36
!!/location
!!/standby Makyen
Makyen/EC2-num02 is switching to standby
@ThomasWard Makyen wrote a reply to me after I fell asleep yesterday; sounded like they had a plan
@JeffSchaller link?
@GeneralGrievance User is not blacklisted (23526288 on stackoverflow.com).
@GeneralGrievance User blacklisted (23526288 on stackoverflow.com).
!!/test skateboardsprint.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username
----------
Potentially bad keyword in body - Position 0-20: skateboardsprint.com
Potentially bad keyword in title - Position 0-20: skateboardsprint.com
Potentially bad keyword in username - Position 0-20: skateboardsprint.com
17:41
16 hours ago, by Makyen
@JeffSchaller Yes, the issue is that there are, potentially, timezone naive date/datetime values stored in the pickles. When some operations are done on a mix of those values and timezone aware values, an exception will be raised, causing a crash. I'll need to go through all the structures which we store in the pickles to see where all a timestamp is stored and create code to make sure they get converted to timezone aware values. For the moment, I've hacked around it for the datetime values used in the queue in bodyfetcher.py.
I got it right the first time!
ye
so
that hack didn't make it to the main repos
hence why Thoth died @Makyen
for now Cerberus is running a clean SmokeDetector clone on the same system, so it should be fine because its a new tree and instance, but we need to make sure that any 'hacks' you do get propagated to the main repos
and if not, we just don't do a merge.
i'm happy to nuke Thoth's pickles but that'd be essentially what Cerberus is doing now
The PR is totally low priority; I just wanted to have some of the legwork done before it got critical
!!/report stackoverflow.com/a/78211177 "Undisclosed affiliation. Article author matches username"
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): get last part of page url and add it as cat in wp_query‭ by ehsan‭ on wordpress.SE
[ SmokeDetector | MS ] Potentially bad ip for hostname in body, potentially bad ns for domain in body (2): Menu drop down covers contents of page in Mobile view ✏️‭ by user3259342‭ on wordpress.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Show Element at Certain Time in Wordpress ✏️‭ by Kelsey Curran‭ on wordpress.SE
!!/watch winusb\.net
@JeffSchaller unfortunately it became critical xD
17:46
@ThomasWard heh
I appreciate your ability to see through the chaos
This is clearly attempted spam, right? stackoverflow.com/a/78218085
@GeneralGrievance I think so, with the failed link
Yeah, that's what I figured.
!!/report stackoverflow.com/a/78218085 "Attempted spam. Failed link markdown."
18:04
I couldn't find proof of affiliation yet, but this is likely CrapGPT spam: stackoverflow.com/a/78220866/20153035
nvm, found proof: medium.com/@gbober101/…
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Bootstrap collapsible not pushing down parallax ✏️‭ by M0NST4H‭ on stackoverflow.com
18:16
@SmokeDetector tpu
@GeneralGrievance Registered answer as true positive and blacklisted user.
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body (2): Has anyone invested with Unique Options FX ✏️‭ by Charles Rennaker‭ on money.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body (2): How to write formula for SIP calculator in javascript ✏️‭ by TechN Finance‭ on money.SE
[ SmokeDetector | MS ] Manually reported answer (93): How to change product image on hover?‭ by MagestyApps‭ on magento.SE
[ SmokeDetector | MS ] Blacklisted user (71): Image change on Mouse Hover‭ by MagestyApps‭ on magento.SE
tpu- feedback received on [MS] How to change product image on hover?‭
tpu- feedback received on [MS] Image change on Mouse Hover‭
Cow
Cow
@ThomasWard It seems like Smokey is repeating a lot of reports today, does this have to do with the problems you discussed earlier with Jeff?
@Cow Cerberus is a clean install of SmokeDetector - there may be repeats.
Cow
Cow
@ThomasWard roger that, must've missed that :)
yeah with Thoth having issues with datetime related things and then that maybe being pickle-related until I get in touch with Makyen to confirm that, Cerberus is a brand new SmokeDetector because we need SD running, even if it's not the same instance as Thoth because of the changes, etc. introduced.
Cow
Cow
@ThomasWard ah ok, thanks for the answer and I hope you're doing well :)
18:58
sips coffee
Cow
Cow
I hear you're very busy these days
[ SmokeDetector | MS ] Few unique characters in answer (89): Servidor de autenticação OAuth 2 em ASP.NET Web API‭ by Vitor Gabriel de Oliveira‭ on pt.stackoverflow.com
Cow
Cow
Remember to take care of yourself also
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): Roundcube mail AUTHENTICATE PLAIN: Temporary authentication failure‭ by HiddenSoftSheep‭ on serverfault.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in body, potentially bad ns for domain in body (2): I want to hire a consultant on 555 timers‭ by Senior Citizen Defender‭ on electronics.SE
19:03
@SmokeDetector tpu
@GeneralGrievance Registered question as true positive and blacklisted user.
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Runtime Error 5 in VBA: Invalid Procedure Call or Argument‭ by Víctor Bravo‭ on stackoverflow.com
[ SmokeDetector | MS ] Pattern-matching website in body (95): Opened compromised Excel file - am I safe?‭ by user275197‭ on security.SE
!!/location
Cow
Cow
19:07
@cocomac before you start, talk to @ThomasWard
:D
drops a flashbang in the channel
Cow
Cow
haha
At the moment, there are known issues with SmokeDetector instances. In order to get us functioning, I have an alternate instance - Cerberus - running instead of Thoth. As a result, because Cerberus is a clean instance, SD may show repeat reports or older reports or other chaos.
5
[ SmokeDetector | MS ] Messaging number in body, potentially bad ns for domain in body (82): Query Japanese verbs and their different conjugations‭ by cyborgreptile93‭ on opendata.SE
19:31
@ThomasWard At least some of the TZ-aware dates are in the pickles. It looks like you figured that out. Yes, I reverted and then re-reverted, because the issues appeared to be mixed data in the pickles, which wasn't something that could be fixed by just reverting, so I'd intended to move forward from the change. As to the WS, my instance wasn't experiencing that, at least for the first 14 hours (i.e., I didn't see any issues with the WS).
The hack I mentioned previously wasn't something that should be in the main repo. It was just on my instance long enough for the scan queue to get down to no entries and was automatically removed at the next reboot.
ack @Makyen well even the revert resulted in failures, probably because pickles had mixed data
the issue doesn't happen when we have a clean SD instance, which Cerberus is, so short of me nuking the pickles...
@ThomasWard Yep, that's what I experienced too.
@ThomasWard It's preferable not to do that. I'll work on code to clean all the pickle entries so they are all TZ aware.
@Makyen if you do that also revert the revert of the revert of the revert xD
if we have pre-code we can run to make the entries TZaware then we can safely reintroduce it
but yeah datetimes're evil
or rather, can be
19:36
Yes.
Let me think about it a bit more. There's at least one more place that my instance encountered after you put it in standby.
[ SmokeDetector | MS ] Url in title, potentially bad keyword in body, potentially bad keyword in title (96): Collected bitcoins at btcfree.win/ And made a GENERAL WITHDRAWAL 0.2 BTC‭ by Ганна‭ on bitcoin.SE
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): Establishing the crime of rape in islamic law‭ by Arsalan‭ on islam.SE
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): how can I atone for the sin of masturbation?‭ by Данияр Гаянов‭ on islam.SE
@Makyen same error you mean?
(Cerberus - a clean SmokeDetector instance - was the fallback solution until we could touch base on this problem)
fp- feedback received on [MS] Collected bitcoins at btcfree.win And made a GENERAL WITHDRAWAL 0.2 BTC‭
@SmokeDetector why
@ThomasWard Potentially bad keyword in answer - Position 1052-1092: ball of hooks, that while unable to kill
@SmokeDetector f
[ SmokeDetector | MS ] Potentially bad keyword in username (1): I dont know from where to approach this‭ by Mohit Singh‭ on dsp.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How do i force a link to open in the native browser of a mobile os?‭ by Mahjoub Kouzbour‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to renew SharePoint Designer 2013 workflow manager certificate‭ by Bikram Pal‭ on stackoverflow.com
20:17
@ThomasWard Same error, different location.
ah check
@Makyen you probably cleaned up your pickles or such so you aren't hitting the on-startup error.
but ye it's a nasty annoying thing
So, I guess the question is: Do we want to go with all TZ-aware or force everything to TZ-naive? Python appears to be moving towards forcing TZ-aware, which is the reason datetime.utcnow() is deprecated.
20:38
[ SmokeDetector | MS ] Potentially bad keyword in body, potentially bad keyword in title (2): Custom patch embedding layer for pre-trained Vision transformers‭ by paper‭ on stackoverflow.com
@Makyen correct. TZ-aware is how we SHOULD be doing it
and I would ASSUME UTC-aware
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, pattern-matching email in answer, potentially bad keyword in answer (273): Is there a way to use Youtube API for realtime history browser verification?‭ by Ella Mimi‭ on stackoverflow.com
in fact i'm starting to enforce this at the workplace for data coming in via API, etc. from data submitters to make it nonambiguous
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Null vs. False vs. 0 in PHP‭ by adrian‭ on stackoverflow.com
Cow
Cow
20:53
@SmokeDetector url is redirected to main site, looks like 404. User not seen for 4 years. Smells like promotion.
@Cow that post is from 2018, so i wonder if it's no longer an actual domain (but not spam/promotion anymore)
Cow
Cow
the website itself looks spammy tbh, coders for hire
I can remove the link at let it be
@SmokeDetector Removed link.
fp- feedback received on [MS] Null vs. False vs. 0 in PHP‭
[ SmokeDetector | MS ] Potentially bad ip for hostname in body, potentially bad ip for hostname in title (2): WordPress Dynamic.ooo Dynamic Posts Template not reflecting on Live Website‭ by Adrian Deetaisong‭ on stackoverflow.com
21:09
@ThomasWard I agree that TZ-aware (for us, effectively UTC-aware) is the way it should be done. However, in the meantime, I think it will be easier to go with TZ-naive, now, to get things back working, then spend more time going through things in more detail to see if we can find more sticking points. For example, it took about 30 hours from the point Thoth was running with the merged TZ code to the point where it crashed.
The current issue appears to be the data in the pickles. I'll go through all of them and write code which harmonizes all of the date/datetime values to either TZ-naive or TZ-aware, based on a parameter. That should make it easy to change to TZ-aware when we (likely me) go through and look at everywhere we get dates and make sure all of them change to TZ-aware.
@Cow @ThomasWard was correct. The domain has been taken over. The content which was there when posted is: web.archive.org/web/20180724133455/http://web-techno.net/…
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): :after not positioning correctly in Safari ✏️‭ by Meredith Dixon‭ on stackoverflow.com
21:23
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): How to write a blob file to local filesystem using PDI?‭ by Ezra Wise‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer, toxic answer detected (81): How do I detect for collisions without immediately resolving them in Godot 3D?‭ by user22692191‭ on stackoverflow.com
21:38
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ee0f84fecd (Makyen: Log as debug MS WebSocket messages) (running on Makyen/MS-Relay, Python 3.11.3)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword with email in body, pattern-matching email in body, potentially bad keyword in body (226): “Deity of love and justice gone viral”‭ by Kelvin Rachel‭ on rpg.SE
!!/watch- priestoguname(?:@gmail\.com)?
PR#10493 ("Vickel: Watch priestoguname(?:@gmail\.com)?") opened by SmokeDetector
22:04
@Makyen yeah since I reverted the code base back to pre-TZ-aware that's probably why your instance is asploding in different areas. I thought it best to go to the TZ-naive until we have a good plan for updating/fixing things
@Makyen we can also revise the original PR that adds TZ-awareness to determine it based off a config option, etc. whether to do TZaware or not, but as long as Stuff Works for now, I'm good. however, Thoth is tainted either way, so I'll need code to go through the pickles and unaware the dates of timezones, so until then, Cerberus is in charge
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body (2): What locks do each locking hint produce?‭ by a deleted user on dba.SE
@ThomasWard Yeah, I'll be working on that in a bit.
@Makyen perfect. Maybe even make it a standalone script that reads the pickles in, alters, and then does stuff :D
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How do I wrap my drawings around a circle in Illustrator?‭ by a deleted user on graphicdesign.SE
22:39
!!/alive
@cocomac Yup
22:52
[ SmokeDetector | MS ] Potentially bad ip for hostname in body (1): Emacs as Java IDE - How to run code? ✏️‭ by user19051‭ on emacs.SE
[ SmokeDetector | MS ] Few unique characters in body (95): lorem ipsum lorem ipsum ✏️‭ by gitpull terrier‭ on serverfault.com
23:22
tp- feedback received on [MS] lorem ipsum lorem ipsum‭
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Adding images to a drag and drop HTML game? ✏️‭ by strangevulture‭ on stackoverflow.com
teward/Cerberus: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 1932a6f41f (SmokeDetector: Auto watch of winusb\.net by Jeff Schaller) (running on teward/Cerberus, Python 3.10.12)
Restart: API quota is 95891.
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Available (soluble?) vs. total phosphorus for seed starting‭ by Daniel Slomovits‭ on gardening.SE
00:00 - 15:0015:00 - 00:00

« first day (3781 days earlier)      last day (335 days later) »