temporary or time-limited or automatically removable logs?

darwin
  • Изменен

I've always preferred the original (dating from 1988) Internet Relay Chat (IRC) because is a Free/Libre/Opensource Software (FLS, OSS, FOSS, FLOSS) decentralized open protocol, over centralized (single point of failure) proprietary/closed-source software like Discord, but some younger friends use Discord more but we might relay their rooms with IRC with a bot. However, virtually all IRC operators (ops) are against permanent logs, for trust & safety/privacy reasons (I originally submitted this a 'trust & safety' request.) Could Discord add option for a room/area to only have temporary / time-limited logs and delete all history preceding a certain time limit? Seems people working on main relay bot probably won't add feature (maybe because won't deal with quoted chat; ) each/any chat service would have to themselves.

0

Комментарии

1 комментарий

Дата Голоса
  • Jose Richards

     The redo log is a disk-based data structure used during crash recovery to correct data written by incomplete transactions. During normal operations, the redo log encodes requests to change table data that result from SQL statements or low-level API calls. Modifications that did not finish updating data files before an unexpected shutdown are replayed automatically during initialization and before connections are accepted. For information about the role of the redo log in crash recovery, see Section 15.18.2, “InnoDB Recovery”.

    The redo log is physically represented on disk by redo log files. Data that is written to redo log files is encoded in terms of records affected, and this data is collectively referred to as redo. The passage of data through redo log files is represented by an ever-increasing LSN value. Redo log data is appended as data modifications occur, and the oldest data is truncated as the checkpoint progresses. 

    0

Войдите в службу, чтобы оставить комментарий.