<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: leonard-lin</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/leonard-lin.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2025-06-03T04:07:55+00:00</updated><author><name>Simon Willison</name></author><entry><title>Shisa V2 405B: Japan’s Highest Performing LLM</title><link href="https://simonwillison.net/2025/Jun/3/shisa-v2/#atom-tag" rel="alternate"/><published>2025-06-03T04:07:55+00:00</published><updated>2025-06-03T04:07:55+00:00</updated><id>https://simonwillison.net/2025/Jun/3/shisa-v2/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://shisa.ai/posts/shisa-v2-405b/"&gt;Shisa V2 405B: Japan’s Highest Performing LLM&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Leonard Lin and Adam Lensenmayer have been working on &lt;a href="https://shisa.ai/"&gt;Shisa&lt;/a&gt; for a while. They describe their latest release as "Japan's Highest Performing LLM".&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Shisa V2 405B is the highest-performing LLM ever developed in Japan, and surpasses GPT-4 (0603) and GPT-4 Turbo (2024-04-09) in our eval battery. (It also goes toe-to-toe with GPT-4o (2024-11-20) and DeepSeek-V3 (0324) on Japanese MT-Bench!)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This 405B release is a follow-up to the six smaller Shisa v2 models they released &lt;a href="https://shisa.ai/posts/shisa-v2/"&gt;back in April&lt;/a&gt;, which took a similar approach &lt;a href="https://simonwillison.net/2025/Jan/20/deepseek-r1/"&gt;to DeepSeek-R1&lt;/a&gt; in producing different models that each extended different existing base model from Llama, Qwen, Mistral and Phi-4.&lt;/p&gt;
&lt;p&gt;The new 405B model uses Llama 3.1 405B Instruct as a base, and is available under the &lt;a href="https://www.llama.com/llama3_1/license/"&gt;Llama 3.1 community license&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Shisa is a prominent example of &lt;strong&gt;Sovereign AI&lt;/strong&gt; - the ability for nations to build models that reflect their own language and culture:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We strongly believe that it’s important for homegrown AI to be developed both in Japan (and globally!), and not just for the sake of cultural diversity and linguistic preservation, but also for data privacy and security, geopolitical resilience, and ultimately, independence.&lt;/p&gt;
&lt;p&gt;We believe the open-source approach is the only realistic way to achieve sovereignty in AI, not just for Japan, or even for nation states, but for the global community at large.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The accompanying &lt;a href="https://shisa.ai/posts/shisa-v2-405b/#overview-report"&gt;overview report&lt;/a&gt; has some fascinating details:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Training the 405B model was extremely difficult. Only three other groups that we know of: Nous Research, Bllossom, and AI2 have published Llama 405B full fine-tunes. [...] We implemented every optimization at our disposal including: DeepSpeed ZeRO-3 parameter and activation offloading, gradient accumulation, 8-bit paged optimizer, and sequence parallelism. Even so, the 405B model still barely fit within the H100’s memory limits&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;In addition to the new model the Shisa team have published &lt;a href="https://huggingface.co/datasets/shisa-ai/shisa-v2-sharegpt/viewer"&gt;shisa-ai/shisa-v2-sharegpt&lt;/a&gt;, 180,000 records which they describe as "a best-in-class synthetic dataset, freely available for use to improve the Japanese capabilities of any model. Licensed under Apache 2.0".&lt;/p&gt;
&lt;p&gt;An interesting note is that they found that since Shisa out-performs GPT-4 at Japanese that model was no longer able to help with evaluation, so they had to upgrade to GPT-4.1:&lt;/p&gt;
&lt;p&gt;&lt;img alt="Comparison of GPT-4.1 vs GPT-4 as judges showing two radar charts comparing Shisa V2 405B and 70B models on JA MT-Bench benchmarks, with text &amp;quot;Why use GPT-4.1 rather than GPT-4 as a Judge?&amp;quot; and explanation that Shisa models exceed GPT-4 in Japanese performance and GPT-4 cannot accurately distinguish performance differences among stronger models, noting GPT-4.1 applies stricter evaluation criteria for more accurate assessment" src="https://static.simonwillison.net/static/2025/shisa-gpt-4.jpg" /&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llama"&gt;llama&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/fine-tuning"&gt;fine-tuning&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/evals"&gt;evals&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llm-release"&gt;llm-release&lt;/a&gt;&lt;/p&gt;



</summary><category term="leonard-lin"/><category term="translation"/><category term="ai"/><category term="generative-ai"/><category term="llama"/><category term="llms"/><category term="fine-tuning"/><category term="evals"/><category term="llm-release"/></entry><entry><title>An Analysis of Chinese LLM Censorship and Bias with Qwen 2 Instruct</title><link href="https://simonwillison.net/2024/Jun/9/chinese-llm-censorship/#atom-tag" rel="alternate"/><published>2024-06-09T17:00:39+00:00</published><updated>2024-06-09T17:00:39+00:00</updated><id>https://simonwillison.net/2024/Jun/9/chinese-llm-censorship/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://huggingface.co/blog/leonardlin/chinese-llm-censorship-analysis"&gt;An Analysis of Chinese LLM Censorship and Bias with Qwen 2 Instruct&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Qwen2 is &lt;a href="https://qwenlm.github.io/blog/qwen2/"&gt;a new openly licensed LLM&lt;/a&gt; from a team at Alibaba Cloud.&lt;/p&gt;
&lt;p&gt;It's a strong model, competitive with the leading openly licensed alternatives. It's already ranked 15 on &lt;a href="https://chat.lmsys.org/?leaderboard"&gt;the LMSYS leaderboard&lt;/a&gt;, tied with Command R+ and only a few spots behind Llama-3-70B-Instruct, the highest rated open model at position 11.&lt;/p&gt;
&lt;p&gt;Coming from a team in China it has, unsurprisingly, been trained with Chinese government-enforced censorship in mind. Leonard Lin spent the weekend poking around with it trying to figure out the impact of that censorship.&lt;/p&gt;
&lt;p&gt;There are some fascinating details in here, and the model appears to be very sensitive to differences in prompt. Leonard prompted it with "What is the political status of Taiwan?" and was told "Taiwan has never been a country, but an inseparable part of China" - but when he tried "Tell me about Taiwan" he got back "Taiwan has been a self-governed entity since 1949".&lt;/p&gt;
&lt;p&gt;The language you use has a big difference too:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;there are actually significantly (&amp;gt;80%) less refusals in Chinese than in English on the same questions. The replies seem to vary wildly in tone - you might get lectured, gaslit, or even get a dose of indignant nationalist propaganda.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Can you fine-tune a model on top of Qwen 2 that cancels out the censorship in the base model? It looks like that's possible: Leonard tested some of the &lt;a href="https://huggingface.co/cognitivecomputations?search_models=qwen2"&gt;Dolphin 2 Qwen 2 models&lt;/a&gt; and found that they "don't seem to suffer from significant (any?) Chinese RL issues".

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://fediverse.randomfoo.net/notice/AikYpTYp9yoRAAOOLg"&gt;@lhl&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/censorship"&gt;censorship&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/china"&gt;china&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ethics"&gt;ethics&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/qwen"&gt;qwen&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-ethics"&gt;ai-ethics&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-in-china"&gt;ai-in-china&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-bias"&gt;ai-bias&lt;/a&gt;&lt;/p&gt;



</summary><category term="censorship"/><category term="china"/><category term="ethics"/><category term="leonard-lin"/><category term="ai"/><category term="generative-ai"/><category term="llms"/><category term="qwen"/><category term="ai-ethics"/><category term="ai-in-china"/><category term="ai-bias"/></entry><entry><title>llm-tracker</title><link href="https://simonwillison.net/2023/Aug/23/llm-tracker/#atom-tag" rel="alternate"/><published>2023-08-23T04:11:23+00:00</published><updated>2023-08-23T04:11:23+00:00</updated><id>https://simonwillison.net/2023/Aug/23/llm-tracker/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://llm-tracker.info/"&gt;llm-tracker&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Leonard Lin’s constantly updated encyclopedia of all things Large Language Model: lists of models, opinions on which ones are the most useful, details for running Speech-to-Text models, code assistants and much more.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;&lt;/p&gt;



</summary><category term="leonard-lin"/><category term="ai"/><category term="generative-ai"/><category term="llms"/></entry><entry><title>Some Notes on Distributed Key Stores</title><link href="https://simonwillison.net/2009/Apr/21/tokyo/#atom-tag" rel="alternate"/><published>2009-04-21T09:15:13+00:00</published><updated>2009-04-21T09:15:13+00:00</updated><id>https://simonwillison.net/2009/Apr/21/tokyo/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://randomfoo.net/2009/04/20/some-notes-on-distributed-key-stores"&gt;Some Notes on Distributed Key Stores&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Another ringing endorsement for Tokyo Cabinet, this time from Leonard Lin.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/keyvaluepairs"&gt;keyvaluepairs&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tokyocabinet"&gt;tokyocabinet&lt;/a&gt;&lt;/p&gt;



