広告効果測定
同意した場合のみX Pixelを使用します。
メールアドレスや制作内容は送信しません。
Some content is automatically translated from Japanese. Untranslated sections are shown in the original language.
TIMELINE ARCHIVE
Follow public updates, creation logs, and related releases from newest to oldest.
Updates
16
Creation logs
6
Related releases
0
TIMELINE
Public records are arranged in one timeline without duplicating the same event.
Oct 26 18:30
Implemented three user requests (textbook font for Chromebook, series summary of works, writing fields for essays/stories), and unified the UI notation to "Series" for the production release. Additionally, made revisions to the import of the read API and synchronized the main, resulting in production revision tategaki-00140-hww (main 26e6c6d).
To respond to specific requests from the public readers.
Oct 23 07:48
In response to security measures, we have implemented Google login. Additionally, we have performed updates to address the RCE vulnerability in node.js.
Due to the PHP incident, various AI-related vulnerabilities have emerged.
Sep 25 20:33
You can now send free support messages from the work page, and they will also be recorded in the author's history. I have also adjusted the display of the writing background image, but I have not confirmed that either has been reflected in the production.
Record the time for each database operation in the management screen to determine whether delays are occurring on the Turso side or along the connection path.
Sep 24 08:13
The title formatting as requested by users, the reflection of bold text in published works, and the implementation of background images for each work have been put into production. The background now appears in reading mode as well, and the issue with the images being too light and washed out has also been fixed.
I thought it would be easier to make the next improvement decisions by reflecting feedback from actual users first.
I will open the piece with the background in the actual performance and check the intensity and readability of the text.
How do you feel about the balance between the readability of the text and the atmosphere when there is a background image on the reading screen?
Sep 14 20:50
When releasing works from the same cloud manuscript, I updated the currently published page instead of creating a new one. I consolidated any works that had been mistakenly published twice, and restored the stories that had different manuscripts even if they shared the same title.
Even if the titles are similar, there is a possibility that the author is releasing different works. Please only update when they are published from the same manuscript.
Sep 8 18:57
Even if not publicly shared, I've added a record of the amount written. On the author's page, the daily word count is not visible; only the achievements are displayed. You can review your own records from the coffee icon at the top of the screen, and I've made it possible to show a small indication of what else you might be writing.
When I share my daily word count with others, I can see the activities of those who haven't published their works. Since the manuscript's saved history contains the most recent full text, I've decided not to use it to track the day's writing volume.
Check if the writing record and the current writing presence look natural on the actual screen.
Sep 6 02:10
Unlogged drafts are left in the browser without guidance. Once logged in, they are moved to a temporary document and handled for cloud storage. While logged in, no local writes are performed. Operations to revert to the previous state and to add headings from within the text have also been included.
Notifications are annoying. Local saves during login are disruptive and can lead to bugs. I believe that drafts that naturally remain before logging in should be moved as temporary documents and saved to the cloud once logged in.
Check on the actual screen whether the draft before logging in remains in the cloud via the temporary document after logging in.
Aug 20 23:36
Enabled update announcements to be registered from the admin screen. Users can switch among WYSIWYG editing, HTML, and preview tabs, and can also insert images. Drafts and published items are separated; published announcements can be viewed by both signed-in and anonymous visitors from the bell icon to the left of the account name. Only the item whose body is opened is marked as read, and users can also mark everything as read.
Aug 13 06:42
Added “Read” and the save status to the persistent mobile header. A button in the lower right now opens a bottom sheet with New Document and “Your Works.” The vertical-writing cursor was too short and crowded the text, while in continuous mode deleting sometimes failed to move the cursor or remove characters, so changes were made immediately to address those problems.
On a smartphone in continuous mode, confirm that characters are deleted correctly and that the blinking cursor has the right shape.
Aug 5 16:59
Removed the “Tip” button from the header and changed the tipping guidance modal to appear automatically only once, like the service introduction. After closing it, users can reopen it from “Receive Support” in Help. The “Tips and Earnings…” item remains in the edit menu.
Use a small test tip to confirm that the corrected flow reaches the received state.
Jul 29 15:14
Investigated a tip that appeared to have arrived even though Stripe had no record of it, and found that the payment had expired without completing. Also fixed a recipient-side defect, changed the earnings screen to show only completed history, and kept the full history available in the admin screen. The method for building tipping was also packaged as a reusable skill that can be moved to other services.
If incomplete amounts appear on the earnings screen, they look as though they have arrived. I wanted the Creator view to retain only completed payments while letting operations track the entire process.
Use a small test tip to confirm that the corrected flow reaches the received state.
Jul 28 08:04
On the Read page (/read), the growing set of categories is no longer shown all at once. The page now limits the initial view to featured and new work plus up to six categories, then loads more on scroll. A left-side search panel can filter by author, category, publication date, character count, and other conditions, and the implementation is complete.
There are already around 150 users, so loading every work into the browser from the start would become heavy. The page was changed to fetch only what is needed.
Test the changes to the Read page (/read) locally.
Jul 15 18:00
Organized the status of incoming requests and adjusted the list so completed items no longer appear at the front.
Added a separate “Completed” state so that only items still in progress appear first.
So that we can focus on the requests being handled now while still preserving completed records.
Jul 14 14:02
Improved descriptions and metadata so published work is easier to understand in search. The visible screen remains unchanged; only discoverability was added.
Improved discoverability by adding search-oriented descriptions rather than changing the screen.
Prioritized passing the existing titles and summaries into search results.
Jul 11 01:32
Refined the feel of vertical writing while adding author pages and a tipping path. There is no follow feature; support is centered on tips.
After organizing the reading entry points, improved the writing experience and added paths for reaching and supporting authors.
Because rather than adding more features, I want to preserve the pleasure of writing vertically and a single clear path for work to reach people.
Complete the tip-receiving setup in production and confirm that money can actually be transferred.
Do the author page and tipping make it feel like you can follow this person’s work even without a follow feature?
Jul 2 17:20
The “Read” page is being reshaped around easy entry points for finding work. The top page will show a limited selection, while people who want more can continue to lists by newest, popular, or hashtag.
Changed from holding the entire catalog on one page to showing it by section and letting readers dig deeper on separate pages. Classification at posting time is also moving away from fixed categories and toward hashtags.
Because I want readers to be able to find work without getting lost even as the catalog grows.
Post real work with hashtags and review how the groupings form and how easy search is to use.
Does finding work through hashtags feel intuitive?
7 2026 1
The tategaki.jp project was started.
12 years of engineering experience.
