News

2025-04-23

• I'm not dead, but I'm also not back per se. I'm working on revamping the CSS on the site, and I wanted to share an update on my progress. I've been working on a different site and neglecting this one as a result, so I want to bring it back to my current standards. Some changes to come are:
• The five or six .css files I'm using will be consolidated into just one: delta7447.css (though that link won't work until I've actually implemented all this). This will require going through each and every .html file on the site and adjusting what .css files are linked to them—which will be precisely as fun as it sounds.
• The variety of included fonts will be reduced. Recursive will be the sole sans-serif font, covering both proportional and monospace text. On the serif side of things, Merriweather will take over for Bitter for story text. Merriweather won me over with its optical sizing axis and larger glyph count.
• Material colors are out, while relative OKLCH colors are in. Most colors won't change significantly, though my use of green on my fetish list for my likes will be swapped to blue to avoid being color-blind-unfriendly, given my use of red for dislikes.
• OKLCH colors became baseline (as in supported by all modern major browsers) in May 2023, so I'm reasonably confident my using it won't be an issue. caniuse.com reports 93.1% of users globally can view OKLCH colors as I write this, so it should be fine. Even so, if you're somehow in that 6.9% and this change makes my site unusable for you, please let me know and I'll do what I can to implement a workaround.
• I'm planning to scrap my Javascript implementation of a light/dark mode toggle in favor of a @media query (prefers-color-scheme), automatically using whichever one your device/browser is set to. I'm not sure how useful a manual toggle is, to be honest. Removing it simplifies my code and my site has less Javascript involved—a win-win, if you ask me. Please let me know if you disagree, of course.
• My use of colored outlines to indicate links, rather than colored text with underlines like the literal entire rest of the internet (it's straight up discouraged to not have underlined links, it's that ubiquitous), is clunky and awkward. I have no idea what I was thinking when I implemented that. Likewise, the CSS to add an emoji arrow next to external links is getting canned too. You can hover over/long press a link to view its destination—I don't do anything to obfuscate that. Moreover, you can probably tell from context where a link goes anyway.
• Webkit (the engine that runs Chromium browsers) has a slew of CSS elements for customizing a scrollbar on a very granular level. I attempted to do this to doll up the scrollbars on my site, but I've since concluded it's more trouble than it's worth, seeing as the implementation is non-standard. Instead I'll be using the simpler and more standardized scrollbar-color, making it look unified with my site's aesthetics but without being an overdesigned eyesore.
• The max-width of the site will be reduced. I'm currently thinking 55rem, which is 880px at a default 16px font-size. On a wide device like a desktop with the browser maximized, a page's content will be centered on the screen with open space on either end. Narrowing the viewport will reduce the amount of open space. Only upon reaching a viewport width less than 55rem will text start to wrap naturally—that's most likely what will happen on a smartphone. All in all, it should either improve or have no impact on one's reading experience.
• The big gray buttons on the nav page will be revamped. The new look is on the simple side, but I'm proud of what I've come up with regardless. It's loosely inspired by jdan's 98.css—or more broadly the skeuomorphism used in the design of early versions of Windows to help the average user understand how things work.
• The barebones mode thing I had in place was honestly an experiment more than any sort of actual deliberate usable feature. It will be nixed too.
• These specifics are all subject to change, but the general idea is that changes are coming to improve the site's appearance.

2024-11-30

• Commissions are closed for the foreseeable future. More on that on my commissions page, or on DeviantArt.

2024-09-02

• I had a bit of a brainfart and neglected to mention this on the day I actually did it (August 31). I added Mango's Lanaverse caption to the site. That particular page has a red accent color to fit with Lana's motif. I might do something similar for Super Goddesses, not sure yet.
• Today, I've given color.css a renovation. I had been using OKLCH colors for novelty's sake, but since most browsers didn't support them until early 2023, they simply wouldn't work at all on an out-of-date browser. So I implemented fallback hex values for everything to (hopefully) override the unrecognized OKLCH values. That got cumbersome, if I'm being honest. Really, OKLCH is good for finding colors. If you need a lighter or darker shade of an existing color for making a color scheme, it's excellent. But since I'm using Material colors, an already established and quite thorough palette, I (generally) don't need to figure out anything new. Everything supports hex, so why should I go out of my way to avoid using it?
• So as a result of this, color.css is about twice its previous size (was 5343 bytes, is now 10894 as I write this), largely due to defining every Material color, not just the ones I'm using.
• For the typical end user, you shouldn't notice any change. The larger file shouldn't have a significant impact on performance. I believe the transition was seamless, but please let me know if you spot an error!

