Has anyone tried Mastodon yet? For those who don't know it's a federated, distributed and (currently) technology-orientated social network (well, rather a group of interoperable social networks) that's fully open source and ad-free. I've been impressed so far but as with every new network, whether it flies or not will depend on how many people join, contribute and keep the ball rolling.
I am not a lawyer, but I believe that if you 'port' software from one language to another, you're creating a derivative work and the original licence applies. However (from Wikipedia):
As you have created the ports of libraries that are in the public domain, I'd suggest that a Creative Commons licence makes most sense. I noticed on several netlib pages that attribution is requested, so CC-BY might be most suitable (crediting both the original authors and you), or CC-0 if that's not required.
Plus, the CSS is totally different between the first and second fiddles. Posting examples with minimised code is a bad idea, it's clearly broken because while it looks like Bootstrap 2 the fonts aren't applied in the preview window. Total failure.
@pty: Good try, but it was a refurb (and I wanted new, the two year warranty at John Lewis is always hard to ignore), there was only one of them (I needed two) and they don't have any stock :-)
Haha yeah, it was such a good deal it was snapped up in hours
I'd have a higher-specced refurb over a brand new lower-spec machine every day of the week. Granted the 2 year warranty from John Lewis is a nice extra (they sell refurbs with the 2 year warranty too, by the way!)
I'd try somewhere like Microcenter, if you look at their clearance/open box section on the website there are some deals to be had. I don't know what your budget is, but this for $791 looks like it'll fit the bill. You'd have to see what's available in your local store though!
There seems to be a bit of anti-Dell rhetoric in here, but the XPS range is good, I prefer my XPS 13 over my MBP in some ways.
True, and if she wants to continue and learn then fair play, and I hope she manages to build something great.
However, she's using a discontinued tool that outputs unmaintainable HTML, and developing her site clearly isn't her goal; letting people know about her jewelry (which looks fantastic, by the way Sanda) is.
Plus, as there's a products tab on her site, one would expect that some kind of 'web shop' is on the radar. That won't be doable in Webplus, and it's not the easiest thing to implement from scratch at the best of times.
I've been following this with some interest. Bad practice to end with a verb?
I think the distinction is between an API and a web app. In a web app, /widgets/123/edit (obtained via a GET) should contain a form that allows you to edit Widget number 123. Submitting the form should send aPATCH to /widgets/123.
In the case of an API, you don't need an edit form so you can omit verbs from the route entirely.
It turned out that the load balancer was blocking non-GET/POST requests. It wasn't an Nginx problem after all!
This doesn't suprise me at all! :)
I actually imitated the /users/~ endpoint after LinkedIn's API, which does:
Yes, but LinkedIn's API is read only.
If Dazah's API allows you to update your profile then it definitely makes sense to split it. Allowing PUT or PATCH to work if the :user_id param is ~ but not if it's anything else adds inconsistency to the API and will add to the complexity either in your code or in your documentation.
Also, because the returned data probably differs despite having the same endpoint (as you expect to see a bit more data on your own profile compared to someone else's), the API in general is less predictable than if you used two disparate endpoints for interacting with profiles generally and viewing/modifying your own.
True, but the requirements he is looking to implement exist in most clients anyway (definitely Gmail, Mail.app and Outlook 365, but you'd need to use categories/labels instead of a new folder per subject).
Of course it's possible, but just do everyone (yourself included) a favour and use an existing client. What advantage is there of having your own? Written by a non-expert, without having thousands (or millions, billions) of hours of hands-on testing, your client is likely to be pretty poor.