Github does proxy SVGs, but it doesn't rasterize them.
If you're interested in embedding something like this on GitHub then you might want to check out Repography [1]. There are only a few styles of dashboards at the moment but I'm working on others.
There's an entry in our FAQ [1] about this. We only use OAuth to identify your GitHub account and then the GitHub app installation has much better defined permissions.
I'd love to be able to restrict the OAuth scope even further but GitHub doesn't let us. I've heard this concern a couple of times now so I'll have another look. I can hopefully at least improve how it's presented and communicated so it's more reassuring!
Hello HN, here's a side project I've been working on for way too long - Work/Artwork lets you create a high-end poster based on an artistic visualisation of your Git repo.
I've seen somewhat similar ideas before but I wanted to create something I'd actually want to put on my wall, or give to a client or to team members to celebrate a project.
I've worked with 4 different artists to create these design systems and I think the range of output is great - depending on your repo some designs will work better than others, and there are also some settings to tweak for each one.
I'm happy to answer questions on the implementation, the process, or just why it's taken so bloody long (first prototype was about 5 years ago!)...
Very nice. We often try and show some visualisation of the work the dev team have done over the year to the rest of the business and this could be quite nice.
There's a very recently announced (https://security.googleblog.com/2021/10/launching-collaborat...) initiative by Google, Salesforce, Okta, Slack and others to create a minimal security standard - https://mvsp.dev/ - which will hopefully reduce this overhead and encourage an improvement in security across the industry.
I think the intent here is to note that there may be business requirements about these that affect the security of your business.
For example, if anyone pays you through credit cards, PCI DSS is non-optional. Certain transactions of health information will require Hitrust. Without them, you won't be able to do business, and while they seem large (PCI DSS if you have another company handle the cards, is a very simple self-assessment.)
IME the human time cost and direct expense associated with obtaining HITRUST, even if you've already done SOC2, is roughly in line with buying a Lamborghini.
Seems like an inoffensive route to monetization for the excellent MDN docs and I hope it's successful, but $5/month (presumably per user for an organisation?) is pretty punchy for the current offering.
Customizing the compatibility tables is a nice idea, but we're talking about shaving seconds of developer time per month.
I'm still seeing $5/month - https://imgur.com/a/SkQyAIo - I guess either it's priced per region (I'm in the EU) or they're A/B testing based on the number of subscriptions to the launch notification.
The core of this is of course the response header "Content-Type: multipart/x-mixed-replace" which in theory lets the server push updated chunks of any content type (although apparently only images in Chrome since 2013 [1]).
While it's a crude and handy way to update some content after the initial load without JS, it was also widely used with JS before Web Sockets - to push messages to clients with less latency than XHR polling.
The big problem with this spec (which is shared today by all the HTTP uploads in the world) is that you have to check for the delimiter every byte!
"Content-Type: chunked" is much better because it gives you the size of each chunk upfront! But that requires .js and also was buggy in IE until version 7.
omg! I thought it would slowly create and send along an mjpeg video file. Server push animation is a 90's thing. I wrote something up about it in 2009, and posted a still-working demo, because of a thread here. https://pronoiac.org/misc/2009/10/server-push-animation/
Very nice. I've used a similar effect for a few years on my homepage - http://arpad.co.uk - albeit with a far more primitive algorithm ;)
Annoyingly I didn't make a note of where I found the algorithm and I can't find the source now, but I remember being struck by its simplicity and deciding I had to find a use for it.
"In Europe, in contrast to Japan and the US, there are restrictions laid down by the EPC on
how far computer programs may be patented. Programs considered to make a “technical contribution”
– such as controlling a robot, or making the internal operation of a computer more efficient – can be
patented; general application programs – such as word processing software – cannot."
...
"In this case, the Review believes the balance of evidence lies in continuing to withhold
patent recognition of non-technical computer programs as part of a sustained effort to deal with the
growing and dangerous problem of thickets. The UK should seek to convince its European partners of
the force of this case.
Similar considerations apply to the patenting of business methods (for example, particular
pricing and marketing schemes) which are also allowed in the US but not in Europe – and unlike in the
computer program area, there is no sizeable European lobby arguing for their patenting. Here, the
correct course is clear: Europe should continue to resist the patenting of business methods."
"Recommendation: Patent thickets and other obstructions to innovation.
In order to limit the effects of these barriers to innovation, the Government should:
• take a leading role in promoting international efforts to cut backlogs and manage the boom in
patent applications by further extending “work sharing” with patent offices in other countries;
• work to ensure patents are not extended into sectors, such as non-technical computer
programs and business methods, which they do not currently cover, without clear evidence of
benefit;
• investigate ways of limiting adverse consequences of patent thickets, including by working
with international partners to establish a patent fee structure set by reference to innovation
and growth goals rather than solely by reference to patent office running costs. The structure
of patent renewal fees might be adjusted to encourage patentees to assess more carefully the
value of maintaining lower value patents, so reducing the density of patent thickets."
Let's hope Vince Cable and the rest of the government take these recommendations seriously and are not looking across the atlantic through rose tinted spectacles (as many of the Conservatives seem to be doing w.r.t. some other areas of economic policy).
