What has the poor guy done? π€£
What has the poor guy done? π€£
> More than 3,600 chemicals approved for food contact in packaging, kitchenware or food processing equipment have been found in humans, new peer-reviewed research has found, highlighting a little-regulated exposure risk to toxic substances.
> More than 3,600 chemicals approved for food contact in packaging, kitchenware or food processing equipment have been found in humans, new peer-reviewed research has found, highlighting a little-regulated exposure risk to toxic substances.
james at mills dot io? π€
james at mills dot io? π€
yarnd. If there was any poorly worded "things", it was just merely pointing out lacking capabilities for caching and discovery.
yarnd. If there was any poorly worded "things", it was just merely pointing out lacking capabilities for caching and discovery.
> You can take IRC out of my cold π₯Ά dead π΅ hands π
> You can take IRC out of my cold π₯Ά dead π΅ hands π
LOL, Now substitute IRC and Discord with
Gopher/Gemini and Web.I hope you get the joke π ***
LOL, Now substitute IRC and Discord with
Gopher/Gemini and Web.I hope you get the joke π ***
LOL, Now substitute IRC and Discord with
Gopher/Gemini and Web.I hope you get the joke π ***
james instead π€£
james instead π€£
$ inspect-db yarns.db | jq -r '.Value.URL' | grep 'aelaraji.com'
https://aelaraji.com/test_feed.txt
https://aelaraji.com/twtxt.txt
$ inspect-db yarns.db | jq -r '.Value.URL' | grep 'aelaraji.com'
https://aelaraji.com/test_feed.txt
https://aelaraji.com/twtxt.txt
kex1fhxntuc0av7q48hlfj970ve297dzzghn82wp5cahr9r92y8rlrqqtwp983
kex1fhxntuc0av7q48hlfj970ve297dzzghn82wp5cahr9r92y8rlrqqtwp983
- Drop
# url= from the spec.- We don't adopt
# uuid = -- Something @anth also mentioned (_see below_)We instead use the
@nick@domain to identify your feed in the first place and use that as the identify when calculating Twt hashes <id> + <timestamp> + <content>. Now in an ideal world I also agree, use WebFinger for this and expect that for the most part you'll be doing a WebFinger lookup of @user@domain to fetch someone's feed in the first place.The only problem with WebFinger is should this be mandated or a recommendation?
- Drop
# url= from the spec.- We don't adopt
# uuid = -- Something @anth also mentioned (_see below_)We instead use the
@nick@domain to identify your feed in the first place and use that as the identify when calculating Twt hashes <id> + <timestamp> + <content>. Now in an ideal world I also agree, use WebFinger for this and expect that for the most part you'll be doing a WebFinger lookup of @user@domain to fetch someone's feed in the first place.The only problem with WebFinger is should this be mandated or a recommendation?
> 17:42
I actually agree with in both counts and it got me thinking...
> 17:42
I actually agree with in both counts and it got me thinking...
Not sure what to say here. π€
Not sure what to say here. π€
Thank you to whomever said this! πββοΈ
Thank you to whomever said this! πββοΈ
See previous. Sorry π
See previous. Sorry π
See previous.
See previous.
Yes, I totally get where you're coming from. However after ~22 results, I _think_ y'all have figured out how to rank them appropriately anyway π€£~
Yes, I totally get where you're coming from. However after ~22 results, I _think_ y'all have figured out how to rank them appropriately anyway π€£~
> your poll should include questions about markdown. personally i think inline bits like style, links, images are yes. block quotes, code blocks, bullet lists are mid. but tables and footnotes are no.
Yes sorry about this, I wasn't able to change much after publishing the poll π
> your poll should include questions about markdown. personally i think inline bits like style, links, images are yes. block quotes, code blocks, bullet lists are mid. but tables and footnotes are no.
Yes sorry about this, I wasn't able to change much after publishing the poll π