2024-08-07

• I apologize for the infrequency of my updates lately.
• I've added my Fate captions to the site.
• I also made the 404 page a bit fancier, centering the text on the screen with flexbox chicanery.

2024-06-20

• It's been a while since I've made updates to the site beyond some occasional additions to my recommendations list. I've done some behind-the-scenes housecleaning to improve the quality of my code. Turns out the id parameter can be applied to other things like <h2>, as opposed to just <a>.

I seem to have accidentally removed my <blockquote> formatting, probably while updating my table of contents thing. So I've restored/remade that.

• I've adjusted the sizes of header text to not get so tiny. Granted, I don't typically use any past <h3>. I've never liked that <h5> and <h6> end up smaller than 1em, so this fixes that, making <h6> be 1.333em.
• I should've renamed "genshin.html" to "genshin_impact.html" back when I was doing that filename revision thing. So I did that.
• I really should have link focus styling on my site, so now I do. Hit Tab or click on a link (clicking a link makes it the one being focused on) and you'll see it.

2024-04-09

• I've made my works page responsive, thanks to work by Drew Dyksterhouse (sapientPearwood), who was in turn inspired by Chris Coyier of CSS Tricks. With some CSS and JavaScript chicanery, it will detect when/if your screen is too narrow to view the whole table in all its glory. If that's the case, it'll transform the table into a much more vertically-oriented and mobile-friendly variant. I'm rather pleased with how this turned out. Please let me know if you encounter any issues.

2024-03-30

• I made a nice and simple sitemap, easily accessed via the new button on the nav page.
• In the process of doing so, I realized I didn't have a Crypticverse page. Fixed that. Ugly uncustomizable 403 Forbidden page, begone!
• I did a bit of CSS chicanery to produce something resembling mobile/desktop parity: basically just somewhat centering the list of bullet points while keeping the nesting nice and pretty.
• On a less significant note, I tweaked the size of the bullet points, getting them more in line with Firefox defaults size/placement-wise while remaining customized to my liking (square, green for dark mode or purple for light)

2024-03-26

• I recently discovered an issue with my light/dark mode toggle. Due to the order of operations between the DOM and JavaScript, a page set on dark mode would flash white briefly upon page load or a refresh. Fixing that simply required putting it in <head> and adding an extra line to have it run only once the DOM is damn good and ready.
• Additionally, my infrequently-used abbr.js is now on most pages, which should better facilitate reading <abbr>-tagged text on mobile.
• I've also included support for a barebones.css, meant to simply the site's visuals for either a plainer experience or to accommodate a low-end browser. Ideally, all of the CSS within an old browser (like Internet Explorer 6 old) no problem--it's a sort of compatibility mode. (Granted, IE6 won't be able to render WOFF2 fonts, but I'm equipped with a slew of fallbacks.) The sheet isn't entirely finished yet, but the broad strokes are there.
• If you'd like to give it a look (only on Firefox; other browsers don't support this, I'm afraid), go to View (you may have to press Alt to show the Menu Bar or enable it from the right-click menu around the top of the Firefox window), Page Style. The normal CSS is labelled as "Standard CSS", whereas this is "Barebones CSS". Enabling that will disable all other CSS, save for in-line stuff on certain pages and barebones.css itself. I hope to eventually set something up to auto-enable it if a sufficiently old browser is viewing the site.

2024-03-23

