Hacker Newsnew | past | comments | ask | show | jobs | submit | eggfriedrice's commentslogin

This is nice, apart from a quick play when they were new I've never really looked at CF Workers and KV again. This made me go and have a look at the docs and find that it's actually looks quite useful. I didn't know they'd added Python and other languages, so that's cool in itself.

I like Jon's example here, a single and fairly short file that does just enough to demo this all, nice.


I'm building a blog directory/reader/search engine [1] on Cloudflare Workers with D1 as the main database. Very pleased with the ecosystem, including Queues and scheduled jobs. DB migrations are simple, local development is a breeze (scheduled jobs don't work though, but there's a simple workaround), and the DB is an SQLite implementation. I am worried about vendor lock in, but as long as I keep the app relatively straight-forward, it shouldn't be a huge deal to migrate to some other Node or Deno backend.

[1] https://minifeed.net/


I'd have thought the SQLite database (D1) would be a more obvious fit for a blog?


Good point, I'm making my way through exploring more of CF so I'll likely try a D1 variant of this. Ta


I have been very impressed with what you can build on it.

I built this little service to add UK specific political location data to Action Network CRM. 300 lines for the actual service!

code here: https://github.com/jms301/ANUpdaterUK/blob/main/src/index.js

Sure it's only taking a webhook, reading an API, looking up a db entry and then updating via API.

But just knowing it's running on someone else's infra and there's so little code to validate is very comforting.

Prior to this I had a version running on a VPS and yeah I can do it. But you end up with a LOT of code / config to run the web server, the queue, the database... And any of that could be introducing bugs and security problems.


I was stoked on D1 when it was announced.

But the maximum DB size is 10GB (https://developers.cloudflare.com/d1/platform/limits/).

Really?


I assume the intention is you store actual data in R2 objects and just hold references to them in D1.


Note that you can create up to 50,000 databases.


Today I learned about <hgroup>!


I particularly like how the UK phone number examples are not written how we would write them in the UK, which I guess underlines the point.


True, I’m not sure I’ve ever seen a 2 + 4 (e.g. 12 3456) style six digit number in the UK. 01234 567890 is probably what I’d expect; maybe 01234 567 890.


I've always seen it with the leading zero part of the area code to make 4, then 3 then 4 grouping. The leading zero was always listed.

e.g. 0123 456 7890

and 01/02 prefixes are landlines, 07 are mobile phones, 08 free, and 09 premium rate lines.

Wikipedia [0] says that there are 8 digit local numbers, and 2/5 digit area codes, but I happen not to have lived in a place that uses them until mobile phones took over anyway.

[0] https://en.wikipedia.org/wiki/List_of_dialling_codes_in_the_...


I like how the first US number does not have enough digits to be valid.


It is all just extremely confusing if you stare at the examples as I am pretty sure there can't be a country code +12... that would get parsed as +1. So, that first one is actually +1(234)567-8901 ;P.


Obviously no country code can be a prefix of another one. The switches would not know how to interpret it.

But 2 or more countries can use the same country code. The area code will determine which country you call to.

In the North American numbering plan +1 all numbers must have a fixed length 3 + 3 + 4.

In many other numbering plans the length varies. Both area code length and subscriber number length can vary. So it gets pretty complicated to parse a number. Basically rules don't help, you need a database and you need to update it regularly. No idea whether an open, non-commercial data set exists.

When I call to Germany Android shows the name of pretty small places. I believe Android reports every number you call to Google. But the database is probably still local, I believe locations are also shown when you have no data connection.

I am not from the US, but I understood there you might also need extensions to be dialled after the number proper.


The way the system used to be in the USA, area codes only had 0 or 1 in middle of it. So only +120 & +121 would do USA until they shifted in 1995 to have USA area codes w other numbers in the middle. I'll guess any of those little islands only get subsets of the number space to maintain comparability. Once I almost got ripped off fromthis, someone called an adult number w a domestic area code that went to Guyana in South America. I had American Long Lines block all foreign and all pay numbers, they knew if was a foreign porn number and tried to get their cut. I refused as they knew it was international and worse they knew it was porn. I knew to block as my roommate was still in college and I assumed issues would arise with out those blocks.


There's no +1234 (you'll end up in a number block allocated for Ohio), but other +12* numbers can go international. +1242 will end up in the Bahamas and +1246 is the international dialing code for Barbados. A bunch of Caribbean islands are part of the American numbering plan: https://en.wikipedia.org/wiki/List_of_North_American_Numberi...


But that isn't because +12 is a country code: it is because, as your link even shows, some of those are codes are international. I did not claim anything about the country, only the parsing process and how using +12 as an example is just confusing the whole matter as the reader is probably familiar with +1 and +12 can't exist.


I'm not sure I understood much except the photo of the cake


It's a great book, my daughter loves it. I was pretty chuffed when she figured out the AND gate needs both buttons pressed at once. I'm not entirely sure she's sussed XOR yet though.


I've also lasered lots of things from Inkscape drawings. I've always found it easier to use than proper CAD but still get good results.

I don't remember this much, but a previous me wrote a guide for lasering using Inkscape for Edinburgh Hacklab. I don't think the process has changed much... https://wiki.ehlab.uk/inkscape_for_lasering


There is essentially no use of LoRaWAN at 433MHz in Europe, this would have been at 868


I do a lot with LoRaWAN, and I like the simplicity of its approach for class A devices, which is to wake up and transmit and then listen for a reply in two defined time windows. These are shortly after the transmission, so clock drift is less of an issue with cheap oscillators.


OMG, I had no idea Tim Hunkin was churning out YouTube videos these days! I was exactly the right age to appreciate the Secret Life of Machines, and it looks like I have several hours of quality stuff to watch there.


Yup, it's great. I used it to shuffle stuff from s3 into Dropbox and it was just the right tool for the job.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: