I do a similar thing [1]. One of the great advantages to formally namespaced IDs is including a systematic conversion into strong types in your code. It's harder to accidentally mix things up when coding; function parameters and return tuples are more 'self documented' (and enforced by compiler where applicable).
I don't see how it isn't based on time. They use GPS and atomic clocks to establish the time, establish an uncertainty window, and in Spanner's case will have transactions wait out that uncertainty to guarantee an ordering (globally).
Agree, and the timestamp comparisons you can make when the windows do not overlap are the basis of the ordering guarantees (across machines, even globally).
Could be an alias, I have a limited set of aliases for each type of system. But I keep a repository of hundreds of personal shell scripts and it fit better there.
I want to make a FOSS reader that we can run on our own machines. It would poll on demand and be really good at archiving sites/posts. A combination of feed reader and scraping/archiving from residential IPs (at a low rate) where it will almost always be successful.
I want to pair that with an (opt-in) service for syncing feed subscriptions and handing off a stream of things worth archiving (it's often not urgent that this happens, you just want to make sure it happens soon so the content is not lost in a few years). That service could be a very low cost monthly subscription thing plus a FOSS option that you could run on a cheap VPS, etc.
24/7 services are also essential for generating notifications when something in a filter is spotted, being able to have an email gateway, doing things like POSTing items to other sites automatically, etc.
Making that "full" service FOSS is not in the near term plans, though. This is a distributed system that has run 100s of millions of jobs already, has a very specific security and monitoring setup, uses a number of queues and databases, etc. From my past experience, it's really hard to support people with on-premises distributed systems software like this (FOSS or not). I couldn't do this part alone (bootstrapping and can't afford to hire anyone yet).
The author is pointing out that someone who clicks an RSS/Atom link and gets a page of gibberish is not going to understand all that XML, and they will likely just go back to the site confused.
Instead, you can have a readable page with a message like the one in the post: "This is an RSS feed. Subscribe by copying the URL from the address bar into your newsreader. Visit About Feeds to learn more and get started. It’s free."
There are a lot of feeds now with titles and maybe a short paragraph of text, like the beginning of the article or a summary.
There is a world of difference between sites maintaining those feeds vs. nothing at all. Having a signal that an article is there with even the slightest amount of context is so much better than the alternative.
It's mildly annoying to visit a site for the full text (with your ad blocker), but signing up for newsletters etc. from each site one-by-one is really painful.
If I'm going to take 5+ minutes to really read something, it's OK to visit the site. That means something is interesting or relevant enough to invest my time in. That signal can usually be gleaned from a title and short paragraph. Compared to the number of new things published every day, it's relatively rare to find things worth those 5+ minutes.
From what I can gather, many people use RSS readers to follow 5-10 feeds, and they slowly look through and read most of the articles. It serves as a convenient way to follow their top few sites and maybe a few aggregators like HN. Other people track 100s of feeds and quickly scan what's happening, only diving into something if it's interesting or important.
I'm building a service for the second type of person (mainly because I'm that type of person, TBH). No idea what the ratio of "completionists" vs. "scanners" is. Having title-only feeds is not ideal for the latter group, but it's usually fine.
Reddit is creating an exemption to its unpopular new API pricing terms for makers of accessibility apps, which could come as a big relief for some developers worried about how to afford the potentially expensive fees and the users that rely on the apps to browse Reddit. As long as those apps are noncommercial and “address accessibility needs,” they won’t have to pay to access Reddit’s data.
“We’ve connected with select developers of non-commercial apps that address accessibility needs and offered them exemptions from our large-scale pricing terms,” Reddit spokesperson Tim Rathschmidt says in a statement to The Verge.
I don't have that mentality that this must be the case, for what it's worth. It's just what is most attractive to the end-users usually. And it's what many products do to attract them.
I did not like that limitation either and get around it by using the Yubico Authenticator app with three separate hardware tokens configured with the same shared TOTP seed. There's also path to reset your root account access, btw.
It's not really about trust, it's about the hassle of adding and maintaining things (including keeping up with their changelogs and security issues).
As for log clutter, my approach comprehensively stops the logs files from being cluttered with failed attempts; that's one of the main reasons I do it.
It all depends on your constraints and who needs SSH access, but if you're like me, you (1) have a number of personal VM instances on major cloud providers and (2) don't want to deal with anything but 'vanilla' Linux and sshd. No customizing kernels, no portknocking, no TCP wrappers, no fail2ban, no VPNs (not even tailscale which is very nice).
The approach that I've been using for about a decade is a script that gets your current (internet facing) IP and then uses a cloud API credential to add that IP to the cloud provider's firewall as a valid source IP to port 22. The API security and cloud firewall implementation is left to the major cloud providers (and they are very good at these things).
I run it manually whenever I'm in a new location or in the rare cases my home IPs change. You can add the IP to the list or replace the list each time. Or clean it up after a trip with a separate CLI flag. I figured one day I would automate it to track IPs, run constantly, and trigger the change if it detected a new IP - but that day never came because it never annoyed me (ymmv).
This approach could be extended to teams, but there are more details to think through about API permissions, etc.
This reminded me of the similar cascading effect you get with availability across the aggregate of many services as discussed in "The Calculus of Service Availability": https://queue.acm.org/detail.cfm?id=3096459
Cool. I also saw "Save to Pinboard share extension" on the list of unlock features which also led me to believe it was only available that way. Anyhow, it's working well and thanks again.
Just to clarify what I was saying, the iOS share extension (including tags and tag-autocompletion) is the most important feature to me and the share extension is only available after unlock. Tag autocompletion will work elsewhere as the author replied.
Thank you for this! I've been unhappy with the iOS options recently (bugs, no one replying to bug reports, etc). So far your app is working better than the other choices and it handled my 15k+ bookmark collection easily.
The most important feature for me is being able to use the iOS share function and quickly add something with tags (and tag auto-complete). It would have been nice to test that ahead of the in-app purchasing but decided to go for it. Happy that all works well. Great work.
> API Gateway has a hard limit of 500 WebSocket connections per second
That particular limit is new connections per second, not total connections per second. Starting from zero, you could have 1.8M connections after an hour (per account, per region).