-
I still use RSS routinely to read academic journals. For this use case, Zotero is an excellent feed reader.
-
Microsoft Sculpt Ergonomic Keyboard
-
Same. The Fn key switch is a bit annoying but most of the Fn functions I use are accessible through alternative combos.
When it comes to my overall health and comfort, however, changing to an ergonomic keyboard helped a little but correcting my desk and posture helped a lot.
-
-
-
Useful little example of moving between a local Pandas DataFrame and a Google Sheet.
-
I was kind of hoping this wouldn’t get accepted. IMHO this seems to reduce readability.
I read somewhere the “as” syntax being mentioned for if/while constructs, which I personally find much more readable.
So, instead of,
if (match := pattern.search(data)) is not None: ...something like,
if pattern.search(data) as match is not None: ...Although I guess as with everything, we’ll get used to it. 🤷♂️
-
-
Previously on lobsters: https://lobste.rs/s/ho3ypn/another_world_source_code_review_2011
Speaking of Delphine Software and art-over-gameplay games, you can chalk me up as probably one of the only people who liked the Flashback sequel, “Fade to Black”.
-
-
lorddimwit
edited
2 months ago
|
link
| on:
Building the Commodore that should have existed, an interview with Stefany Allaire
Commodore was spectacular in how well it could snatch defeat from the jaws of victory. The Amiga was the most amazing machine the world had yet seen in 1985, they had possibly the best team of hardware and software engineers in the world, but management just…couldn’t leave it well enough alone.
Bizarre decisions like:
- The Amiga (later retroactively named the Amiga 1000) had a sidecar expansion port. The Amiga 500 had the same port, but upside down…so that all of the existing peripherals had to be upside down to work. Given how they were designed, it meant that none of them would.
- The Amiga 2000 was the first machine that could use the Video Toaster, and the Video Toaster was the killer app for the Amiga. Then they made the Amiga 3000, which could also use the Video Toaster, except that the case was a quarter-inch too short for the Toaster card.
- The Amiga 600 had a PCMCIA slot. Except that they rushed to manufacturing using a draft of the PCMCIA spec, rather than waiting for the final specification. The end result was that regular PCMCIA cards often wouldn’t work on the Amiga.
- Amiga Unix on the Amiga 3000UX was considered one of the highest-quality SVR4 ports ever. Sun offered to produce the Amiga 3000UX for Commodore as a Sun-branded Unix workstation that could run Amiga software…and Commodore declined.
We’d all be using Amigas now if Commodore’s management had literally been anything other than hilariously incompetent, I swear.
-
Jimmy Maher’s book about the Amiga explores a number of these bizarre decisions and reaches a similar conclusion. The title says it all: The Future Was Here! http://amiga.filfre.net/
-
Agree with everything except conclusion as even less incompetent companies failed including Sun. Only Apple survived and even they became are now basically producing PCs with their distro.
However we might have been living in a different future if Amiga had an opportunity for a bigger impact. Mine certainly is as I went to study mathematics instead of CS because I could not imagine developing software for PCs in DOS era.
-
-
Talk about over complicating things. There are plenty of ways to make money from software - just ask Oracle, Microsoft, Amazon, Facebook, Twitter, Google, Docker, Red Hat, etc.
Honestly, the self martyrdom of some FOSS developers is difficult to understand.
-
Software that is being created to be sold, yes. Software that is being created to further society in a way that is beneficial for all, e.g., free software, no. Even the super important projects like OpenSSL aren’t well funded… Everyone makes a lot of assumptions about software—“oh they do this at work, for their jobs”—but my guess is that is the case for only a small handful of the most popular projects, and the rest are doing the work, gratis.
-
-
-
The ones I listed were VC backed, but that’s only because I purposely chose over the top examples where the founders became billionaires. (And also RedHat ;-)
But there are tons of smaller companies who aren’t backed by VCs, whose founders and employees make a decent living creating software. Things like Pixelmator, Reaper, Quicken, etc.
-
-
The concepts of “open source” and selling software for money are orthogonal. The linked article is about a scheme for people who have chosen to give away their software to try making money from it. My point is that they already made that choice when they decided to give it away to everybody for free.
I think there’s some short sighted-ness in software developers around FOSS. To use your OpenSSL example, if it’s a “super important project” (which is just an opinion), then it’s important for the project to organize itself in such a way that it’s sustainable, and that means providing for the developers so that they can keep developing it.
-
To use your OpenSSL example, if it’s a “super important project” (which is just an opinion)
I’m basing it’s “super important project” status on the fact that it has 100s of millions of users (or more) given it is linked in popular browsers, and popular web servers. You’re likely interacting with OpenSSL as you load Lobste.rs. So, yeah, it’s “super important.” There are viable alternatives, now, but that wasn’t really the case until recently, and the amount of effort for the 2 developers to keep it up, in their free time, for the benefit of society, has caused issues in the past. See also GPG’s fund raising efforts, and countless others.
for people who have chosen to give away their software to try making money from it.
No. It’s absolutely not about that. It’s about recognizing that free / open source developers aren’t peons to be trampled on, but, instead, valuable members of our global economy. The chances of this model, or any other model, being sustainable for all contributors is next to nil. Please keep that in mind. Even the most successful of projects that use a foundation model can’t pay their contributors living wages. But, if the original authors choose a different model (than open source) for release, it’d have been very, very, very difficult to make it.
As you’ve stated now, multiple times, if you want to make money off of your software, you have many avenues to do so. And, look at @mperham, nginx, puppet, and all the other businesses that have successfully created sustainable businesses from roots in open source. It’s possible, but this avenue isn’t right for every project, nor is it right for every situation. I’m not going to give up my cushy corporate job to struggle to survive on and build a business based on a piece of software I found useful to me. I’d be happy to let others do that if they desire, and I indicate that with the licensing I choose to use.
-
I’m basing it’s “super important project” status on the fact that it has 100s of millions of users (or more) given it is linked in popular browsers, and popular web servers. You’re likely interacting with OpenSSL as you load Lobste.rs. So, yeah, it’s “super important.” There are viable alternatives, now, but that wasn’t really the case until recently, and the amount of effort for the 2 developers to keep it up, in their free time, for the benefit of society, has caused issues in the past. See also GPG’s fund raising efforts, and countless others.
At the same time, 100s of millions of people are using iOS, Windows, and OSX, so by that criteria they are also “super important”, yet none of them are available for free. Price and size of user base aren’t really criteria for determining importance.
I’m just pointing out that society in general isn’t going to have much sympathy for people who’ve voluntarily given away all of their work.
-
Price and size of user base aren’t really criteria for determining importance.
Just what do you think the word important means, then?
iOS, Windows, and OSX
This logic… is so weird. Yes, they are super important, too. They contribute 100s of millions of dollars in revenue every year to Microsoft and Apple. Do you agree that Microsoft and Apple save millions of dollars a year by not hiring developers to develop proprietary replacements for the libraries and programs they bundle in their distributions? And, at the same time, reap tremendous additional benefits from doing so, by virtue of remaining compatible with other software systems that said, users of those systems want compatibility with?
This post outlines one possible way for them to say thanks. Making a contribution to this type of fund would more than pay for itself in good will and positive PR.
Note: I don’t even know if I agree with the model outlined. Though, I do agree that some monetary compensation to folks contributing to liberally licensed software is healthy for the ecosystem, human/labor rights generally, and the economy
-
-
-
-
The linked article is about a scheme for letting people who have chosen not sell the software they write can try to make money off of it. My point is that they already made that choice when they decided to give it away to everybody for free.
I think there’s some short sighted-ness in the software world around FOSS. If OpenSSL is a “super important project” then it’s important for the project to organize itself in such a way that it’s sustainable to develop it. Forcing the developers to work on other things for their day jobs, or having them beg for money isn’t sustainable, and it really isn’t necessary - it’s a choice they’ve made.
-
-
-
-
-
Tom Standage’s book on the history of telegraphy, “The Victorian Internet,” is a lot of fun. He is great at pulling out the (many) continuities linking the late 19th century to the present.
-
After running a Debian VM in Windows for years, it’s wild how quickly WSL became normal for me. ConEmu plus bash is such a nice convenience.
-
I’ve tried several times to make ConEmu palatable as an app and have failed every time. I find it beyond ugly as an app and I can’t get the colours for Solarized (light) to look right. If you have any tips, I’d appreciate it.
As for WSL, it’s the only reason to use Windows, frankly.
-
I am using Cmder as a frontend for ConEmu, it provides a slightly more polished setup out of the box. Just for the record, I am using Cmder mini version 1.1.4, which was the last release before some larger changes which (for some reason I cannot remember) did not work for me.
-
-
-
Feeling nostalgic for Yahoo! Pipes. :,-)
-
xmodem
3 months ago
|
link
| on:
Maintaining Notepad is not a full-time job, but it’s not an empty job either
I would love to read an anthology about small Microsoft applications like Notepad, Paint, and Calculator. I like to imagine that each one has a champion within the company.
-
xmodem
3 months ago
|
link
| on:
Microsoft’s new Xbox controller is designed entirely for players with disabilities
I love the concept of a relatively open/hackable interface platform. This seems to have applications far beyond gaming. It seems to lower the bar for developing specialized scientific instrumentation as well.
-
If these PIE menus are so awesome, why can’t I just use them?
-
In Android, there as an patch on (now discontinued) Paranoid Android fork, later respawned as SlimPIE but retored due to problematic maintenance in newer Android. There are some overlay-like applications for that though, but they all suffer from minor problems and feel like extraordinary additions not integrated well with the rest of OS.
-
Using such thing as context menu in GTK or Qt could be probably possible (on X.org at least, with XShape ext.) but there are too many places where people assumed that menus are in form of rectangle (both in 3rd party apps and library itself) that you would probably need to rewrite too many LOCs
-
Not even saying anything about WinNT, as they moved scrollbars rendering code into kernelspace because “it’s faster lol”
-
I don’t know too much about MacOS GUI rendering mechanics, but they already did a great improvement over standard UIs with that global menu thing, which is also pretty hard to reimplement in any other environment without breaking stuff
I’ll be really glad to see the software world migrating to more ergonomic UI/UX concept instead of flattening the world for fun and profit (I mean, reducing amount of skilled graphicians), even when they use some hybrid concepts intead of full PIE, for example “trees” or regular menus expanding from root PIE items. This particular concept has been well presented in Sword Art Online anime and also kinda predicted the UX paradigms for holographic/floating interfaces:
-
Like most widget types that are poorly supported or unsupported in popular GUI toolkits, I see pie menus almost exclusively in games – since people writing games have the expectation that they’ll need to essentially roll their own GUI toolkit in order to make it sufficiently themable anyhow.
It’s an unfortunate state of affairs: widget functionality, once you’ve got past the initial learning curve, is proportional to the degree to which the widget behavior matches the user’s internal mental model of the task, and so expressive UI elements have the ability to make real work much more efficient; limiting the use of good GUIs to video game menus means UI design is limited in its capacity to make anything but our leisure time easier.
(As a side note: SAO is a bad example of UI design in anime – the titular game is, on many levels, not professional enough to make it to market, and the way the menus are laid out is no exception. Geoff Thew explains this in detail in one of his video essays. The way SAO uses pie menus is sort of a shallow copy of how pie menus have been used in games for the past decade, as understood by someone who has never played a video game. A good example of an interesting use of pie menus in a real game is the conversation system in Mass Effect – where segments have their size changed in order to make certain responses more likely, and where pie areas correspond to emotions or tactics.)
-
Great points!
I wrote about “Ersatz Pie Menus” in this additional article, “Pie Menu FUD and Misconceptions: Dispelling the fear, uncertainty, doubt and misconceptions about pie menus.”
Ersatz Pie Menus
Richard Stallman likes to classify an Emacs-like text editor that totally misses the point of Emacs by not having an extension language as an “Ersatz Emacs”.
In the same sense, there are many “Ersatz Pie Menus” that may look like pie menus on the surface, but don’t actually track or feel like pie menus, or benefit from all of their advantages, because they aren’t carefully designed and implemented to optimize for Fitts’s Law by being based purely on the direction between stroke endpoints instead of the entire path, minimizing the distance to the targets, and maximizing the size of the targets.
Microsoft Surface Dial: Someone on Hacker News asked me: Any thoughts on Microsoft’s Surface Dial radial menu?
Good question — glad you asked! (No, really! ;) Turning a dial is a totally different gesture than making directional strokes, so they are different beasts, and a dial lacks the advantages pie menus derive from exploiting Fitts’s Law. […]
Beautiful but Ersatz Pie Menu Example – the graphics are wonderful but the tracking is all wrong: http://pmg.softwaretailoring.net/
Turning Is Not Like Stroking: In terms of “Big O Notation”, pull down menus, click wheels, and carousel selection is linear O(n), while with a pie menu you only have to perform one short directional gesture to select any item, so selection is constant O(1) (with a small constant, the inner inactive radius of the hole in the middle, which you can make larger if you’re a spaz).
Yucky Pie Menus Recipes
Bedazzling and Confusing Graphics and Animations […]
Rectangular Label Targets Instead of Wedge Shaped Slice Targets […]
Triggering Items and Submenus on Cursor Motion Distance Instead of Clicking […]
Not Starting Pie Menus Centered on the Cursor […]
Improperly Handling Screen Edges […]
Improperly Handling Mouse-Ahead Display Preemption and Quick Gestures on Busy Computers […]
Yummy Pie Menu Recipes
I’m certainly not saying that pie menus should never be graphically slick or have lots of cool animations. Just that they should be thoughtfully designed and purposefully easy to use first, so they deeply benefit users from Fitts’s Law, instead of just trying to impress users with shallow useless surface features.
Spectacular Example: Simon Schneegans’ Gnome-Pie, the slick application launcher for Linux
I can’t understate how much I like this. Not only is it slick, beautiful, and elegantly animated, but it’s properly well designed in all the important ways that make it Fitts’s Law Friendly and easy to use, and totally deeply customizable by normal users! It’s a spectacularly useful tour-de-force that Linux desktop users can personalize to their heart’s content.
Gnome-Pie — Simon Schneegans
Homepage of Gnome-Pie, the slick application launcher for Linux. simmesimme.github.io
Gnome-Pie is a slick application launcher which I’m creating for Linux. It’s eye candy and pretty fun to work with. It offers multiple ways to improve your desktop experience.
Check out the project’s homepage @ http://gnome-pie.simonschneegans.de
-
I saw. You had a lot of interesting stuff on your Medium account.
(Are you likely to post more on HyperTIES? As a Xanadu-er & someone interested in the history of pre-web hypertext systems, I find it interesting, since it has a pretty distinct look & feel and seems like it might have more interesting UI ideas to copy. The ‘pop-out’ mechanism for linked areas in images interested me when I saw it mentioned.)
-
One of the good ideas was that every article had a brief definition, which it would show to you the first time you clicked a link, without leaving where you were. That’s a feature I wish was universally supported by the web, so you didn’t have to leave your current page to find out something about the link before following it.
You could then click again (or click on the definition), or pop up a pie menu to open the link in the current or the other window. Also you could turn pages and navigate with the pie menus, swiping in obvious directions, like with an iPad, but having the pie menu to provide a visual affordance of which gestures are available (“self revealing” gestures).
Here are a couple of articles about HyperTIES that I haven’t moved to Medium yet:
Designing to Facilitate Browsing: A Look Back at the Hyperties Workstation Browser. By Ben Shneiderman, Catherine Plaisant, Rodrigo Botafogo, Don Hopkins, William Weiland. http://www.donhopkins.com/drupal/node/102
Abstract: Since browsing hypertext can present a formidable cognitive challenge, user interface design plays a major role in determining acceptability. In the Unix workstation version of Hyperties, a research-oriented prototype, we focussed on design features that facilitate browsing. We first give a general overview of Hyperties and its markup language. Customizable documents can be generated by the conditional text feature that enables dynamic and selective display of text and graphics. In addition we present:
an innovative solution to link identification: pop-out graphical buttons of arbitrary shape.
application of pie menus to permit low cognitive load actions that reduce the distraction of common actions, such as page turning or window selection.
multiple window selection strategies that reduce clutter and housekeeping effort. We preferred piles-of-tiles, in which standard-sized windows were arranged in a consistent pattern on the display and actions could be done rapidly, allowing users to concentrate on the contents.
Pie menus to permit low cognitive load actions: To avoid distraction of common operations such as page turning or window selection, pie menus were used to provide gestural input. This rapid technique avoids the annoyance of moving the mouse or the cursor to stationary menu items at the top or bottom of the screen.
HyperTIES Hypermedia Browser and Emacs Authoring Tool for NeWS. http://www.donhopkins.com/drupal/node/101
That has a screen dump, an architectural diagram, a list of interesting features, data structures, and links to the C, Forth, PostScript, Emacs MockLisp, and HyperTIES markup language source code!
Here’s a demo of HyperTIES and the pop-out embedded menus:
HCIL Demo - HyperTIES Browsing: Demo of NeWS based HyperTIES authoring tool, by Don Hopkins, at the University of Maryland Human Computer Interaction Lab.
https://www.youtube.com/watch?v=fZi4gUjaGAM
A funny story about the demo that has the photo of the three Sun founders whose heads puff up when you point at them:
When you point at a head, it would swell up, and you pressed the button, it would shrink back down again until you released the button again.
HyperTIES had a feature that you could click or press and hold on the page background, and it would blink or highlight ALL of the links on the page, either by inverting the brightness of text buttons, or by popping up all the cookie-cut-out picture targets (we called them “embedded menus”) at the same time, which could be quite dramatic with the three Sun founders!
Kind of like what they call “Big Head Mode” these days! https://www.giantbomb.com/big-head-mode/3015-403/
I had a Sun workstation set up on the show floor at Educom in October 1988, and I was giving a rotating demo of NeWS, pie menus, Emacs, and HyperTIES to anyone who happened to walk by. (That was when Steve Jobs came by, saw the demo, and jumped up and down shouting “That sucks! That sucks! Wow, that’s neat. That sucks!”)
The best part of the demo was when I demonstrated popping up all the heads of the Sun founders at once, by holding the optical mouse up to my mouth, and blowing and sucking into the mouse while secretly pressing and releasing the button, so it looked like I was inflating their heads!
One other weird guy hung around through a couple demos, and by the time I got back around to the Emacs demo, he finally said “Hey, I used to use Emacs on ITS!” I said “Wow cool! So did I! What’s was your user name?” and he said “WNJ”.
It turns out that I had been giving an Emacs demo to Bill Joy all that time, then popping his head up and down by blowing and sucking into a Sun optical mouse, without even recognizing him, because he had shaved his beard!
He really blindsided me with that comment about using Emacs, because I always thought he was more if a vi guy. ;)
-
Accidentally stumbled upon the xanadu-esque side of this conversation. Just to throw in a thought, it’s been on my mind to attempt applying a high level of polish to the federated wiki project such that it facilitated a way to zoom in on reading one thing at a time (a zoom of sorts). So..a ‘big head mode’ of sorts to let you focus on consuming (or editing an article when you needed it then zoom back out to see the connections.
The other crazy thought on my mind is seeing if there’s a way to bend existing oss text editors (particularly atom.io) to facilitate more freeform things like ‘code bubbles’ or liquidtext.
-
-
-
-
-
I just added this example to the article, which you may have missed (since it wasn’t there until a few minutes ago):
Spectacular Example: Simon Schneegans’ Gnome-Pie, the slick application launcher for Linux
I can’t understate how much I like this. Not only is it slick, beautiful, and elegantly animated, but it’s properly well designed in all the important ways that make it Fitts’s Law Friendly and easy to use, and totally deeply customizable by normal users! It’s a spectacularly useful tour-de-force that Linux desktop users can personalize to their heart’s content.
Gnome-Pie - Simon Schneegans
Homepage of Gnome-Pie, the slick application launcher for Linux. simmesimme.github.io
Gnome-Pie is a slick application launcher which I’m creating for Linux. It’s eye candy and pretty fun to work with. It offers multiple ways to improve your desktop experience.
Check out the project’s homepage @ http://gnome-pie.simonschneegans.de
If that doesn’t blow your mind, check this out – there are so many great things about it:
-
-
-
I have a hard time in understanding how decentralized systems are better at protecting me from abusive government agencies, groups, and even individuals? With big online companies, it is not perfect but, as a citizen I have more tools to ask for accountability.
And even for daily stuff, how can I trust “decentralized” systems run by some individual who may or may not be good at following security best practices etc. Again, with big online companies, again it is not perfect but, I have more power as a citizen.
I think centralized systems scale better when it comes to power / responsibility balance.
I vote against decentralizing lobster but happy to read more counter arguments.
-
It’s more about people outside the US. Big Corps like Reddit or Google basically follow the US law and the US law mostly protects only US citizens.
Instances in the fediverse follow local law (which is why usually people don’t federate with Japanese instances that allow NSFW material) which is great if the US law is silly in your culture/country.
The easy answer is simply that you pick a community, not a corp for your server. If you pick a corp for your server you should pick on in the same legislation as you are in.
-
It’s even good for people within the US; for instance, I can pick a fediverse server in Germany and know that the admins will be required by law to ban nazis even though I don’t live in Germany.
-
I agree that federating big platform like reddit, Twitter, or YouTube makes sense because these platforms host multiple communities with conflicting norms and expectations regarding privacy, speech, etc. In an ideal scenario, individual reddit nodes could choose to omit subreddits they found objectionable or implement their own local censorship regimes (a la USENET).
That said, I am inclined to agree with ctulek that lobste.rs is best suited to central hosting. In scale, lobste.rs is more like an individual subreddit than the reddit platform. We pick our community each time we choose lobste.rs over other forums discussing similar topics.
-
-
-
-
I host a little box for my friends and I to play with. We’ve been running these services for about 18 months. I enthusiastically recommend both:
- Evennia, a super fun MUSH engine written in Python: http://www.evennia.com/
- JupyterHub, a multi-user Jupyter server: https://jupyterhub.readthedocs.io/en/stable/
-
I started using KeePassX several years ago because I needed cross-platform compatibility. It requires more manual work than other options and I don’t have it sync’d with mobile. However, it is also reliable enough to discourage me from switching.
-
After a few years of using KeePassX I switched to KeePassXC and I’m glad I did. Nearly the same thing but better (eg. TOTP, UI/UX improvements).
It started as a community fork because development on KeePassX was too slow, take a trip to https://github.com/keepassxreboot/keepassxc/issues/43 for the details.
-
-
-
For a related tangent, check out Bill Lange’s blog post about the Alien Group Voice Box for Atari 400/800 personal computers. It’s one of several voice synthesizer devices for the 8bit micro market. Toward the bottom of the post, there’s also a link to an episode of Kevin Savetz’ podcast with Mike Matthews of Electro Harmonix, who offers some more background and context for the peripheral.
-
IMO If we’d gotten Xanadu instead of the web, we’d still be stuck looking at the equivalent of 1997’s user interfaces. And thanks to TN’s obsession with copyright enforcement, by now (20 years later) the metadata would outweigh the data a hundred to one. It would be a nightmare.
-
Comparisons with the Web are limited because the Web has been stretched so far beyond its roots as a distributed hypertext system. I find Xanadu a lot more compelling when I consider very large collections of documents, e.g. an encyclopedia, dictionary, or textbook archive. Indeed, Nelson’s own examples tend to be non-fiction essays and criticism. What would a deeply annotated version of The Art of Computer Programming look like in a hypertext system with two-way links?
-
I think you misunderstand the purpose of transcopyright.
Rather than being an expansion of normal copyright enforcement, it’s just as much of a subversion as the GPL. Because every clip, no matter how small, is verified, and all assembly occurs on the target machine, derivative works literally cannot be shut down on copyright grounds & abuse of DRM isn’t possible.
Today, most data on the web is partial, degraded duplicates with no notation as to common origin. These duplicates cannot be combined or traced, because we don’t bother to point to a canonical form. Replacing them with metadata makes the total amount that needs to be stored much smaller.
Re: user interfaces – there has been no meaningful progress in mainstream UIs since 1977. There have been interesting fringe experiments, including Squeak’s Morphic, Plan9’s Rio, Xanadu’s own ZigZag, and Jef Raskin’s SwyftKey and ZUI, none of which have had any impact on things non-Lobsters-users have heard of. UI designs, as far as ‘regular users’ know, begin and end with things Alan Kay worked on in the 70s.
You can’t take the Xanadu web pages (which were mostly written in the 90s) & Xanadu open source releases (which were largely written in the 80s) as representative of Xanadu UI designs.
When I worked on the replacement for XanaduSpace (which still looks ostentatiously flashy today, despite being written in 2006), I was pushed hard on visual polish (which ultimately I couldn’t deliver – OpenGL simply doesn’t have the facilities to make it easy to render an entire bible in real 3d in a way where editing is as fast as on a 2d surface).
I personally disagree with some Xanadu UI design decisions, but primarily because they are too visually radical in ways that don’t make sense to me (like text editing in 3d) rather than because they resemble mid-90s web design (which I prefer – at least mid-90s web design worked, when it came to displaying minimally-formatted rich text on slow machines).
-
-
xmodem
4 months ago
|
link
| on:
Google removes ‘Kodi’ from search autocomplete in anti-piracy effort
This seems like one of the more egregious abuses of their monopoly position. I understand that the policy only affects autocomplete but it is still a shady move.
Reminded me of FOAF: http://www.foaf-project.org
Now that takes me back…
I remember being so excited about FOAF when I learned about it around 2005. Those were the heady days of blogs and RSS feeds and open APIs.