• I've begun adding tags to the works page. It'll probably be a bit until everything is tagged, since I anticipate doing them a handful at a time. They will function similarly to the labels on Blogspot, though with several omitted since they appear elsewhere on the table (universe, commissioned by whoever, etc). I also want to avoid taking up too much space unnecessarily, since that table is already too wide for both my computer and phone--odds are that's also the case for your devices. I hope to figure out a solution for that eventually.
• Fandom wikis have a viable fix built in, making a wide table have a horizontal scroll function, making it not exceed the device/viewport's maximum width and cause issues. This is, best I can tell, dark magic that Fandom has access to by way of being pure evil. I'll do some research and try to figure out a solution, either mimicking Fandom's approach or doing something different.

2024-03-03

• I've done some behind-the-scenes cleaning.
• CSS files are now within their own folder and the files are no longer prefixed with "style-". Ditto for JavaScript files, only they didn't have prefixes.
• Similarly, my collection of 88x31 buttons are in their own folder and don't have "88x31_" prefixes.
• RealFaviconGenerator.net recommends against explicitly declaring favicon.ico, since browsers beyond Internet Explorer may use that over a more modern PNG or SVG. Browsers know to look for favicon.ico in the root directory of a site, so if it's there, it's all good. This is admittedly against the recommendations of the W3C, but I believe it's fine.
• I've revised my apple-touch-icon to allow for more safe space around the triangle thingy, using Maskable.app to get the scaling right.
• I've also remade my 88x31 button into an SVG. It's not an exact reproduction, but it's very close, and I'm quite proud of how it turned out.
• Notably, I encountered an issue with Inkscape's variable font functionality--I couldn't set Recursive's MONO parameter to 0.51 like I have it on my website, so I used a static, fully mono, still linear (as opposed to casual), 700 weight version of the font. The difference is most apparent in the serifs of the 'l'--they're longer in fully-mono mode.
• I also have a PNG version handy, in case people don't want to deal with SVGs on their own sites.

2024-02-20

• Several URLs have been tweaked to be more consistent. The list of changes and the rules I'll be following moving forward are listed here. Please note that they're all within the works folder.

2024-02-05

• I've given color.css a renovation, most prominently adding OKLCH colors for every value. Conventional hex/RGBA values are still present (the new ones are identical, save for one that's been ever so slightly tweaked), to serve as fallbacks on the off-chance someone with an incompatible browser happens upon my site.

2024-02-02

• Then put your little hand in mine.... I've given my site's <head> section a makeover, including:
• The assortment of favicons mentioned previously
• The meta name="author" space now reads "Delta7447" on every page, though I believe that space doesn't really do anything.
• The og:image line used to attach an image to a link preview on social media like Discord, Twitter, Facebook, etc has been removed--though outright omitting the line leads to Neocities using a screenshot of the page in that capacity. So I have the line present but pointing to blank space, making it clear that I want no image, rather than "do whatever". I felt that having my logo accompany every link to my site is a bit vain. And since I'm an author first and foremost, a text-only preview makes sense, right?
• Each page has a set of meta name="keywords" now, which should help with SEO.
• Also on the SEO front, I've added <meta name="rating" content="adult"> to every page of my site, which should indicate to search engines that this is a big boy site; people with SafeSearch on or whatever shouldn't find it in their results.

2024-01-25

• I neglected to mention some days ago that I've begun refining the code on my site. It has come to my attention that neglecting to close tags like <p> and <li> technically works and isn't incorrect, but is a bad habit to be in. Doing so relies on a browser to guess where the closing tags should go. In my experience it's consistently correct with at least modern Firefox, but different/older browsers may not necessarily produce the same results.
• The sheer size and text-heavy nature of my site (even in its currently incomplete state) means adding closing tags to everything that's missing them will take a while. Fortunately, I've found an online tool for pointing out exactly this sort of thing. It doesn't automatically correct the errors it finds like I had hoped, but it's definitely better than nothing. Thanks, Alicia Ramirez!

2024-01-23

