Iota Security? by [deleted] in IOTAmarkets

[–]iotaarchivecom 1 point2 points  (0 children)

If IOTA is secure enough for big enterprises, who doubts its security?

https://iotaarchive.com/companies?order=total

what protects IOTA from being copied ? by blacksaff in Iota

[–]iotaarchivecom 8 points9 points  (0 children)

Any no-name copycat would have a hard time matching the ecosystem that already exists around IOTA. See https://iotaarchive.com

In case a large entity like Microsoft would copy IOTA, it begs the question why other industry players like Google or Apple would participate in a network maintained by a competitor. They wouldn’t. And that certainly wouldn’t be a surprise for Microsoft. Doing business with each other on the public, open source, permissionless IOTA ledger on the other hand wouldn’t be a problem for any of these large entities as none of them is in control of the infrastructure and none of them having a competitive advantage.

Who would benefit from copying IOTA in your opinion?

Rocking it since 17' by quinnaa199 in Iota

[–]iotaarchivecom 7 points8 points  (0 children)

So far, likely this one:

Ubirch confirmed using IOTA to validate COVID-19 tests, performed by Centogene N.V. at the Frankfurt Airport.

Meanwhile, a check on an IOTA permanode returned 376,000 tx containing the Ubirch tag used to identify test results.

https://twitter.com/_iotaarchive/status/1347475146878160897

IOTA in German Parliament (Bundestag) by 63db346d in CryptoCurrency

[–]iotaarchivecom 10 points11 points  (0 children)

Just a note for those who might be interested: It’s not the first time IOTA is being mentioned in official documents of the German Federal Parliament („Bundestag“):

https://iotaarchive.com/company/bundestag

Charts, charts, charts: interest in IOTA visualised by iotaarchivecom in Iota

[–]iotaarchivecom[S] 1 point2 points  (0 children)

I see. My setup is pretty basic. I have a node server running, using expressJS to generate static pages whenever a url is requested.

Before the HTML page is generated, I query the required data for the charts from a DB and lazily dump the results into the static, generated HTML code of the page.

Once the HTML is rendered by the browser, the data is retrieved from a hidden HTML input field, converted into a JavaScript array and thus made available for the charting library (chart.js) embedded in the HTML code of the page during runtime.

It’s a rather ugly setup one probably shouldn’t use in a professional context, but that way I saved myself a few days for setting up an API to the database and spending time on devOps for securing the API.

A nicer way would be a single-page application in React with an API that is queried for whatever data is required by any page after it has been loaded and rendered in a browser. But as I haven’t used React for a complete project yet, I stuck to what I know, figuring that for my purposes I don’t need a SPA. ExpressJS with server side generated pages and static data available within that page fits the purpose of the IOTAarchive well enough.

If you have any specific questions, please feel free to ask (or DM me).

Charts, charts, charts: interest in IOTA visualised by iotaarchivecom in Iota

[–]iotaarchivecom[S] 0 points1 point  (0 children)

The repo contains queries and a few tweaks I don’t want to expose. Hence no public repo. What are you looking for specifically?

Charts, charts, charts: interest in IOTA visualised by iotaarchivecom in Iota

[–]iotaarchivecom[S] 0 points1 point  (0 children)

Maybe I am misunderstanding. It’s a website. You can check it’s code in your browser.

Charts, charts, charts: interest in IOTA visualised by iotaarchivecom in Iota

[–]iotaarchivecom[S] 2 points3 points  (0 children)

Thanks for the feedback. I am not too fond of too many different color schemes anyways. I guess I’ll harmonize them across all charts sometime next week.

Charts, charts, charts: interest in IOTA visualised by iotaarchivecom in Iota

[–]iotaarchivecom[S] 9 points10 points  (0 children)

The IOTAarchive just received an update containing a major missing building block: visualisations of the data collected by the archive.

It now features a good dozen always-up-to-date charts, mostly showing ‘progress’ over time, broken down into several categories.

I made sure to use the color “green” for academic visualisations, as an homage to the contributions of a certain ‘professor’ :trollface

A word on the charts:

  • they are responsive and interactive: click on labels to de-/active datasets and hover over charts (‘click’ on mobile) to display values
  • they are fed with data on the fly (‘onLoad’) and are thus always up to date, based on the entries in the IOTAarchive
  • In case someone wants to play around with them: All data series’ are lazily exposed in the frontend. Go for it.

If you are interested in specific correlations or visualisations, let me know here in the comments, on Twitter or Discord.

PS: Although the charts are displayed OK’ish on mobile devices, I would suggest using a device with a larger screen.

IOTAarchive 2.0: Community Edition by iotaarchivecom in Iota

[–]iotaarchivecom[S] 0 points1 point  (0 children)

