Recent searches
Search options
#en
Telegram MTProxy list
Shorthand addresses, e.g. mtproxy-1.telegram.i2p, can be resolved by i2pd only
```
MTProxy #1:
Address
mtproxy-1.telegram.i2p vxxfipsygx6jpz57pmb3d3mjgsk5ls2idxeo2bffs3yp62muyq7q.b32.i2p
Secret key
d676d59cd211bfe0031e4db3debc6a1b
```
MTProxy #2:
**Address** mtproxy-2.telegram.i2p vp3vans4ra3vpo24orm5seaxvod4x4lwiqajrfazb62hfwb45ddq.b32.i2p **Secret key** 1b3e58008e4a2838505ea99838db21df
Example i2pd tunnels config file
That example shows one-for-all configuration. For more information about used settings please refer to i2pd documentation
```
[TG-MTPROXY-1]
type = client
address = 127.0.0.1
port = 8440
destination = vxxfipsygx6jpz57pmb3d3mjgsk5ls2idxeo2bffs3yp62muyq7q.b32.i2p
signaturetype = 7
inbound.length = 1
outbound.length = 1
inbound.quantity = 5
outbound.quantity = 5
i2cp.leaseSetType = 3
i2cp.leaseSetEncType = 0,4
i2p.streaming.initialAckDelay = 20
keys = transient-tg-mtproxy
[TG-MTPROXY-2]
type = client
address = 127.0.0.1
port = 8441
destination = vp3vans4ra3vpo24orm5seaxvod4x4lwiqajrfazb62hfwb45ddq.b32.i2p
keys = transient-tg-mtproxy
```
Telegram Web
You can use *Telegram Web*, based on "Web K" client and patched for usage in I2P: Telegram Web I2P
All requests to Telegram's servers proxifyed with nginx. All data transfered via nginx is encrypted with MTProto cryptographic protocol, and can't be decrypted by our service.
Configuration and changes to original client can be found here.
Downloads
Ready for use configuration file for i2pd: Download
Place it in *tunnels.d* directory and reload tunnels configuration
Preconfigured for I2P Telegram:
Windows 64-bit: Clearnet, I2P
Windows 32-bit: Clearnet, I2P
Linux 64-bit: Clearnet, I2P
Community
chat: @i2p_telegram
IRC: join #en or #ru on Ilita (web)
J'ai une collègue qui travaille sur Nuage avec l'outil permettant de faire des diapos. Son diapo est corrompu et elle n'arrive pas à le récupérer.
C'est pour une certif et elle doit le rendre pour ce soir. Elle travaillait dessus ce matin et d'un coup, le fichier est devenu corrompu !
Si vous avez déjà rencontré ce problème et réussi à le résoudre, ou si vous savez à qui contacter pour le régler, vous seriez nos sauveurs !
Le repouet sauve des collègues de Physique
@pfefferle I only have one so far. How do you ensure that people find those pages?
> FOSS infrastructure is under attack by AI companies
https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies/
Retrouvez toute notre veille sur l'IA sur https://curation.framamia.org
#Framasoft #infrastructure #libre #foss #en
> Vulgar Display of Power
https://tante.cc/2025/03/28/vulgar-display-of-power/
Retrouvez toute notre veille sur l'IA sur https://curation.framamia.org
#Framasoft #ia_generative #droit_auteur #openai #en
> Google Search really has gotten worse. It's not just you. | Mashable
https://mashable.com/article/google-search-low-quality-research
Retrouvez toute notre veille sur l'IA sur https://curation.framamia.org
#Framasoft #ia-slop #google #en
I’ve been listening to Kiasmos a lot in the past few days. It’s hard to pick a specific track, but here is Looped, to get you started! Enjoy!
March 2025 in review / Récap de mars 2025
I am now 31 years old, and the proud owner of a gravel bike and of more equipment than my fitness levels justify. Life is good.
What I've read / Texte
(Only the ones I liked, as usual.)
In English
Fiction
The Books of Ambha, Tasha Suri, Mughal empire-inspired fantasy with blood magic and, of course, genocide.
1984 − Ju
https://alexsirac.com/march-2025-in-review-recap-de-mars-2025/
Partial Solar Eclipse 2025-03-29 https://photo.m-j-s.net/blog/2025/03/partial-solar-eclipse-2025-03-29/
For all Odesza and Severance fans out there: On Repeat Today, Entering Lumon by Odesza:
Salut Mastodon et la team #prof, #EN, #NSI
Je finis mon année de stage dans l'AC de Versailles et repars à Lille pour l’année pro, comme les 3 autres copains du master MEEF de Lille.
On s’est déjà un peu organisés entre nous pour ne pas trop s’entrechoquer pour les vœux.
Sauf qu’on est 6 entrants en NSI, on cherche les 2 derniers que nous ne connaissons pas pour savoir s’ils veulent ou non voir avec nous (ou avoir nos infos pour faire leurs choix de leur côté).
Bisous à toutes et tous !
#en #en #HostEurope #GoDaddy #Microsoft #MS365
In the list of recommended alternatives, I miss @hostsharing A German cooperative for web-, mail-, etc. hosting. I'm posting this from hostsharings mastodon instance. It's great. Become a member, and use it.
Oh, Google allows me to pick a different search engine? Sweet, that should make it easier to use Kagi on my phone!
… Oh. Of course…
I really enjoy reading comments on my favorite podcast episodes in Patreon. Problem is, I don’t listen to my podcasts in Patreon, I use Pocket Casts.
I can’t wait for the day when more creators move to open, federated platforms to host their podcasts, so we can all participate in the discussion in one place, the Fediverse. Are there any popular tools like that? I only know of WordPress right now, and while it works it’s not necessarily known for podcasting. I think Castopod does this maybe?
@voxpelli @tchambers Since both WordPress and Ghost sites support RSS out of the box, I don’t think you need an indicator. 
Now, should we add the tag to long-form content only, or to any posts published via Ghost or WordPress (like this one)?
If you work with GitHub Actions and have used actions to commit to a branch, you may have run into this little problem I ran into today: automatically generated commits and events triggered by a workflow, do not trigger any workflow.
In practice, that means that if you used a workflow to add a commit to your Pull Request, CI will not be triggered after that commit is pushed. All the events and CI that you would expect to see run on your Pull Request will not be triggered until your next push.
This is done on purpose by GitHub, as per the docs:
When you use the repository’s
GITHUB_TOKENto perform tasks, events triggered by theGITHUB_TOKEN, with the exception ofworkflow_dispatchandrepository_dispatch, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository’sGITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.
A possible work-around in such cases is to use a personal access token instead of the default GITHUB_TOKEN to trigger events that require a token.
In my situation, I am using actions/github-script and its authenticated Octokit client. Specifically, I use createOrUpdateFileContents to add a new file, commit it, and push it to the branch. actions/github-script allows using the github-token input to pass your own custom token, so I used that:
uses: actions/github-script@v7 with: github-token: ${{ secrets.API_TOKEN_GITHUB }} script: |The generated commit now happens in my name, and CI events are triggered as expected by that commit.
> Everything you say to your Echo will be sent to Amazon starting on March 28 - Ars Technica
Retrouvez toute notre veille sur l'IA sur https://curation.framamia.org
#Framasoft #exploitation_données #vie_privée #amazon #en
