> In conclusion, the off-center “x” is real and probably an artifact of the display or how it is rendered. It is unlikely that it is the result of chromatic aberration.
Interesting! Haven't come across it before but those linked `~>` operators do indeed quite familiar. If you're familiar with GraphDSL do you have some elements we should look into?
I wonder if with directional arrows, instead of writing "out ~ switch.in; switch.out ~ power.gnd", we could write "out ~> switch ~> power.gnd" instead?
But without distinction between in and out ports it may not be possible to check if connections are valid ones.
Anyway, this project really makes me want to learn electronics! Congrats!
You're absolutely right! We've been thinking very similar ways about "dipole" components and how to best do this; and I think you've nailed it.
What about using dunder __in__ and __out__ attributes? Easy enough to implement for us and overload for folks in the future.
I've only worked with Akka Graph DSL to build some data pipelines or protocol stacks. And I've loved working with it!
The equivalent of atopile signal would be port with Akka I think. A combination of ports gives us a shape. A source shape is just one OUT port. A flow shape is one IN and one OUT port, etc.
I'm very new to electronics so I don't know if it makes sense, but connecting all these ports with directional arrows was really helpful to understand the data flow.
This means that data sharing between the US and EU is a lot more complicated, as the EU ruling basically says that US data protection regulations are not sufficient to comply with the requirements set out in the GDPR.
Sorry but epd (ePrivacy Directive)[0] is from 2002 with last amendments in 2009 and has nothing to do with this.
There's a draft for "ePrivacy Regulation"[1][2] introduced in 2017 that looks to replace ePrivacy Directive, but it's still in a draft and discussions stage. There's no guarantee it'll become a law.
Sorry but you’re mistaken. The original ePD applied to messaging services, ie, SMS providers. What changed this year is that a few months ago the EU decided that providers like Messenger should be covered by the regulation too.
But I don't understand how ePD with no changes from 2009 can suddenly include Facebook and others? Unless there have been other regulations passed?
I can't find anything about ePD changes that forces Facebook to do this, all I can find is the upcoming ePR (ePrivacy Regulation) that will affect Facebook and others, but it hasn't been passed yet.
I haven't heard of any privacy/GDPR/ePD changes recently other than the EU-US Privacy Shield invalidation.
Is there anything I can read on the changes you're talking about?
> ...lawyers spoke to the EU and were told this needs to happen right away
Sorry but this is not how EU works and it doesn't make any sense at all.
You can't "speak with the EU", in the same way you can't "speak with the United States of America".
You can speak with a data regulator in a specific country if you wish so. But each one of them is also part of the European Data Protection Board, which ensures the consistent application of data protection rules throughout the EU.
I can understand lawyers speaking with one of the regulators, and been told about the ePR "ePrivacy Regulation" proposal that looks to repeal the ePD "ePrivacy Directive".
But we live in a sane world (at least here in the EU) where impactful regulations and directives don't change overnight without any notice and implementation period. The ePR "ePrivacy Regulation" draft suggests a 24-month transition period, similar what happened with GDPR which was agreed in 2016 and went live in 2018. So the earliest ePR will take effect as of today is 2023.
Having some "lawyers speak with the EU" about some unannounced "internal material" that "need to happen right away" doesn't make sense.
So no, I don't see how your or Facebook changes were influenced by ePD "ePrivacy Directive" from 2002/2009.
You should've said December 21st straight away! I now have found what you're talking about.
On December 21st, a 2018 European Electronic Communications Code (EECC) directive goes live on 21st of December 2020.
It's a directive to consolidate and reform the framework for the regulation of electronic communications services and networks in the EEA.
> Under the EECC, the scope of electronic communication services will be expanded to include over-the-top/online communication services. Therefore, providers of VoIP services and other online communication apps (video, chat, messaging) will be subject to telecoms regulation and by extension the ePrivacy Directive.
> For the foreseeable future, those caught by the provisions of the ePD will continue to need to comply, taking into account the interplay with the ever-evolving guidance and case law on the GDPR (e.g. on consent, notice, etc.), which will often apply in the context of the application of the ePD. The ePD rules have not been kept up to date with the latest technological developments and are also not well aligned to the enhanced protections of the GDPR.
I was wrong, the changes are influenced by ePD, but indirectly because of the broadening definition of electronic communication services. Finally we're there. I'm surprised no one else commented about this earlier and it took so much time to understand why this is happening.
Kafka also has a KIP to get rid of Zookeeper and I see a bunch of the issues related to the KIP resolved and looks like it should be happening this year.
Doesn't this just internalize the dependency within the project itself? Isn't Redpanda taking on all the effort that Zookeeper has been doing for years, all the edge cases, all the additional support and now the coupling of it within the very project itself?
That is our essential complexity. If you are trying to replicate data to machines, you need to replicate data to machines. We chose raft as the only way. In essence we are much simpler than upstream w.r.t protocols for data replication.
This one is fascinating - especially the slides from the JavaOne presentation. It JITs heavily-used R3000 blocks into Java bytecode, which is then JITted by the Java interpreter. And he did it 14 years ago!
Are you asking in general? That’s one of the first things a student learns in middle school English is that the title is all capitalized except for words like “the, to, and, or”, unless those words are at the beginning of the title.
This site looks like it has the rules more formalized, if you’re interested. I think it’s something most native English writers do without thinking by adulthood.
I've often noticed this pattern but only ask myself now, so, yes, in general. From what I remember I never learnt that in school, but I'm obviously not a native English writer. @Raphmedia already gave me a good link, but thank you for the one you gave me too.
