🔗 https://cynthia.dev - 🏢 IRIT - 📍 Toulouse, France
The Internet should NEVER take such a widespread hit because of a single entity. It's DESIGNED to not be this way. Megacorporations killed the real Internet
The Internet should NEVER take such a widespread hit because of a single entity. It's DESIGNED to not be this way. Megacorporations killed the real Internet
Our website is now live! If you want to get an idea of what the .meow Foundation is all about, what our mission statement is or you just want to look at pictures of the beautiful people involved, you can do so at dotmeow.org/en/what/
Go give it a look!!
Our website is now live! If you want to get an idea of what the .meow Foundation is all about, what our mission statement is or you just want to look at pictures of the beautiful people involved, you can do so at dotmeow.org/en/what/
Go give it a look!!
We need help completing Elixir's browser runtime by porting some Erlang functions to JavaScript.
No Erlang knowledge required. Each function unlocks multiple Elixir stdlib functions!
More here: hologram.page/blog/elixir-...
#Hologram #Elixir #ElixirLang #BEAM #WebDev
We need help completing Elixir's browser runtime by porting some Erlang functions to JavaScript.
No Erlang knowledge required. Each function unlocks multiple Elixir stdlib functions!
More here: hologram.page/blog/elixir-...
#Hologram #Elixir #ElixirLang #BEAM #WebDev
Signed,
Someone who lost an email because TB panicked trying to encrypt it and lost it because gpg is GARBAGE
Signed,
Someone who lost an email because TB panicked trying to encrypt it and lost it because gpg is GARBAGE
SOGo sucks ass and uses the custom property `X-SOGO-SEND-APPOINTMENT-NOTIFICATIONS:NO` to not send email notifications on its own instead of the complying with standards :/
SOGo sucks ass and uses the custom property `X-SOGO-SEND-APPOINTMENT-NOTIFICATIONS:NO` to not send email notifications on its own instead of the complying with standards :/
SOGo sucks ass and uses the custom property `X-SOGO-SEND-APPOINTMENT-NOTIFICATIONS:NO` to not send email notifications on its own instead of the complying with standards :/
SOGo sucks ass and uses the custom property `X-SOGO-SEND-APPOINTMENT-NOTIFICATIONS:NO` to not send email notifications on its own instead of the complying with standards :/
sharing is a single click, it's easily archivable and browsable (internally or publically), zero vendor lock-in, hrmm
sharing is a single click, it's easily archivable and browsable (internally or publically), zero vendor lock-in, hrmm
```json
{
"€kind": ...
...
}
```
```json
{
"€kind": ...
...
}
```
an open issue burried deep in the tracker doesn't cause noise, that's straight up bullshit. it's just bad project management that leaves lots of valid bugs and use-cases unanswered, ughh
an open issue burried deep in the tracker doesn't cause noise, that's straight up bullshit. it's just bad project management that leaves lots of valid bugs and use-cases unanswered, ughh
For a lot of use-cases losing access to user-generated content can be a significant loss of knowledge, yet the canonical source of a user's data can disappear overnight without notice
For a lot of use-cases losing access to user-generated content can be a significant loss of knowledge, yet the canonical source of a user's data can disappear overnight without notice
No more dealing with Yarn/Mojmaps, nor weird edge cases introduced by obfuscation, and most definitely faster build times now that (de)obf is no longer a thing!!!
www.minecraft.net/en-us/articl...
No more dealing with Yarn/Mojmaps, nor weird edge cases introduced by obfuscation, and most definitely faster build times now that (de)obf is no longer a thing!!!
www.minecraft.net/en-us/articl...
So to help you get started, here's a big one:
https://drive.proton.me/urls/ENZ7VZW9CG#MazXhWgb1yIp
So to help you get started, here's a big one:
https://drive.proton.me/urls/ENZ7VZW9CG#MazXhWgb1yIp
I wish there was a way to restrict the trigger to a branch (i.e. don't use the spec from another branch) and accept a ref (with the fancy selector) as dispatch input :(
I wish there was a way to restrict the trigger to a branch (i.e. don't use the spec from another branch) and accept a ref (with the fancy selector) as dispatch input :(