但第二个问题却让我束手无措

事件处理数据的变化，代码的变化呢？ 我们可以将这里视为三种广泛的代码更改：新功能、缺陷修复和时序逻辑。

构建事件处理程序逻辑

Complete Rebuild：我们可以完全丢弃应用程序状态并通过在空应用程序上重新运行事件日志中的事件来重建它。 时间查询：我们可以在任何时间点确定应用程序的状态。从概念上讲，我们通过从空白状态开始并将事件重新运行到特定时间或事件来做到这一点。我们可以通过考虑多个时间线（类似于版本控制系统中的分支）来进一步实现这一点。 事件重播：如果我们发现过去的事件不正确，我们可以通过反转它和以后的事件来计算后果，然后重播新的事件和以后的事件。（或者实际上是通过丢弃应用程序状态并按顺序使用正确事件重播所有事件。）相同的技术可以处理以错误顺序接收的事件——这是与异步消息通信的系统的常见问题。

This eventof cognition, or better yet the event of making sense – the primal mental event, allencompassing, both forming and dissolving boundaries, multiple4 and affirming, Ifind to be the proper stage to present my research

to do our own work to develop our own teams to 00:13:48 grow our own networks so based on that we decided to organize a movement to build these kinds of new models to arrive at much more sustainable public goods funding not just sustainable ideally regenerative 00:14:01 systems with possible externalities they're not just sustaining themselves at some level but actually creating a lot more value around themselves and we hope to also create structures for much better value alignment within these networks 00:14:13 so we decided to throw an event uh last year uh so it's less than a year ago um there's probably a number of other people that helped put this on if um uh i in my memory yesterday i remembered a set of folks who are here uh which i 00:14:26 want to thank for for driving this and really creating this this event but it really takes a village to put this on especially the pl events team um uh and many others who have helped uh and since then we've now had uh three 00:14:37 events two virtual one and one in person and we're scaling the community in the size of the conversations the um systems that we're reviewing the mechanisms that we're exploring the studies that we're doing and so on uh so 00:14:50 in this conference we've gone from you know 11 18 talks and now 56 really encourage you to like attend all of them simultaneously of course you can do that of course you can later in time they're all recorded 00:15:02 and we're also very fortunate to be working with a whole bunch of other folks in the ecosystem building out the broader public goods movement in the blockchain space great uh 00:15:15 thanks to the github community and shelling point and many other manila groups that are very focused on building regenerative structures so all of this leaves me uh very hopeful um you know our impact so far has been 00:15:28 to explore a set of funding mechanisms here's a few uh that i pulled from the youtube uh channel a bunch of these mechanisms are explained explaining explored and so on some of them also have kind of experimental review still early days so 00:15:41 a lot of it is still kind of not very systematic not very well experimented upon and so on but i'd love to kind of crank that up and get to drastically better study to the point where we can like analyze these systems with the same 00:15:53 level of rigor that we analyze things like network protocols or like hardware devices and things like that we've also [Music] sort of revived the impact certificates um 00:16:05 idea and and field we've um gotten to explore a number of novel entity types i know that a few of these are actually getting booted up now which is really awesome impact for just a few months of talking about things um and we've 00:16:19 created some uh we've talked about some coordination systems that could be um extremely useful i think this is a very promising area but probably under under um understudied and an area that that is 00:16:31 maybe harder or seems um diffic much more difficult to get traction on so it doesn't get studied as much

The focus event does not bubble in Internet Explorer. Therefore, scripts that rely on event delegation with the focus event will not work consistently across browsers. As of version 1.4.2, however, jQuery works around this limitation by mapping focus to the focusin event in its event delegation methods, .live() and .delegate().

$('input[name=myInput]').change(function() { ... });1. 在输入框内容变化的时候不会触发change，当鼠标在其他地方点一下才会触发

No need to construct strings that then need to be deconstructed later.

I believe we need the break free of these anachronistic designs and use event loggers, not message loggers

µ/log's idea is to replace the "3 Pillars of Observability" with a more fundamental concept: "the event"

Event-based data is easy to index, search, augment, aggregate and visualise therefore can easily replace traditional logs, metrics and traces.