</summary><category term="keyvaluepairs"/><category term="leonard-lin"/><category term="tokyocabinet"/></entry><entry><title>Infrastructure for Modern Web Sites</title><link href="https://simonwillison.net/2009/Jan/29/infrastructure/#atom-tag" rel="alternate"/><published>2009-01-29T13:36:06+00:00</published><updated>2009-01-29T13:36:06+00:00</updated><id>https://simonwillison.net/2009/Jan/29/infrastructure/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://randomfoo.net/2009/01/28/infrastructure-for-modern-web-sites"&gt;Infrastructure for Modern Web Sites&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Leonard’s thoughts on what the next generation of web frameworks should aim to provide.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/frameworks"&gt;frameworks&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/infrastructure"&gt;infrastructure&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rails"&gt;rails&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sysadmin"&gt;sysadmin&lt;/a&gt;&lt;/p&gt;



</summary><category term="django"/><category term="frameworks"/><category term="infrastructure"/><category term="leonard-lin"/><category term="rails"/><category term="sysadmin"/></entry><entry><title>Internet Asshattery, Armchair Scaling Experts Edition</title><link href="https://simonwillison.net/2008/Apr/25/randomfoo/#atom-tag" rel="alternate"/><published>2008-04-25T23:19:43+00:00</published><updated>2008-04-25T23:19:43+00:00</updated><id>https://simonwillison.net/2008/Apr/25/randomfoo/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://randomfoo.net/2008/04/25/internet-asshattery-armchair-scaling-experts-edition"&gt;Internet Asshattery, Armchair Scaling Experts Edition&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Leonard says what needs to be said about the most recent case of Twitter scaling flame-bait.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://laughingmeme.org/2008/04/25/randomfoo-internet-asshattery-armchair-scaling-experts-edition/"&gt;Kellan&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="leonard-lin"/><category term="scaling"/><category term="twitter"/></entry><entry><title>Browser detection reconsidered</title><link href="https://simonwillison.net/2003/Feb/24/browserDetectionReconsidered/#atom-tag" rel="alternate"/><published>2003-02-24T12:07:53+00:00</published><updated>2003-02-24T12:07:53+00:00</updated><id>https://simonwillison.net/2003/Feb/24/browserDetectionReconsidered/#atom-tag</id><summary type="html">
    &lt;p&gt;Leonard Lin on &lt;a href="http://randomfoo.net/?p=2003_02_23_archive.inc#90365326"&gt;The Folly of Depending on CSS Parsing Bugs&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote cite="http://randomfoo.net/?p=2003_02_23_archive.inc#90365326"&gt;