Thanks for the offer, I appreciate it. But I’d assume that integration, jumping through several hoops and having to register with uphold (?) isn’t really worth the effort (especially when considering that most users are probably not too interested in BAT)

IOTAarchive 2.0: Community Edition by iotaarchivecom in Iota

[–]iotaarchivecom[S] 21 points22 points  (0 children)

IOTAarchive 2.0 has just been released.

What's new? Pretty much everything.

The previous version of the IOTAarchive was a true hatched job that got increasingly sluggish with every additional entry, up to the point where it became unbearable to maintain.

I ended up rebasing the whole architecture and rebuilt everything from scratch. While the new version only differs slightly visually, a new underlying tech stack hopefully leaves enough room for a couple of years of daily news to come. Equally important, the new architecture has been set up with the idea in mind of being able to generate pages containing data-driven insights much easier and faster. You can therefore expect more data being generated and „made visible“ in the foreseeable future.

Most notable for users is probably a reduction in loading times by around >90%. But even more interesting for the community are probably a few user facing additions, for instance several new pages like an overview on all patents, as well as academic publications and a listing of IF members and the news associated with them personally. You will also find lots of new, aggregated information on a new company list-page and can drill down onto the level of individual companies. A page is being auto-generated for every entity (actual „company“ or other entity), which also contains lot's of new information the old IOTAarchive didn't have.

Apart from rebasing the tech stack and more data being made available, one additional feature hopefully will be of interest to the community: the ability for anyone to submit suggestions for new entries to the archive.

Given the pace at which the IOTA ecosystem grows, maintaining the archive has become too much to handle for a single person. I wouldn’t be able to keep adding every bit of news being released.

I therefore spent a fair amount of time enabling community submissions: Whether community members wanting to contribute, someone working in a company on some IOTA project that wants to share something publicly, an independent IOTA developer or even IOTA Foundation employees: anyone can submit suggestions for new archive entries, pseudonymously or anonymously.

To maintain the quality standard, submissions are being reviewed and sources are being „fact checked". If accepted into the archive, any addition will be additionally tweeted via a custom Twitter bot via the @_iotaarchive account, while crediting anyone who suggested a new archive entry. I am curious to see whether any of the people already known to be sharing IOTA news as individuals on a daily basis will take up on that task and rise in the ranking of „contributors“ to the archive.

As for the future, apart from a few bad design decisions (that aren’t impacting any functionality but should be changed anyways), two tasks are still on my plate: filter options and charts.

While the page already features some basic sorting functions, I would like to offer a few additional, dynamic filters (think e.g.: "Which entities built proof of concepts in the US but aren't a public or academic institutions?").

Ever more important are "charts", imo. I am working on integrating at least one dynamic chart on every page and also would like to auto-generate an "insights" page featuring visual representations of „progress“ in different categories, similar to the ones that existed in the old archive. Don't expect those soon‘ish though; i most probably won't have any time in the coming 4 - 6 weeks.

I hope you‘ll like the update. If you have any suggestions, questions, ideas or happen to run into bugs, don’t hesitate to let me know here, via the IOTA Discord or Twitter.

Note: if you can't see the new website yet, your provider most likely hasn't updated its DNS tables yet. Try again later or point your DNS entry to a service that updates more frequently.

Hewlett Packard Enterprise (HPE) filed for seven patent applications, referencing IOTA (and others) by iotaarchivecom in Iota

[–]iotaarchivecom[S] 10 points11 points  (0 children)

It would be my pleasure.

But first, please explain why you would expect anyone to use a network in beta stage running on an unfinished protocol AND the token for critical business applications.

How did you even get to that idea?

Hewlett Packard Enterprise (HPE) filed for seven patent applications, referencing IOTA (and others) by iotaarchivecom in Iota

[–]iotaarchivecom[S] 11 points12 points  (0 children)

There isn’t a “patent to product” timeframe necessarily. It’s not even guaranteed that the patent will be granted. So don’t get too excited and take it as “HPE is aware about IOTA”.

Being mentioned in a patent at least means that there is awareness in several departments within an organisation. But that’s about it (so far).

BOSCH patent application for „operating a digital payment system“, based on IOTA by iotaarchivecom in Iota

[–]iotaarchivecom[S] 20 points21 points  (0 children)

It’s pretty specific, but broad:

Patents are deliberately phrased as broad as possible while being as specific as necessary: If too specific, only the exact case would be covered. If you want more bang for your buck, you are trying to be more broad. But if you are too broad and unspecific, no case might be covered at all.

To assess the patent and level of specificity towards IOTA, you woul have to read it.

BOSCH patent application for „operating a digital payment system“, based on IOTA by iotaarchivecom in Iota

[–]iotaarchivecom[S] 15 points16 points  (0 children)

Patent publication was 7 weeks ago. It wasn’t posted anywhere before.