rmedaer

8 ms·

31.
by rmedaer 6y ago
Would you be interested to read a blog post about how it works? I consider to write a few articles about each part of the project... if there are people to read them! ;-)
32.
by rmedaer 6y ago
It generates the smallest QR Code possible (Version 1; size 21×21). Other URL shorteners generates bigger QR code (usually version 2 or 3)
33.
by rmedaer 6y ago
Hi masukomi. Currently it's still a side project (started a few days). My plan included the following phases: 1. Idea + POC (solved technical issues) => Done 2. Build a MVP => Done 3. Get some feedback and see if there is
34.
by rmedaer 6y ago
Right! Currently there is no plan to remove shortened URL. Meaning that the service keep shortened URL indefinitely.
35.
by rmedaer 6y ago
The shortened URL contains 25 characters. Actually it could be smaller but the goal is to generate the smallest QR code. To do so, a restricted set of characters is used. The result is a small QR code version 1. There is currently no limita
36.
Show HN: URL Shortener Optimized for QR Code(ku.ag)
52 points by rmedaer 6y ago|41 comments
37.
Ask HN: Should I write Terms and Conditions for a free-to-use service?
6 points by rmedaer 6y ago|2 comments
38.
Configure Your Sockets with URIs(raphael.medaer.me)
2 points by rmedaer 6y ago|0 comments
39.
Flockport: Time to Start All over Again and Return to LXC Containers(thenewstack.io)
1 points by rmedaer 6y ago|0 comments
40.
by rmedaer 6y ago
Thanks quaffapint to raise this point. To be honnest, I hesitated to add this question in the post. Indeed HPACK could partially solve the issue. But as you said, it requires HTTP/2. Btw, HPACK is well explained here: https:/&#x2
41.
by rmedaer 6y ago
I edited my article with a link to the RFC of JSON Web Tokens, which is for me the first result on Google or DuckDuckGo when I search "JWT".
42.
by rmedaer 6y ago
I see that you have a lot of scopes ( https://github.com/difi/felleslosninger/blob/ad9ef79b4fef61f... ). Especially from 3rd parties ( https://integrasjon.difi.no/scopes/all https:/&#
43.
by rmedaer 6y ago
> need to be some degree of agreement and coordination between token producers about what a particular scope string means & agreement between different services (...) I agree with you on this point. Actually there are already some &q
44.
by rmedaer 6y ago
Hi shoo, thanks for your feedback. At this point in time this is only a proposal. A proposal which needs to be challenged. So thanks again for your useful feedback. Indeed the goal is to limit the size of JWT tokens. I can't tell you i
45.
by rmedaer 6y ago
Here I'm talking about the value of one particular claim: `scope`. If you identify each scope by only one character it would be limited to the size of your alphabet. If you talk about claim names, they basically aim to be short. For in
46.
JWT scope claim compression using a bitmap(raphael.medaer.me)
40 points by rmedaer 6y ago|40 comments
47.
Scope Bitmap in JWT (and OAuth)(raphael.medaer.me)
4 points by rmedaer 6y ago|0 comments
48.
by rmedaer 7y ago
Understood! The name is inspired by "Open *" projects. For instance OpenAPI. The goal of this project is first to design a specification format for APT repositories like OpenAPI is doing for HTTP APIs. I have to admit that it is
49.
by rmedaer 7y ago
Managing, organising and publishing APT repositories became a nightmare for us as well. That's why OpenAPT is alive. It moves APT management from script paradigm to state description paradigm. Indeed with OpenAPT, you don't have t
50.
by rmedaer 7y ago
What do you mean by "closed apt" ?
51.
Show HN: OpenAPT first release – Automate your APT repositories layouts(github.com)
22 points by rmedaer 7y ago|16 comments
52.
by rmedaer 7y ago
I'm going to build a small online service with only one product and a subscription fee by month. I had to compare the Payment Gateways to know which one fit my needs. To do this comparison, I made a small spreadsheet which could (maybe
53.
Is Content-Type header mandatory in HTTP response?(github.com)
2 points by rmedaer 7y ago|0 comments
54.
RESTful API Guidelines from Zalando(opensource.zalando.com)
3 points by rmedaer 7y ago|0 comments
55.
Stop going to networking events and start networking(mattandre.ws)
3 points by rmedaer 7y ago|0 comments
56.
by rmedaer 7y ago
It might be interesting to answer the same questions for `git-crypt`! I also listen to `git-secrets`... but I don't know much more!
57.
Comparison of encrypted Git remote implementations (2017)(ptspts.blogspot.com)
20 points by rmedaer 7y ago|5 comments
58.
A Faster HTTP Parser for Node.js(github.com)
1 points by rmedaer 7y ago|0 comments
59.
PostgreSQL 13 – Allow sampling of statements depending on duration(depesz.com)
5 points by rmedaer 7y ago|0 comments
60.
OpenAPT: Description Format for Apt Repositories(github.com)
14 points by rmedaer 7y ago|0 comments

More ›