• With some adjustments made in Inkscape and the assistance of SVGOMG to clean up the code, I've refined the SVGs of my logo.
• Additionally, I've used those improved SVGs to make more versatile favicons. Per RealFaviconGenerator.net, I now have:
• favicon.svg
• favicon.png, since Safari doesn't support SVGs as favicons.
• apple-touch-icon.png (and apple-touch-icon.svg)
• site.webmanifest (though it may be configured incorrectly, since the site says I'm missing a high resolution icon and that there's no icon for Android Chrome)
• browserconfig.xml (Again, it may also be configured incorrectly, since it doesn't recognize the tile icon despite it being included and referred to)
• Addendum 2024-01-29: this is intended for Windows 8 and Internet Explorer 10/11, both of which aren't supported anymore. I've made the executive decision to nix them for simplicity's sake.
• A monochromatic safari-pinned-tab.svg (Removing the white center from my logo to make it an irregular hexagon that's close to a triangle with its points cut off. This design should be also used for Windows 8/10 and Internet Explorer (browserconfig.xml), but like I said, it's not working right currently)
• And Ol' Reliable, favicon.ico
• To clarify, these are currently only set up on the index page, but I do intend to set them up site-wide.

2024-01-21

• Over the holidays, I got covid. My symptoms were pretty mild, all things considered, but it wasn't exactly a good time. As of 01-13, I've recovered and gotten a subsequent negative test.
• Wake up babe, new Delta7447 lore just dropped I've expanded my about me page a bit, including the juicy details of how I found my way to the Omnitopia Discord server and began publicly posting my works to the world.

2023-12-29

• I've renovated base.css, organizing it while also ensuring all its everything still works.
• I also have a simple bit of JavaScript equipped on some pages to allow mobile users to view <abbr> title text. The element's default functionality assumes a mouse is hovering over to view the text in question, which is impossible on a touchscreen without some sort of special app or emulated functionality. This will hopefully remove the need for that sort of accommodation, but it will require JavaScript to be enabled. Those elements will change your cursor to pointer mode upon hovering, as if it's a link. And this is an organic example.

2023-12-06

• I've implemented some Javascript on the works page, giving a cumulative word count and estimated reading time for each work, assuming an averaged average of 217 (and change) WPM. I confess I used ChatGPT to get the code down (I'm very new to JavaScript, I'm afraid), but I believe I'm gradually learning how to do this sort of thing, albeit on a very basic level.

2023-11-27

• Things are still hectic, though I hope they will calm down in the coming days, now that Thanksgiving has passed.
• I've switched the font used for story text from Bitter Pro to Bitter. See also the fonts section of my about site page for more.

2023-11-09

• Continuing work I began yesterday, I've added container elements to distinguish page <header>s from separate works (<article>) or chapters (<section>). Likewise, the previously generic <div class="toc"> element used for tables of contents is now <nav class="toc">--visually identical but taking advantage of fancy HTML semantics, for the sake of screen readers and so on.

2023-11-07

• I've officially phased out index2 in favor of nav.

2023-11-01

• My fetish dislikes page has been implemented. Due to its relatively short length compared to my likes, getting it in didn't take particularly long. For the time being, I'll leave the three pages as is, but I do hope to consolidate them into one at some point. That will be tested on a separate page before being implemented properly, probably adding the unified table to the root fetishes intro page.
• In contrast, I may eventually split this page into subpages to help with navigation. At some point the table of contents will get ridiculously long, but I think the way to mitigate that is to only include links to the first entries of a given month. An individual entry is generally pretty short, so you could simply scroll a little bit to find a given day, even if it doesn't have a link directly to it.
• If you know the date of a given entry, its <a id=...> thing is still present, so you could manually add "#2023-10-20" to the URL to reach that corresponding entry.
• My work availability has been revised effective today, both to improve my general work-life balance and to give me more time and energy for actually getting my commissions done.

2023-10-28

• Irresistible uses colored text to indicate who's speaking--since the three girls are blue/pink/purple color coded, which in turn corresponds to their glowing eyes. With the light/dark theme toggle, however, a single set color for each of them would result in poor contrast for one mode or the other. Not anymore, I'm pleased to report. I've expanded the technique used on style-color.css with the handy <style> tag, adding a pair of colors for each girl, ensuring good contrast across the board.

2023-10-27

• Added the neutral portion of my fetishes list. I'm tentatively thinking of consolidating all three lists into one, color-coding them to indicate like/neutral/dislike. There'd also be a column on the far left also saying so (either just reading "Like/Neutral/Dislike" or possibly using emoji: 💚😐😡), not unlike the Type column on my works page.
• This would allow me to more easily switch my stance on a given fetish, which I was compelled to do twice while adding the neutrals in (my interest in otoko no ko's and the inverse dansou no reijin have improved--I may be bi, or perhaps less concerned about gender)
• I'll hold off on actually merging the lists together until I've added the dislikes page. I'd also like to give my tables some fancy JavaScript-enabled filter/search and sorting functionality. Wikipedia and Fandom wikis have the latter, and given the size of some of my tables, the former would be helpful.

2023-10-26

• Things have been kinda hectic lately, so I haven't been able to make much commission progress. I was admittedly afraid this might happen when I re-opened commissions, since I have a job now, whereas the last time I accepted commissions was late 2021.
• I've added some more to my about me page.

2023-10-24

• Added my logo to the lower-right corner of every page on the site. Clicking it will lead to my nav page.
• Also did some housekeeping to various pages, ensuring everything has an <h1> header at the top and subsections use <h2>.
• The ever-janky index page has gotten a bit of revision, bringing it a bit more in line with the nav page.

2023-10-20

• GhostlyGarden's commission is complete and live, titled A Strikingly Vivid Reality

2023-10-15

• GhostlyGardener's commission is a bit behind schedule. I had intended to have it out by the end of last week (i.e. yesterday Saturday, 2023-10-14), but it didn't quite pan out. It's underwent some rewrites (for the better, I think), and should be out soon.
• A couple of my captions have made it onto some esoteric boorus. I most certainly don't mind that, so long as credit is given. So far, with Taste of Divinity and Totally Just a Fishing Maid, they have indeed given me sufficient credit. To that end, I've included links to those pages on my works list.
• It's not unheard of for my captions to make it onto 4chan threads here and there. I don't anticipate bothering to document those, but as long as credit is given, I don't mind it at all.

2023-10-12

• Made some adjustments to the Love Live page, including:
• Switching Just Passing Through to be in the Love Live universe rather than Idolmaster, since Anya (from Idolmaster) rather explicitly appears in Riko's (from Love Live) room, which one would assume is in her own universe.
• Stargazing and Chill includes a brief allusion to a doujinshi I'm rather fond of. The events in it are treated as canon, so I've added a link to it in the page's table of contents.
• I'm a bit behind on completing GhostlyGardener's commission, but I hope to have it finished soon. My initial goal was getting it done by the end of this week (Saturday the 14th or sooner), but I think I can still make that happen, or at least come close.

2023-10-10

• GhostlyGardener's commission has entered the beta reading phase, and its accompanying picture has gotten the usual edits. I think I like the plan of focusing on one commission at a time--I'll continue that practice for the foreseeable future.

2023-10-05

• Created this page. There is admittedly more that happened before today, but I didn't write it down 🤷
• Working towards phasing out index2 in favor of nav, since the latter does everything the former does, only better
• On the commissions front, my three slots are all filled--which happened a lot faster than I expected. It's weird being vaguely somewhat maybe kinda borderline if-you-squint-really-hard famous.
• Kampmichi's involves two of their OCs indulging in lots of omni-tier sex
• JayMercury and Loamlife had very similar requests, so I spoke with them and turned it into a co-venture--they both have a say and will split the commission's final cost evenly. They want something expanding on the setting introduced in The Project (no Neocities link now, since I plan on posting the caption alongside this expanded story on the same page)
• GhostlyGardener also requested something that expands on an existing caption of mine, only regarding Your New Mistress (ditto). It's quickly turning out to be rather long for a caption, but it may easily get trimmed down--we'll see.
• Commented out the buttons on the custom scrollbar (not visible on Firefox for whatever reason), since they aren't really necessary and I haven't been able to add arrows to the buttons like a scrollbar would traditionally include.