home.social

#ldes — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ldes, aggregated by home.social.

  1. Ore Energy Completes EU-Funded Multi-Day Energy Storage Pilot At EDF R&D Laboratories In France

    100-Hour Iron-Air Long-Duration Energy Storage (LDES) System Piloted Under The European Union’s “StoRIES” Programme AMSTERDAM, February 10, 2026…
    #France #FR #Europe #EU #ÉlectricitédeFrance #battery #BESS #EDF #energystorage #grid #iron-air #LDES
    europesays.com/france/18939/

  2. #EnergyMastodon
    Gee, I wonder if the US funding cuts are finally affecting our National Laboratories?

    Sandia @SandiaLabs wants to outsource the leadership of the National Consortium for the Advancement of Long Duration Energy Storage #LDES Technologies, but won't pay a penny towards the job!

  3. #EnergyMastodon
    Gee, I wonder if the US funding cuts are finally affecting our National Laboratories?

    Sandia @SandiaLabs wants to outsource the leadership of the National Consortium for the Advancement of Long Duration Energy Storage #LDES Technologies, but won't pay a penny towards the job!

  4. #EnergyMastodon
    Gee, I wonder if the US funding cuts are finally affecting our National Laboratories?

    Sandia @SandiaLabs wants to outsource the leadership of the National Consortium for the Advancement of Long Duration Energy Storage #LDES Technologies, but won't pay a penny towards the job!

  5. #EnergyMastodon
    Gee, I wonder if the US funding cuts are finally affecting our National Laboratories?

    Sandia @SandiaLabs wants to outsource the leadership of the National Consortium for the Advancement of Long Duration Energy Storage #LDES Technologies, but won't pay a penny towards the job!

  6. #EnergyMastodon
    Gee, I wonder if the US funding cuts are finally affecting our National Laboratories?

    Sandia @SandiaLabs wants to outsource the leadership of the National Consortium for the Advancement of Long Duration Energy Storage #LDES Technologies, but won't pay a penny towards the job!

  7. @GuillaumeRossolini
    You are indirectly talking about the need for long-duration energy storage #LDES, and especially seasonal energy storage. Saving up energy to last for the average 14-day Dunkelflaute is important in all locales. And yes, seasonal storage for getting through the winter is also very important. And yes, most analysts agree that for 2+ weeks of LDES, including seasonal storage, hydrogen is the lowest cost storage vector.

  8. AccelerateEU ‘emergency toolbox’ policy on fossil fuel dependence falls short on energy storage, trade groups say

    AccelerateEU ‘emergency toolbox’ policy on fossil fuel dependence falls short on energy storage, trade groups say – Energy-St…
    #Energy #Advocacy #electricitymarketdesign #electrification #energysecurity #EnergyStorageEurope #EuropeanCommission #EuropeanUnion #flexibility #fossilfuels #ldes #long-durationenergystorage #supplychain #tradeassociation
    europesays.com/2939276/

  9. Devon is testing pumped hydro without mountains: a 500 kW pilot using a fluid ~2.5× denser than water to make “hillside batteries” viable on gentler slopes. The bigger story: #LDES is often a permitting + finance problem, not a tech problem
    climatetech.industryexaminer.c
    #ClimateTech #EnergyStorage #TechNews

  10. On-site solar PV, 32MW PEM electrolyzer using reclaimed mine water, 41hr of hydrogen storage in steel tanks, running #H2 through 7.5MW PEM fuel cells, all installed on a Questa, NM brownfield site!

    Now that's a long-duration energy storage / seasonal energy storage demo!
    #hydrogen #grid #LDES #PV #solar #fuelcell #electrolyzer

  11. Eight energy trends that will shape energy storage in 2026

    Short-duration battery energy storage systems (BESS) will continue playing a critical role in frequency control, congestion management, and…
    #Energy #australia #Cybersecurity #data-centres #dc-coupled #energystorage #energystorageaus #fluence #gridforming #ldes #nem #policy #sociallicense #solarplusstorage #StorageAus
    europesays.com/2610957/

  12. Next week we’re hosting the second in-person #LDES workshop at #SEMIC2025.

    Piotr Sowiński will be the keynote speaker. He developed Jelly, a binary RDF format for syncing RDF datasets at speeds we can only aspire to.

    What is his opinion about the work we’re doing? What can we learn from eachother? Looking forward to the talk and the discussion!

  13. Ambri, the 2010 MIT spinout and liquid metal battery company that targeted long duration energy storage #LDES, is no more.

    This is why the MIT startup ecosystem calls hard tech "hard tech."
    #hardtech

  14. Ambri, the 2010 MIT spinout and liquid metal battery company that targeted long duration energy storage #LDES, is no more.

    This is why the MIT startup ecosystem calls hard tech "hard tech."
    #hardtech

  15. Ambri, the 2010 MIT spinout and liquid metal battery company that targeted long duration energy storage #LDES, is no more.

    This is why the MIT startup ecosystem calls hard tech "hard tech."
    #hardtech

  16. @pietercolpaert Is there a document that compares #LDES with related methods of synchronization such as Revsion Control Systems, OAI-PMH, ResourceSync? It looks like the problem to be solved is a variant of the Cache Invalidation in "Only two hard problems in Computer Science".

  17. After 4 years of this blog post being in draft, I’ve just published the initial motivation for working on Linked Data Event Streams #LDES and kept the date at which it was planned to appear: pietercolpaert.be/ldes/2021/09

    It elaborates on the maintenance hell for APIs and replication hell with dumps, and how we are fighting this status quo with the #SEMIC LDES initiative.

  18. AI and automation are changing how we manage Long Duration Energy Storage—but at what risk? ⚠️

    Explore our latest blog on LDES vulnerabilities, risk mitigation, and regulatory needs.
    🔗 ampyxcyber.com/blog/automation

    #LDES #Cybersecurity #AI #EnergyTech

  19. Tomorrow, 22d of May, the #SEMIC Community Workshop on Linked Data Event Streams will take place.

    For the first time during an #LDES workshop, we’ll have duo presentations with each time someone representing a producer, with right after getting the consumer’s perpective.

    interoperable-europe.ec.europa

  20. California: "…Pacific Steel breaks ground on state’s first new steel mill in 50 yrs"
    Mojave Micro Mill (electric arc furnace #EAF) will be very green, with
    ᛫ Behind the meter solar PV #PV,
    ᛫ Long duration battery energy storage #LDES #BESS,
    ᛫ No natural gas use #natgas,
    ᛫4-step exhaust cleanup (selective non-catalytic reduction #SNCR, 2 baghouses in series, wet scrubber, activated carbon injection),
    ᛫ Carbon dioxide capture & liquefaction…

  21. California: "…Pacific Steel breaks ground on state’s first new steel mill in 50 yrs"
    Mojave Micro Mill (electric arc furnace #EAF) will be very green, with
    ᛫ Behind the meter solar PV #PV,
    ᛫ Long duration battery energy storage #LDES #BESS,
    ᛫ No natural gas use #natgas,
    ᛫4-step exhaust cleanup (selective non-catalytic reduction #SNCR, 2 baghouses in series, wet scrubber, activated carbon injection),
    ᛫ Carbon dioxide capture & liquefaction…

  22. California: "…Pacific Steel breaks ground on state’s first new steel mill in 50 yrs"
    Mojave Micro Mill (electric arc furnace #EAF) will be very green, with
    ᛫ Behind the meter solar PV #PV,
    ᛫ Long duration battery energy storage #LDES #BESS,
    ᛫ No natural gas use #natgas,
    ᛫4-step exhaust cleanup (selective non-catalytic reduction #SNCR, 2 baghouses in series, wet scrubber, activated carbon injection),
    ᛫ Carbon dioxide capture & liquefaction…

  23. Hey BGS #BritGeoSurvey you missed the topline headline:

    The UK has successfully stored hydrogen in underground salt caverns at Teesside since 1972.

    #hydrogen101 #hydrogen #H2 #LDES #NetZero

  24. Hey BGS #BritGeoSurvey you missed the topline headline:

    The UK has successfully stored hydrogen in underground salt caverns at Teesside since 1972.

    #hydrogen101 #hydrogen #H2 #LDES #NetZero

  25. Hey BGS #BritGeoSurvey you missed the topline headline:

    The UK has successfully stored hydrogen in underground salt caverns at Teesside since 1972.

    #hydrogen101 #hydrogen #H2 #LDES #NetZero

  26. Hey BGS #BritGeoSurvey you missed the topline headline:

    The UK has successfully stored hydrogen in underground salt caverns at Teesside since 1972.

    #hydrogen101 #hydrogen #H2 #LDES #NetZero

  27. Hey BGS #BritGeoSurvey you missed the topline headline:

    The UK has successfully stored hydrogen in underground salt caverns at Teesside since 1972.

    #hydrogen101 #hydrogen #H2 #LDES #NetZero

  28. Want to widen your set of skills with Linked Data/RDF, #knowledgegraphs, #LDES, Solid, ontologies, Web APIs, data interoperability, etc?

    All our courses are now listed on our website! Next up: the VAIA/UGain course on Linked Data & Solid starting September!

    knows.idlab.ugent.be/education

  29. Arrived in Paris for a workshop with data portal maintainers across Europe. Tomorrow I'm giving a talk on #LDES for exchanging #DCAT-AP feeds.

  30. Our team is at #SEMANTiCS2024! We have contributions on:
    * “No more raw data!”, and how to always envelope data with trust by @rubenverborgh and @besteves4
    * RDF Lens as a way to create reusable and composable transformations of triples into objects for developers by Arthur Vercruysse (ceur-ws.org/Vol-3759/paper13.p)
    * Linked Data Event Streams within cultural heritage #LDES by me at 14:00 today

  31. A team from #Rijksmuseum Amsterdam reviewed several solutions for #sync of up-to-date information:
    1️⃣ OAI-PMH
    2️⃣ ResourceSync
    3️⃣ Git
    4️⃣ #LinkedData Notifications
    5️⃣ Linked Data Event Streams
    6️⃣ #IIIF Change Discovery

    Read in this blogpost which solution they chose for the Colonial Collections Datahub: theartofinformationblog.wordpr
    #museumdocumentation #ColonialHeritage #openGLAM #LDES

  32. Presenting YARRRML+LDES demo at to easily generate versioned knowledge graphs of your data!

    @pietercolpaert

  33. My #SolidProject client and server are now ready for efficient access control demos on #BigData using the HTTP WG's 's "Signing HTTP Messages".

    I can demo with a server publishing N resources (in this case, #LinkedData Event Stream (#LDES) data.
    The client is implemented in #Scala using #http4s, and the server uses #Akka.
    The libraries can be compiled to JS for use on #nodeJS frameworks too. Native is not far off, either.
    The client need make no more than N+2 requests:

    1. Request 1 on a resource R returning a "401 Unauthorised"
    2. a max of 2 requests to get the access control rules
    3. from there on, N signed requests using #HttpSignatures (when those all fall in the same container space)

    Solid clients are essentially like Search Engine crawlers fetching data on the web, so they need to jump around from website to website. Having approx 2 requests extra per website for auth is very interesting in that scenario.

    Note: those 2 requests can be cached, so those may be only needed once over a long period of time. The connection efficiency is possible by combining the following pieces:

    • using the IETF's HTTPSig (a version from the beginning of the year)
    • using default rules (part of the spec)
    • caching of ACLs on the client
    • the use of a "defaultAccessContainer" link header to reduce the number of requests.

    I am trying to work out who may be interested in such a technical demo, what a good time for it may be, ...
    so please just comment here or send me a mail at [email protected]

  34. My #SolidProject client and server are now ready for efficient access control demos on #BigData using the HTTP WG's 's "Signing HTTP Messages".

    I can demo with a server publishing N resources (in this case, #LinkedData Event Stream (#LDES) data.
    The client is implemented in #Scala using #http4s, and the server uses #Akka.
    The libraries can be compiled to JS for use on #nodeJS frameworks too. Native is not far off, either.
    The client need make no more than N+2 requests:

    1. Request 1 on a resource R returning a "401 Unauthorised"
    2. a max of 2 requests to get the access control rules
    3. from there on, N signed requests using #HttpSignatures (when those all fall in the same container space)

    Solid clients are essentially like Search Engine crawlers fetching data on the web, so they need to jump around from website to website. Having approx 2 requests extra per website for auth is very interesting in that scenario.

    Note: those 2 requests can be cached, so those may be only needed once over a long period of time. The connection efficiency is possible by combining the following pieces:

    • using the IETF's HTTPSig (a version from the beginning of the year)
    • using default rules (part of the spec)
    • caching of ACLs on the client
    • the use of a "defaultAccessContainer" link header to reduce the number of requests.

    I am trying to work out who may be interested in such a technical demo, what a good time for it may be, ...
    so please just comment here or send me a mail at [email protected]

  35. My #SolidProject client and server are now ready for efficient access control demos on #BigData using the HTTP WG's 's "Signing HTTP Messages".

    I can demo with a server publishing N resources (in this case, #LinkedData Event Stream (#LDES) data.
    The client is implemented in #Scala using #http4s, and the server uses #Akka.
    The libraries can be compiled to JS for use on #nodeJS frameworks too. Native is not far off, either.
    The client need make no more than N+2 requests:

    1. Request 1 on a resource R returning a "401 Unauthorised"
    2. a max of 2 requests to get the access control rules
    3. from there on, N signed requests using #HttpSignatures (when those all fall in the same container space)

    Solid clients are essentially like Search Engine crawlers fetching data on the web, so they need to jump around from website to website. Having approx 2 requests extra per website for auth is very interesting in that scenario.

    Note: those 2 requests can be cached, so those may be only needed once over a long period of time. The connection efficiency is possible by combining the following pieces:

    • using the IETF's HTTPSig (a version from the beginning of the year)
    • using default rules (part of the spec)
    • caching of ACLs on the client
    • the use of a "defaultAccessContainer" link header to reduce the number of requests.

    I am trying to work out who may be interested in such a technical demo, what a good time for it may be, ...
    so please just comment here or send me a mail at [email protected]

  36. My #SolidProject client and server are now ready for efficient access control demos on #BigData using the HTTP WG's 's "Signing HTTP Messages".

    I can demo with a server publishing N resources (in this case, #LinkedData Event Stream (#LDES) data.
    The client is implemented in #Scala using #http4s, and the server uses #Akka.
    The libraries can be compiled to JS for use on #nodeJS frameworks too. Native is not far off, either.
    The client need make no more than N+2 requests:

    1. Request 1 on a resource R returning a "401 Unauthorised"
    2. a max of 2 requests to get the access control rules
    3. from there on, N signed requests using #HttpSignatures (when those all fall in the same container space)

    Solid clients are essentially like Search Engine crawlers fetching data on the web, so they need to jump around from website to website. Having approx 2 requests extra per website for auth is very interesting in that scenario.

    Note: those 2 requests can be cached, so those may be only needed once over a long period of time. The connection efficiency is possible by combining the following pieces:

    • using the IETF's HTTPSig (a version from the beginning of the year)
    • using default rules (part of the spec)
    • caching of ACLs on the client
    • the use of a "defaultAccessContainer" link header to reduce the number of requests.

    I am trying to work out who may be interested in such a technical demo, what a good time for it may be, ...
    so please just comment here or send me a mail at [email protected]

  37. My #SolidProject client and server are now ready for efficient access control demos on #BigData using the HTTP WG's 's "Signing HTTP Messages".

    I can demo with a server publishing N resources (in this case, #LinkedData Event Stream (#LDES) data.
    The client is implemented in #Scala using #http4s, and the server uses #Akka.
    The libraries can be compiled to JS for use on #nodeJS frameworks too. Native is not far off, either.
    The client need make no more than N+2 requests:

    1. Request 1 on a resource R returning a "401 Unauthorised"
    2. a max of 2 requests to get the access control rules
    3. from there on, N signed requests using #HttpSignatures (when those all fall in the same container space)

    Solid clients are essentially like Search Engine crawlers fetching data on the web, so they need to jump around from website to website. Having approx 2 requests extra per website for auth is very interesting in that scenario.

    Note: those 2 requests can be cached, so those may be only needed once over a long period of time. The connection efficiency is possible by combining the following pieces:

    • using the IETF's HTTPSig (a version from the beginning of the year)
    • using default rules (part of the spec)
    • caching of ACLs on the client
    • the use of a "defaultAccessContainer" link header to reduce the number of requests.

    I am trying to work out who may be interested in such a technical demo, what a good time for it may be, ...
    so please just comment here or send me a mail at [email protected]

  38. @nichtich I'm glad if I receive that for consumption.

    For publishing the higher cost seems to come from ensuring we have the data with sufficient quality. Offering different formats is relatively cheap. We do #sparql and #turtle by default for most of the data, depending on where it's shared. #LDES is coming soon for most of those. Adding #HDT could be nice over time.

    More adoption is more fun.