How do I insert a timestamp in Word for the Web or Google Docs, on a chromebook, via hotkey or voice?

Desired Result:

The desired result is to insert a timestamp (local machine time or whatever) into a “Word for the Web” document or Google Docs document, on a Chromebook, by using: i) a hotkey and/or ii) voice dictation.

Formatting of the timestamp would be nice, but not necessary. Only the time of day is needed, but including the date is good too.

Any alternative solutions would be welcome, outside of Word or Google Docs, so long as it can be accomplished on a Chromebook.

Solutions I have investigated but could not get to work:

  1. Using hotkey or voice dictation to trigger a macro or script. Apparently, neither Word online nor Google Docs supports this.

  2. Google Sheets appears to allow the use of a macro to run a script, but I need this as applied to Word online or Google Docs. Google Sheets is a no-go, unfortunately.

Thank you for help.



post meta – How to save custom fields’ value whenever they change with timestamp?

I have created two custom fields for posts – post owner and post assignee. I want to check the chain of possession throughout the existence of that post along with the timestamp. But, I’m unable to find a way to do so.

I checked into the WordPress post revisions but as far as my understanding, that doesn’t save meta fields out of the box.

I want to create a meta box in the post edit screen and display whoever was the owner/assignee of that post at a particular date and time.

Please help me find the possible ways to do so. Thank you.

time series database – Entries with same timestamp in GridDB

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

timestamp – Can Taproot be used to commit arbitrary data to chain without any additional footprint?

Yes, you can commit to data this way, but there is nothing special about Taproot here.

The Pay-to-Contract construction used to tweak the root key in Taproot is generally usable, and has in fact been used for exactly this purpose. In fact, it is one of the mechanisms used in OpenTimestamps to commit to timestamped data (including a variant sign-to-contract which makes a signature commit to data rather than a public key). It is also used in Blockstream’s Liquid pegin mechanism, where transfers from Bitcoin to Liquid pay to an address derived using a tweaked key of the federation, which commits to the transfer information.

In fact, using an additional leaf in Taproot for this is overkill, and would inevitably increase the depth in the Merkle tree for at least one other leaf – resulting in increased spending cost. Just using pay-to-contract or sign-to-contract directly on one of the public keys involved can be done with zero cost to on-chain spending policies.

Would this not significantly reduce the cost of services like colored coins, timestamping services, etc, which commit their data directly onto the chain?

Decent timestamping services already use better techniques.

For colored coins it depends whether they just need timestamping or actual publication of data. My understanding is that it’s generally the latter (as otherwise, they need another censorship-resistant channel to transfer the actual data, which could then probably be used directly).

GOOGLEFINANCE in Google Sheets to get high & low and timestamp of high/low from the day i took trade

I wanted to keep a track of high/low of a trade from the day i took the trade.
for a day i am able to get high/low but how to get from the date i took my trade which is stored in one of cell.


magento2 – How to make Magento 2 log timestamp follows locale configuration?

How can i make exception.log, system.log, , debug.log or any other log inside var/log which is generated from magento 2 follows the configuration timestamp, right now it is showing the utc timezon in the log timezone, how can I set ti to UTC+5 just like my locale configuration in Magento 2 ?

I’m using Magento ver2.4.1

postgresql – Converting DATE and TIME Ingeters to Timestamp in postgres

I am trying to get a Timestamp by combining Date and Time columns in my PostgresQL database and am running into errors. Here is what I have.

| StartDate | StartTime |
| 20210301  | 18000000  |
| 20210302  | 19000000  |
| 20210303  | 20000000  |

Here is what I want

| StartDate | StartTime | StartStamp            |
| 20210301  | 18000000  | 2021-03-01 18:00:00.0 |
| 20210302  | 19000000  | 2021-03-02 19:00:00.0 |
| 20210303  | 20000000  | 2021-03-03 20:00:00.0 |

In MySQL I would be able to get this by using the following sql

SELECT  STR_TO_DATE(concat(LPAD("STARTDT", 8, '0'),'-', LEFT(LPAD("STARTTM", 8, '0'),6)),'%Y%m%d-%H%i%s') AS StartStamp
From Table1 

To get that in postgres, I’ve tried to CAST(STARTDT as DATE) but that resulted in an error. I’ve tried TO_DATE() but that also did not work. Is there a way to get the timestamp in PostgresQL ?

SQL Trigger – how to update timestamp column of a table when any changes made in another table?

I want to keep record of any change made in one table and update the time of that change made in another table( in this table I have one timestamp column where I want to update the time)

t sql – How do I convert a TIMESTAMP to a BIGINT in Azure Synapse

What’s the best way to convert a TIMESTAMP to a BIGINT In Azure Synapse. I tried this (which works) but seems clumsy. Is there a better, more concise and efficient way of doing the same thing?

           CONVERT(CHAR(8), CURRENT_TIMESTAMP, 112) + 

node.js – Javascript – How to properly parse a unix timestamp with milliseconds

I’m receiving a unix timestamp (example: 1615184467653) and I try to parse it with the npm package date-fns. It seems that the package can only handle simple unix timestamps without milliseconds. I also tried the npm package moment but it delivers the same results.

const moment = require('moment');
const { fromUnixTime, formatISO } = require('date-fns');

const now =;


// 53155-12-09T15:59:27+01:00
// +053155-12-09T14:59:27.000Z

What is currently the best practice in parsing a unix timestamp with milliseconds in JavaScript/ NodeJS? All questions that I found on StackOverFlow only talk about simple unix timestamps like 1330515905 and not about the longer format with milliseconds like 1615184467653.