This was great for passing things between services where fire-and-forget was adequate.

In this example, Bigipedia informs us that the DOI is referenced by the article page. Note that because the subject is not a DOI, the metadata must be supplied in the subj key. $ curl "https://bus.eventdata.crossref.org/events" \ --verbose \ -H "Content-Type: application/json" \ -H "Authorization: Token token=591df7a9-5b32-4f1a-b23c-d54c19adf3fe" \ -X POST \ --data '{"id": "dbba925e-b47c-4732-a27b-0063040c079d", "source_token": "b1bba157-ab5b-4cb8-9ac8-4beb2d6405ff", "subj_id": "http://bigipedia.com/pages/Chianto", "obj_id": "https://doi.org/10.3403/30164641u", "relation_type_id": "references", "source_id": "bigipedia", "license: "https://creativecommons.org/publicdomain/zero/1.0/", "subj": {"title": "Chianto", "issued": "2016-01-02", "URL": "http://bigipedia.com/pages/Chianto"}}'

El púlsar binario PSR J0737 como banco de pruebas de la relatividad general Por Francisco R. Villatoro, el 16 diciembre, 2021. Categoría(s): Astronomía • Ciencia • Física • Noticias • Physics • Relatividad • Science ✎ 3

Evidence Record Creates observations of type landing-page-url for annotates relation types. Creates observations of type plaintext for discusses relation types.

Discusses: { "license": "https://creativecommons.org/publicdomain/zero/1.0/", "obj_id": "https://doi.org/10.1146/annurev.earth.32.082503.144359", "source_token": "8075957f-e0da-405f-9eee-7f35519d7c4c", "occurred_at": "2015-05-11T04:03:44Z", "subj_id": "https://hypothes.is/a/qNv_Ei5ZSnWOWO54GXdFPA", "id": "00054d54-7f35-4557-b083-7fa1f028856d", "evidence_record": "https://evidence.eventdata.crossref.org/evidence/20170413-hypothesis-a37bc9bf-1dc0-4c8a-b943-2e14beb4de6f", "terms": "https://doi.org/10.13003/CED-terms-of-use", "action": "add", "subj": { "pid": "https://hypothes.is/a/qNv_Ei5ZSnWOWO54GXdFPA", "json-url": "https://hypothes.is/api/annotations/qNv_Ei5ZSnWOWO54GXdFPA", "url": "https://hyp.is/qNv_Ei5ZSnWOWO54GXdFPA/www.cnn.com/2015/05/05/opinions/sutter-sea-level-climate/#", "type": "annotation", "title": "The various scenarios presented should be specified as being global averages of expected sea level rise. The sea level rise observed locally will vary significantly, due to a lot of different geophysical factors.", "issued": "2015-05-11T04:03:44Z" }, "source_id": "hypothesis", "obj": { "pid": "https://doi.org/10.1146/annurev.earth.32.082503.144359", "url": "https://doi.org/10.1146/annurev.earth.32.082503.144359" }, "timestamp": "2017-04-13T10:40:18Z", "relation_type_id": "discusses" }

Annotates: { "license": "https://creativecommons.org/publicdomain/zero/1.0/", "obj_id": "https://doi.org/10.1007/bfb0105342", "source_token": "8075957f-e0da-405f-9eee-7f35519d7c4c", "occurred_at": "2015-11-04T06:30:10Z", "subj_id": "https://hypothes.is/a/NrIw4KlKTwa7MzbTrMAyjw", "id": "00044ac9-d729-4d3f-a2c8-618bcdf1d252", "evidence_record": "https://evidence.eventdata.crossref.org/evidence/20170412-hypothesis-de560308-e500-4c55-ba28-799d7b272039", "terms": "https://doi.org/10.13003/CED-terms-of-use", "action": "add", "subj": { "pid": "https://hypothes.is/a/NrIw4KlKTwa7MzbTrMAyjw", "json-url": "https://hypothes.is/api/annotations/NrIw4KlKTwa7MzbTrMAyjw", "url": "https://hyp.is/NrIw4KlKTwa7MzbTrMAyjw/arxiv.org/abs/quant-ph/9803052", "type": "annotation", "title": "[This article](http://arxiv.org/abs/quant-ph/9803052) was referenced by [\"Decoherence\"](http://web.mit.edu/redingtn/www/netadv/Xdecoherenc.html) on Sunday, September 25 2005.", "issued": "2015-11-04T06:30:10Z" }, "source_id": "hypothesis", "obj": { "pid": "https://doi.org/10.1007/bfb0105342", "url": "http://arxiv.org/abs/quant-ph/9803052" }, "timestamp": "2017-04-12T07:16:20Z", "relation_type_id": "annotates" }

