💾 Archived View for gemi.dev › gemini-mailing-list › 000401.gmi captured on 2023-11-04 at 12:46:56. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
if you use Mastodon or Pleroma and you want to be able to use those over gemini, i built a thing to allow for that. source code: https://git.sr.ht/~boringcactus/gemifedi demo instance: gemini://gemifedi.boringcactus.com/about the code is bad - partially because tls libraries with good client cert support are rare, and partially because i'm too lazy to do anything the right way - but it *works*. mostly. (if your client of choice hasn't implemented client certs yet, you can run gemifedi locally with the --horribly-insecure flag and it will just trust all requests. don't do that for very long at a time, though.) as an exercise, i think designing gemifedi was really interesting: gemini has constraints i'm not used to working within, and i had to get creative to build what i wanted. for example, while drafting this paragraph in this email, i thought of a better solution to the problem of "well if everything is GET then everything needs to be idempotent" than i previously had. i'm not sure how gemini-ish this sort of service is, but given that it's possible to build with gemini as it already exists, it might be a useful data point in ongoing discussions about building Applications? on top of gemini. -??
It kinda fails to find the master branch. Maybe that's just me being pebkac on cargo. boringcactus <boringcactus at gmail.com> writes: > if you use Mastodon or Pleroma and you want to be able to use those over > gemini, i built a thing to allow for that. > > source code: https://git.sr.ht/~boringcactus/gemifedi > demo instance: gemini://gemifedi.boringcactus.com/about > > the code is bad - partially because tls libraries with good client cert > support are rare, and partially because i'm too lazy to do anything the > right way - but it *works*. mostly. > > (if your client of choice hasn't implemented client certs yet, you can > run gemifedi locally with the --horribly-insecure flag and it will just > trust all requests. don't do that for very long at a time, though.) > > as an exercise, i think designing gemifedi was really interesting: > gemini has constraints i'm not used to working within, and i had to get > creative to build what i wanted. for example, while drafting this > paragraph in this email, i thought of a better solution to the problem > of "well if everything is GET then everything needs to be idempotent" > than i previously had. > > i'm not sure how gemini-ish this sort of service is, but given that it's > possible to build with gemini as it already exists, it might be a useful > data point in ongoing discussions about building Applications? on top of > gemini. > > -??
Looks like the branch is called main: cargo install --git https://git.sr.ht/~boringcactus/gemifedi --branch main On Thu, Oct 8, 2020 at 12:49 PM Sandra Snan <sandra.snan at idiomdrottning.org> wrote: > It kinda fails to find the master branch. Maybe that's just me being > pebkac on cargo. > > boringcactus <boringcactus at gmail.com> writes: > > > if you use Mastodon or Pleroma and you want to be able to use those over > > gemini, i built a thing to allow for that. > > > > source code: https://git.sr.ht/~boringcactus/gemifedi > > demo instance: gemini://gemifedi.boringcactus.com/about > > > > the code is bad - partially because tls libraries with good client cert > > support are rare, and partially because i'm too lazy to do anything the > > right way - but it *works*. mostly. > > > > (if your client of choice hasn't implemented client certs yet, you can > > run gemifedi locally with the --horribly-insecure flag and it will just > > trust all requests. don't do that for very long at a time, though.) > > > > as an exercise, i think designing gemifedi was really interesting: > > gemini has constraints i'm not used to working within, and i had to get > > creative to build what i wanted. for example, while drafting this > > paragraph in this email, i thought of a better solution to the problem > > of "well if everything is GET then everything needs to be idempotent" > > than i previously had. > > > > i'm not sure how gemini-ish this sort of service is, but given that it's > > possible to build with gemini as it already exists, it might be a useful > > data point in ongoing discussions about building Applications? on top of > > gemini. > > > > -?? >
On 2020-10-08 6:19 AM, P?emysl Vyhnal wrote: > Looks like the branch is called main: > > cargo install --git https://git.sr.ht/~boringcactus/gemifedi --branch main oh, i'll go make the docs reflect that. didn't know cargo assumed the default branch was always named master.
This is awesome! Also I didn't know cargo could do this. So this means that if I wanna make mods, all I have to do is make them in a repo? For example I wanna change URLs that lead to stuff that is bihosted on https and gemini to be Gemini URLs. P?emysl Vyhnal <premysl at vyhnal.net> writes: > Looks like the branch is called main: > > cargo install --git https://git.sr.ht/~boringcactus/gemifedi --branch main > > > > On Thu, Oct 8, 2020 at 12:49 PM Sandra Snan <sandra.snan at idiomdrottning.org> > wrote: > >> It kinda fails to find the master branch. Maybe that's just me being >> pebkac on cargo. >> >> boringcactus <boringcactus at gmail.com> writes: >> >> > if you use Mastodon or Pleroma and you want to be able to use those over >> > gemini, i built a thing to allow for that. >> > >> > source code: https://git.sr.ht/~boringcactus/gemifedi >> > demo instance: gemini://gemifedi.boringcactus.com/about >> > >> > the code is bad - partially because tls libraries with good client cert >> > support are rare, and partially because i'm too lazy to do anything the >> > right way - but it *works*. mostly. >> > >> > (if your client of choice hasn't implemented client certs yet, you can >> > run gemifedi locally with the --horribly-insecure flag and it will just >> > trust all requests. don't do that for very long at a time, though.) >> > >> > as an exercise, i think designing gemifedi was really interesting: >> > gemini has constraints i'm not used to working within, and i had to get >> > creative to build what i wanted. for example, while drafting this >> > paragraph in this email, i thought of a better solution to the problem >> > of "well if everything is GET then everything needs to be idempotent" >> > than i previously had. >> > >> > i'm not sure how gemini-ish this sort of service is, but given that it's >> > possible to build with gemini as it already exists, it might be a useful >> > data point in ongoing discussions about building Applications? on top of >> > gemini. >> > >> > -?? >>
---