6/20/2023 0 Comments Transat hesperides ibiza![]() You could also send a snapshot to a friend so they can run an application from a given point on their machine. If you do snapshots + live reloading there are tons of other things you can do (e.g. live patching and replaying of functions while debugging). Must identify a useability limit and upper bound on how long a user is willing to wait before getting an email address.Out of curiosity, are you planning on (progressively, slowly) rolling your own JIT, or using something like DynASM ( ), libFirm ( ), or some other preexisting thing (eg ) in the space?įWIW, I understand that LuaJIT gets some of its insane real-world performance from a JIT and VM design that's effectively shrink-wrapped around Lua semantics/intrinsics - it's not general-purpose. Users with specific aim of getting an email address and general browsers have different aims.What is the aim of the user when browsing the site? In a discussion with Jon Oberlander today after lectures he suggested:ġ. Their user experience expectations will adjust according to their desired goals. when viewing an academics homepage, most users would be interested in finding out what research areas are, what papers are etc., not in trying to achieve commuinication with the page owner. As such, a browser will probably tolerate, not be bothered about any delays. Explaining why and how long user must wait for information may increase their tolerance for waiting.However, when a user has specific intention to get email address(or contact site owner), they will want get information fast. Incorporating something like "this is an anti-spam measure. Google keywords: latencies, user tolerance.Although may not have publish figures, may hint to sources of primary research that's uncited! Imperical research: how long is a user willing to wait before their expectations are frustated: it will take XXX seconds for the email address to appear" this into the design may increase useability.Ģ. Project Musings: Honeypot Started reading Honeypots by Lance Spitzner (Addison-Wesley, 2003) to gather ideas on how to improve on the existing spam honeypot. JavaScript must have these characteristics to deter the attacker Whilst may not be able to know these bounds, as we do not know attackers modus operandi, an estimated bounds maybe useful in identifying a suitable NP complete problem.Must identify way to set/measure reasonable bounds on these?.Can limit attacker machine’s – CPU, Memory or Bandwidth.Mine Sweeper is NP complete (wikipedia).Establishing Upper Resource Bounds on Spammer’s machine #Email obfuscator tool how to Problem must be NP complete – must be no shortcuts to solving the problem i.e.The source code function must be such that.Īttacker must successfully complete execution before they can derive result.# JavaScript Idea (Email address stored in an incomplete private-key) # ![]()
0 Comments
Leave a Reply. |