When did you use 1Password for the last time? Not a big fan by myself, but the points you are mentioning are fully available
Readit Newsmboehm commented on Passage Is Joining 1Password passage.id/post/passage-i... · Posted by u/mfiguiere
Quite the contrary, I’ve found Docker to be absolutely indispensable for local dev, particularly when I’m debugging various cloud-targeted components, e.g. AWS Lambdas and Step functions. A container can nicely simulate most of the running environment of those things, and mock everything else. Docker + JetBrains IDE is a must-have for that reason
What images do you use? I would love to hear about your setup to debug lambda functions.
mboehm commented on DigitalOcean: New $4 Droplet and updated pricing digitalocean.com/blog/new... · Posted by u/lode
To give some hobbyist level price increase numbers:
I'm currently running two basic droplets at 8gb RAM and 4vCPU, which is basically just enough resources for a proper dev kubernetes cluster with Promethueus, Loki, 5-6 apps, etc (4gb 4vCPU is not enough, I tried). I also run a third 1gb1vcpu management droplet outside the cluster as well as a load balancer in front of my API gateway and a spaces instance to dump backups and store stuff like terraform state. My previous bill was $102 and it looks like it will now under this new pricing with all of the above be about $125 which is about 20% increase.
Are there similar managed kubernetes offerings out there that are better on price? My understanding is that I could probably half this or even do better if I run my own control plane on some other provider but if I want managed k8's is this still the best option price wise? I guess if something like Hetzner or OVH is less than half the price it may even be worth the headache to run my own control plane (which has it's own advantages too - currently I'm stuck with Cilium on DOKS and it would be nice to use another network provider for some of my use cases).
You might want to look into OVH's k8s offering [1]. You only pay the worker nodes and the general purpose instances cost 26,18 € per month offering 2vcpu and 7 gb RAM [2].
We started our journey with Janus about three months ago and I can just fully recommend it. It is an amazing well-written piece of software which is just as flexible and integrative as developers wish. E.g. Slack used Janus, at least in 2016 [0]. It is important to understand: Janus offers the ingredients for building great WebRTC applications (examples [1]), whereas Jitsi is more like a ready-to-go solution and got much more attentation as Janus did.
Lorenzo and his colleagues are doing a really great job.
In the space of SFU/MFU, one really needs to decide beforehand what kind of solution is suitable for which requirement. I have chosen Janus because we could integrate it by 100% in our software. For example, I was also looking into Jitsi. But compared to Janus it feeled so much more complicated and not suited for that specific job.
However, it is important to point out, that this is no a ready-to-go solution. There is a long list of things you will have to dig into:
- ICE (a way to connect if you switch between WIFI and LAN or to punch a hole into your fw) [2]
- Cross-browser compatibility (Thank you iOS [4])
- TURN/STUN (Which matrix of udp/tcp and ports is needed for Hole Punching?), I recommend coturn.
- Scalability: How many clients are planned? In my experience, CPU and bandwith are bottlenecks, we went with horizontal scaling
- How do you gonna test your WebRTC application? So far great results with https://testrtc.com, but you probably also could accomplish a lot with Selenium.
- Simulcast/Bitrate or Unified Plan (Use available bandwith and adapt on-the-fly) [3][5]
But once you got it running, it is an amazing feeling. We are in 2020 and it is possible for an SMB to offer video conferencing to customers via a web-browser using your own infrastructure while being compliant to GPDR and other stuff.
[0] https://webrtchacks.com/slack-webrtc-slacking/
[1] https://janus.conf.meetecho.com/demos.html
[2] https://webrtcglossary.com/ice/
[3] https://webrtcbydralex.com/index.php/2018/03/14/extending-ja...
[4] https://webrtchacks.com/guide-to-safari-webrtc/
[5] https://www.callstats.io/blog/what-is-unified-plan-and-how-w...
Having to look into this professionally for local/remote streaming solutions and came across this paper in the last couple of weeks which has been a huge help to understanding my use case:
http://lup.lub.lu.se/luur/download?func=downloadFile&recordO...
One of the most useful/interesting use cases to me is the ability to have a PTP encrypted stream without having to go through weird IoT PKI hoops.
Ninja edit: If anyone has experience with Janus and/or WebRTC on edge devices I would very much like to talk as I could really use a solid consultant in this realm.
Out of curiousity: What is an edge device? An IP camera?
Depending on the professional grade of your use case, you could directly talk to meetecho, as they are the original developers and offer consultancy around Janus.
What turn servers do you use?
Answering for myself, not for bbeausej. We are currently using coturn. It is quite easy to setup, you have to dig a little into the configuration parameter and that's it - I would recommend it.
Oh well, you probably should use the rest api for generating credentials on the fly and think about scaling (depending on your needs).
I recently used the iText Library for PDF parsing in java.
Everything was alright until I discovered their AGPL license.
https://itextpdf.com/en/how-buy/agpl-license
Since our product was proprietary, we had to remove the library since our product would also come under the AGPL license or we would have to buy their commercial version, for which we can get a "quote"(https://itextpdf.com/en/how-buy)
There is an actively maintained fork of iText: https://github.com/LibrePDF/OpenPDF
From their background section: It is a fork of iText version 4, more specifically iText svn tag 4.2.0, which was hosted publicly on sourceforge with LGPL and MPL license headers in the source code, and lgpl and mpl license documents in the svn repository. Beginning with version 5.0 of iText, the developers have moved to the AGPL to improve their ability to sell commercial licenses.
Cool recap. From your article:
> Is there a general interchange format for these systems?
I don't understand why none of these people is using RDF. Seems like a perfect technology for a memex.
I guess because they do not have a common memex yet. :-)
But yes, RDF should fit very well.
As others pointed out already, I also dislike the idea of being locked into a proprietary file format. This should not be a problem using RDF - I guess we all should think about that idea.
And 10Gbit FTTH from the same provider is just 12 euros. :)