looks in the text for links to registered content

It looks for two things: the annotation of registered content (for example Article Landing Pages) and the mentioning of registered content (for example DOIs) in the text of annotations.

The Hypothes.is Agent monitors annotations

Crossref Membership rules #7 state that: You must have your DOIs resolve to a page containing complete bibliographic information for the content with a link to — or information about — getting the full text of the content. Where publishers break these rules, we will alert them.

It's always not one-to-one DOIs can be assigned to books and book chapters, articles and figures. Each Agent will do its job as accurately as possible, with minimal cleaning-up, which could affect interpretation. This means that if someone tweets the DOI for a figure within an article, we will record that figure's DOI. If they tweet the landing page URL for that figure, we will do our best to match it to a DOI. Depending on the method used, and what the publisher landing page tells us, we may match the article's DOI or the figure's DOI. Sometimes two pages may claim to be about the same DOI. This could happen if a publisher runs two different sites about the same content. It's also possible that a landing page has no DOI metadata, so we can't match it to an Event. The reverse is true: sometimes two DOIs point to the same landing page. This can happen by accident. It is rare, but does happen. This has no material effect on the current methods for reporting Events.

Matching also varies from publisher to publisher. For some landing page domains we can easily match the DOI. For some we need to do a bit more work. For others, it's impossible.

We maintain a list of domain names that belong to publishers (see the Artifact page for more information) and track and query for those domains. When we see a URL that could be a landing page, we attempt to match it to a DOI.

Every Agent will attempt to match registered content items in as broad a manner as possible by looking for linked and unlinked DOIs and Article Landing Page URLs.

They could use a hyperlinked DOI (one you can click), or a plain-text DOI (one you can't click). They could also use the Article Landing Page (the page you get to when you click on a DOI). Every source is different: we tend to see most people using Article Landing Pages on Twitter, but on Wikipedia DOIs are frequently used.

Event Data Agents are on the look out for links to registered content items, but people on the Web use a variety of methods to refer to them.

www.scientificamerican.com: 6768,

Every Event starts its journey somewhere, usually in an external source. Data from that external source is processed and analyzed

the subject of the event, e.g. Wikipedia article on Fish the type of the relation, e.g. "references" the object of the event, e.g. article with DOI 10.5555/12345678

Every time we notice that there is a new relationship between a piece of registered content and something out in the web, we record that as an individual Event.

Each web source is referred to as a 'data contributor'. The Events, and all original data from the data contributor, are available via an API.

When a relationship is observed

a registered content item (that is, content that has been assigned a DOI by Crossref or DataCite)

This data is of interest to a wide range of people: Publishers may want to know how their articles are being shared, authors might want to know when people are talking about their articles, researchers may want to conduct bibliometrics research. And that's just the obvious uses.

The Event Data service captures this activity and acts as a hub for the storage and distribution of this data. The service provides a record of instances where research has been bookmarked, linked, liked, shared, referenced, commented on etc, beyond publisher platforms. For example, when datasets are linked to articles, articles are mentioned on social media or referenced in Wikipedia.

this happens with getClient and setClient because it is a svelte context which is only available at component initialization (construction) and cannot be in an event handler.

Datafication, the authors argued, involves much more than converting symbolic materialinto digital form, for it is datafication, not digitization, that “made [digital] text indexable andthus searchable”

Events AAA and BBB are mutually exclusive (cannot both occur at once) if they have no elements in common.

The complement of an event AAA in a sample space SSS, denoted AcAcA^c, is the collection of all outcomes in SSS that are not elements of the set AAA. It corresponds to negating any description in words of the event AAA.

Most “legacy” operations don’t have this output, yet. However, the Model() macro now supports this terminus.

we head straight into an additional terminus, or end event as it’s called in BPMN

Note that the path ends in its very own end, signalizing a new end state, or outcome. The end’s semantic is :with_cc.

What I think is happening is that instantiating the component is immediately running the $: reactive code, which dispatches the event synchronously, before the parent component attaches the listener.

Knowing exactly what happens in your application can mean the difference between feeling in full control or experiencing deep frustration. Personally, unknowns drive me crazy, which in turn often leads to all sorts of experiments and/or debug sessions.

It's more powerful to have them happen in definition order, because this lets you intercept thing in event handlers or in actions.

beforeUpdate(async () => { console.log('the component is about to update'); await tick(); console.log('the component just updated'); });

“Once” handlers Say a button does something pretty darn important, like submitting a payment. It would be pretty scary if it was programmed such that clicking the button multiple times submitted multiple payment requests. It is situations like this where you would attach a click handler to a button that only runs once. To make that clear to the user, we’ll disable the button on click as well.

etainee abuse scandal

how naked prisoners being subjected to sexual humiliation by American women

Saad Naif said he saw a prisoner shot dead at Abu Ghraib when he approached the razor wire.

Seeing her lying bound in the sun, the brother angrily started to cross the razor wire ringing his tent, "and they shot him in the shoulder," Naif said.

punished by having rations reduced or withdrawn,

"The Gardens" – a razor-wire enclosure where prisoners were made to lie face down on the burning sand for two or three hours, hands bound.

Sometimes we'd fight the Americans with tent poles. The Americans would come at us behind riot shields, firing plastic bullets and electric pistols (stun guns).

He said two died in the next tent while he was there.

Water was the first concern for internees everywhere, especially as summer temperatures topped 120 degrees. There was never enough to drink and wash with, they said.

ICRC's decision to reduce its Baghdad staff, because of the bombing of its headquarters, may limit its ability to visit detention sites.

organization's policy does not allow any public comment on any abuse or other poor conditions detected

representatives are the only outsiders allowed into the camps

listing and processing of detainees has improved in recent weeks.

In toppling the Saddam government last April, the U.S.-British invasion force inherited a legal vacuum and began incarcerating ordinary criminals with prisoners of war and less well-defined detainees.

In one, four soldiers are accused of beating Iraqi prisoners; in the other, two Marines are charged in connection with an Iraqi's death in detention.

Baghdad airport's overcrowded Camp Cropper, was closed.

riots, punishment in the sun

For example, an event handler callback that can be used to handle both fullscreenchange and fullscreenerror might look like this:

It's possible to have multiple event listeners for the same event

Handlers are normally not suffixed, but instead, they most often have on as the prefix (onClick, onSwipe etc.).

Listeners are often objects, so they are commonly suffixed with Listener.

Event listener and event handler are two terms that cause confusion.

A listener watches for an event to be fired. For example, a KeyListener waits for KeyEvents, a MessageListener waits for messages to arrive on a queue and so on. The handler is responsible for dealing with the event. Normally, listeners and handlers go hand-in-hand. For example, the KeyListener tells the ExitHandler that "the letter Q was pressed" and the handler performs logic such as cleaning up resources and exiting the application gracefully. Similary a ButtonClickListener would tell the same ExitHandler that the "Exit button was clicked". So, in this case you have two different events, two different listeners but a single handler.

The most basic difference is the association Listener is associated with Event Source (Ex: key board) Handler is associated with an Event (Ex: keydown)

enables passive event listeners by default for some events (see list below). It basically will set { passive: true } automatically every time you declare a new event listener.

All standard UI events are forwarded.

(The distinction is conceptually similar to passive versus active event listeners.)

United States soldiers abusing and humiliating Iraqi prisoners.

Part of the functionality that is returned are event handlers. I'd like to avoid needing to manually copy the events over one by one so the hook implementation details are hidden.