home.social

#complicated — Public Fediverse posts

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

  1. ... such as not enforcing licensee #compliance with #conditions.”

    The proposed amendments continue to promote the notion that #water #licenses are 'property #rights’ rather than a ‘right of use’. The FITFIR approach to water #management has inherent limitations considering the anticipated water regimes under prolonged #drought scenarios under #climateChange. These limitations are #complicated by the notion of #property rights.

    10/24

  2. Iran war deaths could resurface Trump’s complicated history with military sacrifice

    misryoum.com/us/us-news/iran-w

    It’s delicate for any president to watch flag-draped transfer cases return home from overseas, a solemn tradition that honors the dead and shines a spotlight on the human costs of conflict.Donald Trump’s visit Saturday to Dover Air Force Base, honoring...

    #Iran #war #deaths #could #resurface #Trumps #complicated #history #with #military #sacrifice #US_News_Hub #misryoum_com

  3. Another thing about #evil is that it's always #complicated. That's another #engineering #principle that all but guarantees in the short term their failure. #Humankind has cycled forward, brutally slowly, generations would argue that that shit never happens, #history says inching forward.

  4. Another thing about #evil is that it's always #complicated. That's another #engineering #principle that all but guarantees in the short term their failure. #Humankind has cycled forward, brutally slowly, generations would argue that that shit never happens, #history says inching forward.

  5. Beim anlegen eine SoS #39c3
    Was soll ich denn als Ort angeben? Und Zeit?
    #complicated

  6. Many #recycling programs are a farce. Every #recycler has a huge list of wants/don't wants. The little triangles on things are.....wtf? It's TOO #COMPLICATED for the #masses. Fuck recycling.

    #Biodegradable materials are where it's at. People are lazy. The solution MUST also be #lazy. If the general public need to think, they won't do it. That's why we have an orange clown taking a wrecking ball to the #planet.

  7. #Decentralized #Module #Federation #Microfrontend #Architecture

    I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

    How it will be #architected: [positive-intentions.com/blog/d
    Some #benefits of the #approach: [positive-intentions.com/blog/s

    I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

    When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

    #Cryptography modules - cryptography.positive-intentio

    #P2P framework - p2p.positive-intentions.com/?p

    This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

    #P2P chat - [chat.positive-intentions.com/]
    #P2P file transfer - [file.positive-intentions.com/]

    The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

    I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

    Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

    (mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

  8. #Decentralized #Module #Federation #Microfrontend #Architecture

    I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

    How it will be #architected: [positive-intentions.com/blog/d
    Some #benefits of the #approach: [positive-intentions.com/blog/s

    I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

    When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

    #Cryptography modules - cryptography.positive-intentio

    #P2P framework - p2p.positive-intentions.com/?p

    This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

    #P2P chat - [chat.positive-intentions.com/]
    #P2P file transfer - [file.positive-intentions.com/]

    The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

    I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

    Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

    (mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

  9. #Decentralized #Module #Federation #Microfrontend #Architecture

    I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

    How it will be #architected: [positive-intentions.com/blog/d
    Some #benefits of the #approach: [positive-intentions.com/blog/s

    I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

    When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

    #Cryptography modules - cryptography.positive-intentio

    #P2P framework - p2p.positive-intentions.com/?p

    This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

    #P2P chat - [chat.positive-intentions.com/]
    #P2P file transfer - [file.positive-intentions.com/]

    The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

    I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

    Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

    (mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

  10. #Decentralized #Module #Federation #Microfrontend #Architecture

    I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

    How it will be #architected: [positive-intentions.com/blog/d
    Some #benefits of the #approach: [positive-intentions.com/blog/s

    I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

    When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

    #Cryptography modules - cryptography.positive-intentio

    #P2P framework - p2p.positive-intentions.com/?p

    This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

    #P2P chat - [chat.positive-intentions.com/]
    #P2P file transfer - [file.positive-intentions.com/]

    The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

    I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

    Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

    (mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

  11. #Decentralized #Module #Federation #Microfrontend #Architecture

    I'm working on a #webapp and I'm being #creative on the #approach. It might be considered #overcomplicated (because it is), but I'm just trying something out. It's entirely possible this approach won't work #longterm. I see it as there is #onewaytofindout. I don't recommend this approach. Just sharing what I'm trying/#investigating.

    How it will be #architected: [positive-intentions.com/blog/d
    Some #benefits of the #approach: [positive-intentions.com/blog/s

    I find that #modulefederation and #microfrontends to generally be #discouraged when I see posts, but I think it works for me in my #approach. I'm #optimistic about the approach and the #benefits and so I wanted to #share details.

    When I serve the #federatedmodules, I can also host the #storybook statics so I think this could be a good way to #document the modules in #isolation.

    #Cryptography modules - cryptography.positive-intentio

    #P2P framework - p2p.positive-intentions.com/?p

    This way, I can create #microfrontends that consume these #modules. I can then #share the #functionality between #apps. The following apps are using a different codebase from each other (there is a #distinction between these apps in #opensource and #closesource). Sharing those #dependencies could help make it easier to roll out #updates to #coremechanics.

    #P2P chat - [chat.positive-intentions.com/]
    #P2P file transfer - [file.positive-intentions.com/]

    The #functionality also works when I create an #Android build with #Tauri. This could also lead to it being easier to create #newapps that could use the #modules created.

    I'm sure there will be some distinct #test/#maintenance #overhead, but depending on how it's #architected I think it could work and make it easier to #improve on the current #implementation.

    Everything about the #project is far from finished. It could be seen as this is a #complicated way to do what #npm does, but I think this #approach allows for greater #flexibility by being able to #separate #opensource and #closesource code for the #web. (Of course as #javascript, it will always be "source code available". Especially in the age of #AI, I'm sure it's possible to #reverseengineer it like never before.)

    (mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)

  12. 🎉 Behold the riveting #update where #GTK #developers declare #accessibility is a mystical riddle wrapped in an enigma! 🧙‍♂️ After a year of intense meditation, they've emerged with the groundbreaking insight that accessibility is... complicated! 🤯 Who knew?
    blog.gtk.org/2025/05/12/an-acc #Enigma #Complicated #Insights #HackerNews #ngated

  13. Complicated Hiking Logistics

    Reading Time: 2 minutes

    This morning I was studying the logistics for Stage 8 and 9 of the Jura Crest Trail before thinking, "This is too complicated, to be interesting". Specifically, I noticed that if we finish at Vue des Alpes we have to go via La-Chaux-De-Fonds rather than via Neuchatel. This means that if we go by car, and park in one valley, we need to take multiple trains to get back to the other valley. It has be thinking twice about hiking stages 8 and 9 of the Jura Crest trail.

    When you're planning a hike, especially with public transport it's good to plan from the location with irregular hours to one with regular hourss. With Stage eight, from Chasseral to Vue Des Alpes getting to the start of the VF is quite complicated, but what makes it more complicated is that if you drive to Neuchatel for example, to save a little on train costs, then you need to keep in mind that the Col of "Vue Des Alpes" has an irregular train schedule that will find you going to La Chaux-De-Fonds before taking you back to Neuchatel.

    According to the schedule, and how exhausted I was, I would consider walking down to Hauts-Geneveys before taking the train from there home. I know that the train from here is once an hour. It does add four kilometres to a twenty kilometre hike but it adds flexibility.Psychologically it means that I expect to walk four more kilometres. It also means that I don't expect to be stranded at the Col because I already have the next step of the journey planned.

    The journey to the start of the hike requires five changes of transport. It requires two trains, which is quite ordinary, but then requires three buses. This type of routing reminds me of London journeys.

    Summary

    After looking at options I believe that I will drive to Chambrelien or another P&Rail parking, park there, catch the trains and buses to Hotel Chasseral, and from there do the hike. I might then walk from Vue Des Alpes to Haut-Geneveys before taking the train back to Chambrelien and driving home. This will require a 0600 start so it's early. Of course if I find something more convenient I will do that.

    #buses #complicated #hiking #logistics #trains

  14. How UX Can Make Cybersecurity Feel Effortless Cybersecurity is often seen as a series of complicated and intrusive steps that require time, patience, and a certain level of technical knowledge. From multi-factor authentication to complex password requirements, these security measures...

    medium.com/design-bootcamp/the

    #designbootcamp #cybersecurity #effortless #series #complicated #intrusive

  15. How UX Can Make Cybersecurity Feel Effortless Cybersecurity is often seen as a series of complicated and intrusive steps that require time, patience, and a certain level of technical knowledge. From multi-factor authentication to complex password requirements, these security measures...

    medium.com/design-bootcamp/the

    #designbootcamp #cybersecurity #effortless #series #complicated #intrusive

  16. #30DayChartChallenge Día 15: Complicated Relationships! 🐧↔️🐧

    Hoy, una matriz de scatter plots con ggpairs para explorar las relaciones entre medidas corporales (Long. Pico, Long. Aleta, Masa Corporal) en los pingüinos de Palmer. ¡Perfecto para el prompt "Complicated"! #RelationshipsWeek #Animals

    La matriz lo enseña todo:
    * Diagonal: Distribución de cada medida (densidad).
    * Abajo: Scatter plots de cada par de medidas (coloreado por Especie).
    * Arriba: ¡La correlación $ entre ellas!

    Se ven las fuertes relaciones positivas (más grande = aleta más larga) y cómo las especies (Adelie, Chinstrap, Gentoo) forman clusters distintos en este espacio de rasgos. ¡Una forma densa de ver muchas relaciones a la vez!

    🛠 #rstats #ggplot2 #GGally | Data: #palmerpenguins | Theme: #theme_week3_animals
    📂 Código/Viz: t.ly/GATJi

    #Day15 #Complicated #dataviz #DataVisualization #Penguins #Ecology #Morphometrics #Multivariate #ggplot2 #RStats

  17. #30DayChartChallenge Día 15: Complicated Relationships! 🐧↔️🐧

    Hoy, una matriz de scatter plots con ggpairs para explorar las relaciones entre medidas corporales (Long. Pico, Long. Aleta, Masa Corporal) en los pingüinos de Palmer. ¡Perfecto para el prompt "Complicated"! #RelationshipsWeek #Animals

    La matriz lo enseña todo:
    * Diagonal: Distribución de cada medida (densidad).
    * Abajo: Scatter plots de cada par de medidas (coloreado por Especie).
    * Arriba: ¡La correlación $ entre ellas!

    Se ven las fuertes relaciones positivas (más grande = aleta más larga) y cómo las especies (Adelie, Chinstrap, Gentoo) forman clusters distintos en este espacio de rasgos. ¡Una forma densa de ver muchas relaciones a la vez!

    🛠 #rstats #ggplot2 #GGally | Data: #palmerpenguins | Theme: #theme_week3_animals
    📂 Código/Viz: t.ly/GATJi

    #Day15 #Complicated #dataviz #DataVisualization #Penguins #Ecology #Morphometrics #Multivariate #ggplot2 #RStats

  18. #30DayChartChallenge Día 15: Complicated Relationships! 🐧↔️🐧

    Hoy, una matriz de scatter plots con ggpairs para explorar las relaciones entre medidas corporales (Long. Pico, Long. Aleta, Masa Corporal) en los pingüinos de Palmer. ¡Perfecto para el prompt "Complicated"! #RelationshipsWeek #Animals

    La matriz lo enseña todo:
    * Diagonal: Distribución de cada medida (densidad).
    * Abajo: Scatter plots de cada par de medidas (coloreado por Especie).
    * Arriba: ¡La correlación $ entre ellas!

    Se ven las fuertes relaciones positivas (más grande = aleta más larga) y cómo las especies (Adelie, Chinstrap, Gentoo) forman clusters distintos en este espacio de rasgos. ¡Una forma densa de ver muchas relaciones a la vez!

    🛠 #rstats #ggplot2 #GGally | Data: #palmerpenguins | Theme: #theme_week3_animals
    📂 Código/Viz: t.ly/GATJi

    #Day15 #Complicated #dataviz #DataVisualization #Penguins #Ecology #Morphometrics #Multivariate #ggplot2 #RStats

  19. #30DayChartChallenge Día 15: Complicated Relationships! 🐧↔️🐧

    Hoy, una matriz de scatter plots con ggpairs para explorar las relaciones entre medidas corporales (Long. Pico, Long. Aleta, Masa Corporal) en los pingüinos de Palmer. ¡Perfecto para el prompt "Complicated"! #RelationshipsWeek #Animals

    La matriz lo enseña todo:
    * Diagonal: Distribución de cada medida (densidad).
    * Abajo: Scatter plots de cada par de medidas (coloreado por Especie).
    * Arriba: ¡La correlación $ entre ellas!

    Se ven las fuertes relaciones positivas (más grande = aleta más larga) y cómo las especies (Adelie, Chinstrap, Gentoo) forman clusters distintos en este espacio de rasgos. ¡Una forma densa de ver muchas relaciones a la vez!

    🛠 #rstats #ggplot2 #GGally | Data: #palmerpenguins | Theme: #theme_week3_animals
    📂 Código/Viz: t.ly/GATJi

    #Day15 #Complicated #dataviz #DataVisualization #Penguins #Ecology #Morphometrics #Multivariate #ggplot2 #RStats

  20. Día 15: Complicated Relationships! 🐧↔️🐧

    Hoy, una matriz de scatter plots con ggpairs para explorar las relaciones entre medidas corporales (Long. Pico, Long. Aleta, Masa Corporal) en los pingüinos de Palmer. ¡Perfecto para el prompt "Complicated"!

    La matriz lo enseña todo:
    * Diagonal: Distribución de cada medida (densidad).
    * Abajo: Scatter plots de cada par de medidas (coloreado por Especie).
    * Arriba: ¡La correlación $ entre ellas!

    Se ven las fuertes relaciones positivas (más grande = aleta más larga) y cómo las especies (Adelie, Chinstrap, Gentoo) forman clusters distintos en este espacio de rasgos. ¡Una forma densa de ver muchas relaciones a la vez!

    🛠 | Data: | Theme:
    📂 Código/Viz: t.ly/GATJi