home.social

#epicyon — Public Fediverse posts

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

fetched live
  1. Changed the way that empty user agents are dealt with in #Epicyon. They were blocked already, but now they're blocked at an earlier stage and with more logging so that you can see the IP addresses. On my instance so far they seem to be primarily coming from Cloudflare (what a surprise!).

  2. Changed the way that empty user agents are dealt with in #Epicyon. They were blocked already, but now they're blocked at an earlier stage and with more logging so that you can see the IP addresses. On my instance so far they seem to be primarily coming from Cloudflare (what a surprise!).

  3. Changed the way that empty user agents are dealt with in #Epicyon. They were blocked already, but now they're blocked at an earlier stage and with more logging so that you can see the IP addresses. On my instance so far they seem to be primarily coming from Cloudflare (what a surprise!).

  4. Updated the Prosody modules on #LibreServer and also added something in #Epicyon to comment out newswire feeds which no longer resolve. If a server comes back later then you can always uncomment the feed, and this avoids trying to download feeds from websites which no longer exist.

  5. Updated the Prosody modules on #LibreServer and also added something in #Epicyon to comment out newswire feeds which no longer resolve. If a server comes back later then you can always uncomment the feed, and this avoids trying to download feeds from websites which no longer exist.

  6. Updated the Prosody modules on #LibreServer and also added something in #Epicyon to comment out newswire feeds which no longer resolve. If a server comes back later then you can always uncomment the feed, and this avoids trying to download feeds from websites which no longer exist.

  7. @tofeo apologies on my delayed response. I tried to look for #epicyon public instance examples but wasn't able to find any.

    But then upon taking a deeper look it looks like this is by design as Epicyon discourages public instances, please see: codeberg.org/bashrc/epicyon/sr

  8. @tofeo apologies on my delayed response. I tried to look for #epicyon public instance examples but wasn't able to find any.

    But then upon taking a deeper look it looks like this is by design as Epicyon discourages public instances, please see: codeberg.org/bashrc/epicyon/sr

  9. @tofeo apologies on my delayed response. I tried to look for #epicyon public instance examples but wasn't able to find any.

    But then upon taking a deeper look it looks like this is by design as Epicyon discourages public instances, please see: codeberg.org/bashrc/epicyon/sr

  10. @tofeo apologies on my delayed response. I tried to look for #epicyon public instance examples but wasn't able to find any.

    But then upon taking a deeper look it looks like this is by design as Epicyon discourages public instances, please see: codeberg.org/bashrc/epicyon/sr

  11. Epicyon ("more than a dog")
    is a large, extinct, canid genus of the subfamily
    Borophaginae ("bone-crushing dogs"),
    native to North America.

    Epicyon existed for about 7 million years
    from the early Clarendonian age of the Late Miocene to the late Hemphillian age of the Early Pliocene.

    E. haydeni is the largest known canid of all time,
    with the type species reaching
    2.4 m (7.9 ft) in length,
    90 cm (35 in) in shoulder height
    and approximately 100–125 kg (220–276 lb) in body mass.

    #Epicyon #Canid #Borophaginae
    en.wikipedia.org/wiki/Epicyon

  12. Epicyon ("more than a dog")
    is a large, extinct, canid genus of the subfamily
    Borophaginae ("bone-crushing dogs"),
    native to North America.

    Epicyon existed for about 7 million years
    from the early Clarendonian age of the Late Miocene to the late Hemphillian age of the Early Pliocene.

    E. haydeni is the largest known canid of all time,
    with the type species reaching
    2.4 m (7.9 ft) in length,
    90 cm (35 in) in shoulder height
    and approximately 100–125 kg (220–276 lb) in body mass.

    #Epicyon #Canid #Borophaginae
    en.wikipedia.org/wiki/Epicyon

  13. Epicyon ("more than a dog")
    is a large, extinct, canid genus of the subfamily
    Borophaginae ("bone-crushing dogs"),
    native to North America.

    Epicyon existed for about 7 million years
    from the early Clarendonian age of the Late Miocene to the late Hemphillian age of the Early Pliocene.

    E. haydeni is the largest known canid of all time,
    with the type species reaching
    2.4 m (7.9 ft) in length,
    90 cm (35 in) in shoulder height
    and approximately 100–125 kg (220–276 lb) in body mass.

    #Epicyon #Canid #Borophaginae
    en.wikipedia.org/wiki/Epicyon

  14. Epicyon ("more than a dog")
    is a large, extinct, canid genus of the subfamily
    Borophaginae ("bone-crushing dogs"),
    native to North America.

    Epicyon existed for about 7 million years
    from the early Clarendonian age of the Late Miocene to the late Hemphillian age of the Early Pliocene.

    E. haydeni is the largest known canid of all time,
    with the type species reaching
    2.4 m (7.9 ft) in length,
    90 cm (35 in) in shoulder height
    and approximately 100–125 kg (220–276 lb) in body mass.

    #Epicyon #Canid #Borophaginae
    en.wikipedia.org/wiki/Epicyon

  15. Epicyon ("more than a dog")
    is a large, extinct, canid genus of the subfamily
    Borophaginae ("bone-crushing dogs"),
    native to North America.

    Epicyon existed for about 7 million years
    from the early Clarendonian age of the Late Miocene to the late Hemphillian age of the Early Pliocene.

    E. haydeni is the largest known canid of all time,
    with the type species reaching
    2.4 m (7.9 ft) in length,
    90 cm (35 in) in shoulder height
    and approximately 100–125 kg (220–276 lb) in body mass.

    #Epicyon #Canid #Borophaginae
    en.wikipedia.org/wiki/Epicyon

  16. CW: AI hype

    If scraping the entire internet to make a chatbot is "fair use" then #Nitter is certainly fair use. It might be premature to remove the domain replacing functionality from #Epicyon, but it is looking like this sort of alternative front end doesn't have a future.

    I set my own instance to remove anything coming from Twitter quite a while ago. Dragging in posts from Twitter was a mainstay of the early fediverse, because there was not much native content, but now I think a better strategy is just to cut any ties to #BigTech sites.

  17. CW: AI hype

    If scraping the entire internet to make a chatbot is "fair use" then #Nitter is certainly fair use. It might be premature to remove the domain replacing functionality from #Epicyon, but it is looking like this sort of alternative front end doesn't have a future.

    I set my own instance to remove anything coming from Twitter quite a while ago. Dragging in posts from Twitter was a mainstay of the early fediverse, because there was not much native content, but now I think a better strategy is just to cut any ties to #BigTech sites.

  18. CW: AI hype

    If scraping the entire internet to make a chatbot is "fair use" then #Nitter is certainly fair use. It might be premature to remove the domain replacing functionality from #Epicyon, but it is looking like this sort of alternative front end doesn't have a future.

    I set my own instance to remove anything coming from Twitter quite a while ago. Dragging in posts from Twitter was a mainstay of the early fediverse, because there was not much native content, but now I think a better strategy is just to cut any ties to #BigTech sites.

  19. Added better support for CJK characters in #Epicyon. So usernames can be in Chinese or Japanese.

  20. Added better support for CJK characters in #Epicyon. So usernames can be in Chinese or Japanese.

  21. Added better support for CJK characters in #Epicyon. So usernames can be in Chinese or Japanese.

  22. Testing international usernames in #Epicyon, and indeed it appears that http signature checks fail with non-ASCII characters.

  23. Testing international usernames in #Epicyon, and indeed it appears that http signature checks fail with non-ASCII characters.

  24. Testing international usernames in #Epicyon, and indeed it appears that http signature checks fail with non-ASCII characters.

  25. I must say, the word substitution feature that I have in #Epicyon sometimes makes it extremely clear where people stand on a particular issue.

    #KindaVagueButWhatever

  26. I must say, the word substitution feature that I have in #Epicyon sometimes makes it extremely clear where people stand on a particular issue.

    #KindaVagueButWhatever

  27. I must say, the word substitution feature that I have in #Epicyon sometimes makes it extremely clear where people stand on a particular issue.

    #KindaVagueButWhatever

  28. Added an option in #Epicyon to convert dashes to em dashes. AI scrapers may use the presence of em dashes to infer that the text was machine extruded and thus not include it within training sets.

    Of course this only works while em dashes are niche. If they become mainstream then this will no longer have the same effect.

  29. Added an option in #Epicyon to convert dashes to em dashes. AI scrapers may use the presence of em dashes to infer that the text was machine extruded and thus not include it within training sets.

    Of course this only works while em dashes are niche. If they become mainstream then this will no longer have the same effect.

  30. Added an option in #Epicyon to convert dashes to em dashes. AI scrapers may use the presence of em dashes to infer that the text was machine extruded and thus not include it within training sets.

    Of course this only works while em dashes are niche. If they become mainstream then this will no longer have the same effect.

  31. Added an option in #Epicyon to dither attached images, and changed the dithering type to halftone. This may be a mitigation against generative #AI scrapers, because the dot patterns will confuse keypoint detection and convolution during training of deep neural nets. Although theoretically halftone dithering could be reversed into an undithered image as a data cleaning step, it would not be a very good image and would suffer from a lot of upscaling "hallucinations".

  32. Added an option in #Epicyon to dither attached images, and changed the dithering type to halftone. This may be a mitigation against generative #AI scrapers, because the dot patterns will confuse keypoint detection and convolution during training of deep neural nets. Although theoretically halftone dithering could be reversed into an undithered image as a data cleaning step, it would not be a very good image and would suffer from a lot of upscaling "hallucinations".

  33. Added an option in #Epicyon to dither attached images, and changed the dithering type to halftone. This may be a mitigation against generative #AI scrapers, because the dot patterns will confuse keypoint detection and convolution during training of deep neural nets. Although theoretically halftone dithering could be reversed into an undithered image as a data cleaning step, it would not be a very good image and would suffer from a lot of upscaling "hallucinations".

  34. Improved support for featured #hashtags in #Epicyon. So now, hashtags don't need to be in the bio anymore.

    #HashtagsNotInBio

  35. Improved support for featured #hashtags in #Epicyon. So now, hashtags don't need to be in the bio anymore.

    #HashtagsNotInBio

  36. Improved support for featured #hashtags in #Epicyon. So now, hashtags don't need to be in the bio anymore.

    #HashtagsNotInBio

  37. Added a profile option in #Epicyon to allow an account to be added to lists, as per FEP-7aa9. For now, being added to lists is only permitted for mutuals, and I think this is the safest option considering the (waving hands) contemporary milieu of online horrors.

    Adding people to lists in general, even with authorizations, sets off my "this is likely to lead to bad things" alarm. So in Epicyon it's opt-in.

    I have also updated the Occitan translations.

  38. Added a profile option in #Epicyon to allow an account to be added to lists, as per FEP-7aa9. For now, being added to lists is only permitted for mutuals, and I think this is the safest option considering the (waving hands) contemporary milieu of online horrors.

    Adding people to lists in general, even with authorizations, sets off my "this is likely to lead to bad things" alarm. So in Epicyon it's opt-in.

    I have also updated the Occitan translations.

  39. Added a profile option in #Epicyon to allow an account to be added to lists, as per FEP-7aa9. For now, being added to lists is only permitted for mutuals, and I think this is the safest option considering the (waving hands) contemporary milieu of online horrors.

    Adding people to lists in general, even with authorizations, sets off my "this is likely to lead to bad things" alarm. So in Epicyon it's opt-in.

    I have also updated the Occitan translations.

  40. Adding some support for lists in #Epicyon. However, my enthusiasm for lists is not high. I am often reminded of the comedy sketches from decades ago in which the stereotypical nazi is "adding you to a list".

  41. Adding some support for lists in #Epicyon. However, my enthusiasm for lists is not high. I am often reminded of the comedy sketches from decades ago in which the stereotypical nazi is "adding you to a list".

  42. Adding some support for lists in #Epicyon. However, my enthusiasm for lists is not high. I am often reminded of the comedy sketches from decades ago in which the stereotypical nazi is "adding you to a list".

  43. Added QR codes for Enigma public key and Ricochet ID, to make transferring random strings between devices easier. #Epicyon

  44. Added QR codes for Enigma public key and Ricochet ID, to make transferring random strings between devices easier. #Epicyon

  45. Added QR codes for Enigma public key and Ricochet ID, to make transferring random strings between devices easier. #Epicyon

  46. The new #Epicyon website is more or less done. I even slapped an established year on it, because I was thinking of the style of old-fashioned typewriter letter headers.

    libreserver.org/epicyon

  47. The new #Epicyon website is more or less done. I even slapped an established year on it, because I was thinking of the style of old-fashioned typewriter letter headers.

    libreserver.org/epicyon

  48. The new #Epicyon website is more or less done. I even slapped an established year on it, because I was thinking of the style of old-fashioned typewriter letter headers.

    libreserver.org/epicyon

  49. Made an NLnet application to see if I can get any funding for development on #Epicyon. I've done similar in the past, but for LibreServer instead. It's highly doubtful that anything will come of it, since Epicyon is not a very mainstream kind of fediverse instance and isn't intended to vertically scale, like Mastodon.

    The future plan for the project is to maybe focus more on C2S and one or more native clients for that. There is already a demo client, but it's quite primitive. Also trying to make the workflow for keyboard plus speech synthesis interaction as painless as possible.

  50. Made an NLnet application to see if I can get any funding for development on #Epicyon. I've done similar in the past, but for LibreServer instead. It's highly doubtful that anything will come of it, since Epicyon is not a very mainstream kind of fediverse instance and isn't intended to vertically scale, like Mastodon.

    The future plan for the project is to maybe focus more on C2S and one or more native clients for that. There is already a demo client, but it's quite primitive. Also trying to make the workflow for keyboard plus speech synthesis interaction as painless as possible.

  51. Made an NLnet application to see if I can get any funding for development on #Epicyon. I've done similar in the past, but for LibreServer instead. It's highly doubtful that anything will come of it, since Epicyon is not a very mainstream kind of fediverse instance and isn't intended to vertically scale, like Mastodon.

    The future plan for the project is to maybe focus more on C2S and one or more native clients for that. There is already a demo client, but it's quite primitive. Also trying to make the workflow for keyboard plus speech synthesis interaction as painless as possible.