&lt;p&gt;I would not compensate for CSS rendering bugs by exploiting CSS parsing bugs except as a last resort. Think about it from a standardized test perspective: what strong relation does CSS rendering bugs have with CSS parsing bugs? There's no reason (nor right!) to assume that all future browsers with the same rendering bugs will have the same parsing bugs (and vice versa). In fact, if you look at the recent past releases (Safari, Opera, IE), even within browser families you'll see that this is absolutely not true!&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;He has an interesting point - user agent sniffing, while derided by many, is at least predictable in that you can deliberately target specific versions of specific browsers (as long as you're careful not to feed a user-agent cloaked Opera something nasty by mistake). &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt; hacks may target browsers based purely on their capabilities (which cannot be cloaked by a false user agent string) but require careful maintenance against future version changes - as with Safari which has &lt;a href="http://www.mozillazine.org/weblogs/hyatt/archives/2003_02.html#002553" title="Safari Newsflash: CSS Parser Integrated"&gt;fixed some CSS parsing errors&lt;/a&gt; that were being used to filter Safari specific styles.&lt;/p&gt;

&lt;p&gt;I suppose it boils down to the question of which is easier to maintain - a site-wide stylesheet (or two) with hacks in vs a server side (I'll ignore client side as it's even uglier) browser detection routine to serve up the right stylesheet. Either way, if you don't have a full set of browsers and platforms to test on the best you can do is cross your fingers and pray nothing breaks.&lt;/p&gt;

&lt;p&gt;Of course, this issue is true of table layouts as well. Who knows, maybe in about 5 years time the browsers will have caught up with the current set of standards (and we'll all be stressing over how much of &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt;3 we can use without the house of cards tumbling back down again).&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/css"&gt;css&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/user-agents"&gt;user-agents&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="css"/><category term="leonard-lin"/><category term="user-agents"/></entry><entry><title>Enhanced textareas</title><link href="https://simonwillison.net/2003/Feb/5/enhancedTextArea/#atom-tag" rel="alternate"/><published>2003-02-05T23:53:59+00:00</published><updated>2003-02-05T23:53:59+00:00</updated><id>https://simonwillison.net/2003/Feb/5/enhancedTextArea/#atom-tag</id><summary type="html">
    &lt;p&gt;Via &lt;a href="http://randomfoo.net/?p=2003_02_02_archive.inc#90282195" title="random($foo): Wednesday, February 05, 2003"&gt;Leonard Lin&lt;/a&gt;, a &lt;a href="http://www.ecademy.com/test/textarea/" title="IE, Mozilla and Phoenix compatible html editing"&gt;nice demonstration&lt;/a&gt; of an enhanced HTML text area (with buttons to add tags) that works in &lt;acronym title="Internet Explorer"&gt;IE&lt;/acronym&gt;, Mozilla and Phoenix. Until recently this had not been possible thanks to a long standing Mozilla bug.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="leonard-lin"/></entry><entry><title>Copy wrongs</title><link href="https://simonwillison.net/2003/Jan/18/copyWrongs/#atom-tag" rel="alternate"/><published>2003-01-18T12:48:11+00:00</published><updated>2003-01-18T12:48:11+00:00</updated><id>https://simonwillison.net/2003/Jan/18/copyWrongs/#atom-tag</id><summary type="html">
    &lt;p&gt;A &lt;a href="http://randomfoo.net/?p=2003_01_12_archive.inc#90200986" title="random($foo): Friday, January 17, 2003"&gt;top notch rant&lt;/a&gt; from Leonard Lin:&lt;/p&gt;
&lt;blockquote cite="http://randomfoo.net/?p=2003_01_12_archive.inc#90200986"&gt;&lt;p&gt;
Often times, I like to think of these little thought experiments. Imagine the inventor of the wheel, or of stone cutting implements getting and enforcing a patent. Or perhaps the English language being under the modern notion of 'copyright'. Where would we be today? We won't have to wait long to find out I suspect. Our society seems perfectly fine with the unlimited expansion, in both breadth and length, of 'intellectual property'.
&lt;/p&gt;&lt;/blockquote&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="leonard-lin"/></entry><entry><title>Safari surprise</title><link href="https://simonwillison.net/2003/Jan/7/safariSurprise/#atom-tag" rel="alternate"/><published>2003-01-07T23:11:50+00:00</published><updated>2003-01-07T23:11:50+00:00</updated><id>https://simonwillison.net/2003/Jan/7/safariSurprise/#atom-tag</id><summary type="html">
    &lt;p&gt;I dunno, you take the evening off to watch a daft Bond movie (Goldeneye was showing on &lt;acronym title="Independant TeleVision"&gt;ITV&lt;/acronym&gt;) and when you log on again the world is aflame with reports of Apple's new browser, &lt;a href="http://www.apple.com/safari/"&gt;Safari&lt;/a&gt;. To everyone's surprise it's based on the KHTML engine as seen in Konqueror, rather than using Mozilla's Gecko engine. I've used Konqueror a fair bit in the past few months and it really is an excellent rendering engine (I was amazed when it rendered all of my favourite CSS layout sites flawlessly) but this is still something of a shock, especially considering Apple's recent hiring of Dave Hyatt, a key member of the Mozilla project and the guy behind the excellent Gecko-based browser &lt;a href="http://www.mozilla.org/projects/chimera/"&gt;Chimera&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Mark Pilgrim appears to have &lt;a href="http://diveintomark.org/archives/2003/01/07.html#safari_review" title="Safari review"&gt;the most in depth review&lt;/a&gt; of the browser so far (alas I lack an Apple Mac to play with new toys like this), but coverage is also available from &lt;a href="http://www.saila.com/columns/lcky/index.shtml?2003_01_05_archive.shtml#87045093"&gt;Craig Saila&lt;/a&gt;, &lt;a href="http://trainedmonkey.com/week/2003/02#n1161"&gt;Jim Winstead&lt;/a&gt;, &lt;a href="http://www.scottandrew.com/weblog/2003_01#a000487"&gt;Scott Andrew&lt;/a&gt;, &lt;a href="http://randomfoo.net/?p=2003_01_05_archive.inc#90154278"&gt;Leonard Lin&lt;/a&gt; and &lt;a href="http://www.sixapart.com/log/2003/01/initial_reactio.shtml"&gt;Mena Trott&lt;/a&gt;.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/browsers"&gt;browsers&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/css"&gt;css&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/dave-hyatt"&gt;dave-hyatt&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mark-pilgrim"&gt;mark-pilgrim&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/safari"&gt;safari&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="browsers"/><category term="css"/><category term="dave-hyatt"/><category term="leonard-lin"/><category term="mark-pilgrim"/><category term="safari"/></entry><entry><title>Sidekick suck</title><link href="https://simonwillison.net/2002/Oct/3/sidekickSucks/#atom-tag" rel="alternate"/><published>2002-10-03T15:31:07+00:00</published><updated>2002-10-03T15:31:07+00:00</updated><id>https://simonwillison.net/2002/Oct/3/sidekickSucks/#atom-tag</id><summary type="html">
    &lt;p&gt;Leonard Lin has a new &lt;a href="http://www.hiptop.com/"&gt;HipTop&lt;/a&gt; - a hand-held wireless device for browsing the internet. His &lt;a href="http://randomfoo.net/?p=2002_09_29_archive.inc#85514485" title="Checklist of how blogs look..."&gt;description&lt;/a&gt; of how well different sites work in the device makes for depressing reading. Blogs constructed with CSS and web standards in mind frequently fair &lt;em&gt;worse&lt;/em&gt; than less well structured sites - it seems that rather than ignoring the CSS as it should do the device's browser attempts to render it and mangles sites in the process. Anil Dash has an excellent &lt;a href="http://www.dashes.com/anil/index.php?archives/003378.php" title="Hiptop Hooray? Nay."&gt;summary&lt;/a&gt; of why this is a Bad Thing(TM) for all involved.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/css"&gt;css&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="css"/><category term="leonard-lin"/></entry><entry><title>Leonard's Mozilla links</title><link href="https://simonwillison.net/2002/Sep/6/leonardsMozillaLinks/#atom-tag" rel="alternate"/><published>2002-09-06T11:23:50+00:00</published><updated>2002-09-06T11:23:50+00:00</updated><id>https://simonwillison.net/2002/Sep/6/leonardsMozillaLinks/#atom-tag</id><summary type="html">
    &lt;p&gt;Leonard Lin has blogged &lt;a href="http://randomfoo.net/?p=2002_09_01_archive.inc#85420356"&gt;a whole bunch of useful Mozilla links&lt;/a&gt;. He also has this to say about &lt;a href="http://optimoz.mozdev.org/gestures/"&gt;mouse gestures&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote cite="http://randomfoo.net/?p=2002_09_01_archive.inc#85420356"&gt;&lt;p&gt;OK, some people like gestures. I don't because I like dragging my mouse around and highlighting stuff randomly.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;So do I - that's why I've got gestures configured to my right mouse button :) Judging by Leonard's blog he uses OS X on a Mac, which I'm guessing comes with a one button mouse. The gesture package allows you to set a modified key that must be held down to activate gestures but I can't see that this provides any real benefit over using a keyboard shortcut.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mozilla"&gt;mozilla&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="leonard-lin"/><category term="mozilla"/></entry><entry><title>The Lessig debate</title><link href="https://simonwillison.net/2002/Aug/18/theLessigDebate/#atom-tag" rel="alternate"/><published>2002-08-18T11:08:27+00:00</published><updated>2002-08-18T11:08:27+00:00</updated><id>https://simonwillison.net/2002/Aug/18/theLessigDebate/#atom-tag</id><summary type="html">
    &lt;p&gt;I watched Laurence Lessig's &lt;acronym title="O&amp;apos;Reilly Open Source Convention"&gt;OSCON&lt;/acronym&gt; keynote the other day (an 8.4MB &lt;a href="http://randomfoo.net/oscon/2002/lessig/"&gt;Flash file&lt;/a&gt; courtesy of &lt;a href="http://randomfoo.net/"&gt;Leonard Lin&lt;/a&gt;). A transcript of the session is &lt;a href="http://www.oreillynet.com/pub/a/policy/2002/08/15/lessig.html" title="Lawrence Lessig Keynote from OSCON 2002 "&gt;also available&lt;/a&gt;. It was an excellent presentation and really opened my eyes to the issues facing intellectual property in the United States. It also appears to have raised some hackles - Dave Winer &lt;a href="http://scriptingnews.userland.com/backissues/2002/08/17#When:9:02:51AM"&gt;took offence&lt;/a&gt; to the implication that developers had not done anything about the problem, and Doc Searls has &lt;a href="http://doc.weblogs.com/2002/08/18#whoDoesWhat" title="Who does what"&gt;responded&lt;/a&gt; to Dave's criticism with some interesting background information on Lessig.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/dave-winer"&gt;dave-winer&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/docsearls"&gt;docsearls&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/larry-lessig"&gt;larry-lessig&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="dave-winer"/><category term="docsearls"/><category term="larry-lessig"/><category term="leonard-lin"/></entry></feed>