Recent comments

jack_walking wrote

By a different point of view, I like the scarcity of people around. Makes it easier to engage in a direct conversation rather than the chaos of reddit.

I would even go as far as to propose a (monthly?) cap for new users, or joining by invitation only. That may keep the quality of posts high while decreasing scam / advertisement / etc.

In my opinion, that does not contrast with the freedom of speech that constiuetes the foundations of Ramble.

2

jack_walking OP wrote

Don't worry man, I got it.

I'm comfortable in using TOR network and crypto currencies, what I was uncertain about is that I never made this kind of purchase and never had experience with shipment of substances.

I'll do some research and determine whether I really need Adderall and if the purchase is worth the risk.

2

Rambler OP wrote

Reply to comment by boobs in Help accessing YGG domains. by Rambler

Got it.

It works via Lynx, not sure what the deal is with the other browsers I've tried it with, but it is "working". The thing I wanted to do most was just confirm it was resolving for others, and it appears to be doing that just fine. The issues I'm experiencing seem isolated to me and only me and since I access the site mostly via I2P or Loki recently, I don't mind using the longform IPV6 if need be to access it over Yggdrasil.

I've got a ton of other stuff I'm working on and it seems that the .ygg is working, so that's good. I can access it via curl, dig, load it in lynx all fine now. Why I can't via a normal web browser even after clearing everything out, private browsing windows, etc is beyond me. Sometimes it works, sometimes it doesn't in the browser. But if it's working normally and reliably for everyone else I'm not going to fuss with it anymore, haha.

1

z3d wrote (edited )

If you're not running a repo or .deb installed version of I2P, or you're running I2P+, backing up your settings is as simple as copying the ~/.i2p/ directory to the new $HOME location, and if necessary, chowning it to ensure it's owned by the user account running I2P/I2P+ on the new server.

You can either move ~/.i2p/ to your home directory before you run I2P/I2P+ for the first time, or, if you've already run I2P/I2P+, delete the existing ~/.i2p/ directory and copy your backup there. All existing configs should be restored without issue.

2

Rambler OP wrote (edited )

Reply to comment by cypherpunks in Help accessing YGG domains. by Rambler

Works via terminal, nowhere else. It loaded a few times via Firefox for me but that's it. Clearing everything, private window this, new browser that... Nothing.

Via terminal though, it's fine. I'm done messing with it. If it works for you and others, that's the important thing. Otherwise, the IPV6 works fine for me. I just like accessing the site through various networks depending on what I'm doing. Seems lately it's been a pretty consistent mix of I2P, Loki and clearnet. But as soon as I type in http://[ firefox completes the IPv6 for me so it's not that big of a deal on my end.


$ curl -Is ramble.ygg | head -1
HTTP/1.1 200 OK


$ ping ramble.ygg
PING ramble.ygg(200:718d:c499:3fce:c5e:65c6:73d6:f46d
(200:718d:c499:3fce:c5e:65c6:73d6:f46d)) 56 data bytes
64 bytes from 200:718d:c499:3fce:c5e:65c6:73d6:f46d (200:718d:c499:3fce:c5e:65c6:73d6:f46d): icmp_seq=1 ttl=64 time=246 ms
64 bytes from 200:718d:c499:3fce:c5e:65c6:73d6:f46d (200:718d:c499:3fce:c5e:65c6:73d6:f46d): icmp_seq=2 ttl=64 time=325 ms
64 bytes from 200:718d:c499:3fce:c5e:65c6:73d6:f46d (200:718d:c499:3fce:c5e:65c6:73d6:f46d): icmp_seq=3 ttl=64 time=250 ms

```
1

Rambler OP wrote

I love other people's dogs and will go out of my way to interact with them. Dogs seem to like me, too.

But cats are awesome. They sleep 16 hours a day and shit in a box. They like to chill and are incredibly easy to care for. Really, can't ask for a better indoor animal than a cat in my opinion...

So I'm going to have to say cats. But I love dogs too.

1

Rambler OP wrote

Reply to comment by cypherpunks in Help accessing YGG domains. by Rambler

Crazy thing is when I use dig, it responds. In the browser, nothing. No .ygg will load for me. Maybe I'm misinterpreting this.

$ dig ramble.ygg AAAA @301:2522::53 

; <<>> DiG 9.10.3-P4-Ubuntu <<>> ramble.ygg AAAA @301:2522::53
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60331
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; CLIENT-SUBNET: 200:ac7f:495d:c674:5851:6714:128f:0/112/0
;; QUESTION SECTION:
;ramble.ygg.			IN	AAAA

;; ANSWER SECTION:
ramble.ygg.		3600	IN	AAAA	200:718d:c499:3fce:c5e:65c6:73d6:f46d

;; AUTHORITY SECTION:
ygg.			300	IN	NS	ns2.ygg.
ygg.			300	IN	NS	ns1.ygg.

;; ADDITIONAL SECTION:
ns1.ygg.		300	IN	AAAA	301:2923::53
ns2.ygg.		300	IN	AAAA	301:2522::53

;; Query time: 687 msec
;; SERVER: 301:2522::53#53(301:2522::53)
;; WHEN: Fri Dec 18 17:47:51 EST 2020
;; MSG SIZE rcvd: 181
1

abralelie wrote

You're probably running Ubuntu or Debian, right?

I'd shutdown the node and simply tar /var/lib/i2p/, install I2P on the new device, make sure it's off, rm -rf /var/lib/i2p, untar your backup archive and chown -R i2psvc /var/lib/i2p (change the owner to the i2p service). Then you can start i2p up again.

Never done that before, but I think that's they only state i2p stores.

2

Rambler OP wrote

Reply to comment by cypherpunks in Help accessing YGG domains. by Rambler

Yeah, that's what I thought.

resolv.conf is overwritten, I would assume by my network manager that I use to connect to my wireless network. When adding in 'additional DNS servers' under IPV6 settings, I choose one provided by wyrd (ex: 300:4523::53 ) and save it.

Disconnect / reconnect, no go.

I'll just add 300:4523::53 anywhere I can set anything DNS related until it works I guess, haha.

1