btc is bitcoin yes. coinbase is one of the bigger exchanges so that’s fine
if you live in the USA crypto makes your taxes more complicated; the IRS wants to know when you buy and sell it and how much you got it for just like traditional investments.
In the meantime, if you want both reddit like and twitter like functionality, checkout kbin. Kbin federates with both lemmy and mastodon and has both magazines (their version of communities) and microblogging (like twitter/mastodon)
thats what their site says, at least when ran through google translate
first I’ve heard of it, but I’m skeptical of their claim to deliver security fixes faster than firefox.
anything in particular I can clear up?
blow by blow: first the request for an A record ( ipv4 address) for lemmy.ml is sent to a.root-servers.net ( one of several core name servers to the entire internet)
they don’t reply with an A record, but instead a few NS ( nameserver) records for .ml and then in the additional section also give use the ipv4 and ipv6 addresses to those .ml name servers
so we go ask those .ml servers again for an A record for lemmy.ml, they still don’t give us that A record, but instead say these ns.freenom.com name servers are responsible.
we ask one of them and they finally give us that A record: lemmy.ml is 54.36.178.108 so your computer knows to connect to 54.36.178.108 when you ask for lemmy.ml.
its the first and last two columns that are important. the second column is just how many seconds that information should be considered good for before asking again to make sure it hasn’t changed
dns lookups ( what turns lemmy.ml into an address your computer can connect to) actually go right to left. first the root servers are asked, then they say go ask the ml servers and g, then they ask the lemmy.ml servers.
in practice, usually unless otherwise configured your isp’s name servers are asked first; if someone else has recently asked for the same site it remembers what the answer was and just gives the same to you.
~ $ dig lemmy.ml @a.root-servers.net
; <<>> DiG 9.18.17 <<>> lemmy.ml @a.root-servers.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 194
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 8
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;lemmy.ml. IN A
;; AUTHORITY SECTION:
ml. 172800 IN NS a.nic.ml.
ml. 172800 IN NS b.nic.ml.
ml. 172800 IN NS d.nic.ml.
ml. 172800 IN NS c.nic.ml.
;; ADDITIONAL SECTION:
a.nic.ml. 172800 IN A 196.10.220.136
b.nic.ml. 172800 IN A 165.90.218.166
b.nic.ml. 172800 IN AAAA 2c0f:f900:2:3::2
d.nic.ml. 172800 IN A 196.216.168.37
d.nic.ml. 172800 IN AAAA 2001:43f8:120::37
c.nic.ml. 172800 IN A 204.61.216.144
c.nic.ml. 172800 IN AAAA 2001:500:14:6144:ad::1
dig lemmy.ml @a.nic.ml
; <<>> DiG 9.18.17 <<>> lemmy.ml @a.nic.ml
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9343
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 00164cf2465aee8df39824f664cda390738de0ec34953975 (good)
;; QUESTION SECTION:
;lemmy.ml. IN A
;; AUTHORITY SECTION:
lemmy.ml. 7200 IN NS ns04.freenom.com.
lemmy.ml. 7200 IN NS ns02.freenom.com.
lemmy.ml. 7200 IN NS ns03.freenom.com.
lemmy.ml. 7200 IN NS ns01.freenom.com.
dig lemmy.ml @ns04.freenom.com
; <<>> DiG 9.18.17 <<>> lemmy.ml @ns04.freenom.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49838
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;lemmy.ml. IN A
;; ANSWER SECTION:
lemmy.ml. 3600 IN A 54.36.178.108
;; AUTHORITY SECTION:
lemmy.ml. 300 IN NS ns01.freenom.com.
lemmy.ml. 300 IN NS ns02.freenom.com.
lemmy.ml. 300 IN NS ns03.freenom.com.
lemmy.ml. 300 IN NS ns04.freenom.com.
;; ADDITIONAL SECTION:
ns01.freenom.com. 7200 IN A 54.171.131.39
ns02.freenom.com. 7200 IN A 52.19.156.76
ns03.freenom.com. 7200 IN A 104.155.27.112
ns04.freenom.com. 7200 IN A 104.155.29.241
mind replying to the OP since most of us are on instances hes (likely accidentally) blocked?
By setting an allow list hes blocked every other instance not in his list
https://join-lemmy.org/docs/administration/federation_getting_started.html
Allowlist: Explicitly list instances to connect to. BlockList: Explicitly list instances to not connect to. Federation is open to all other instances. Open: Federate with all potential instances.
Federation is enabled by default. You can add allowed and blocked instances, by adding a comma-delimited list in your instance admin panel. IE to only federate with these instances, add: enterprise.lemmy.ml,lemmy.ml to the allowed instances section.
What would you do with that much storage?
It can be easy to be nose-blind to your own smell, trust me its easy to stink enough to be offensive to others but not notice yourself.
They’re doing you a favor by letting you know. Just take the extra moment and put some on in the morning. Just don’t overdo it and douse yourself in body spray; too much body spray is nasty too.
0.18.3 is bringing in more sanitization, probably got missed.
I poked them and they’re working on a fix
Update: fix is in and should be in the next rc. It does work ( built my personal backend from source)
if no one on your home instance was subscribed to the community, it wont get posts or comments. the first time someone on an instance searches the community it seems to just get a few of the old posts but it doesnt get their comments; if you or someone else on your instance subscribes then the instance will get new posts and new comments
it runs fine if you don’t cross-compile and build it on the pi itself ( or emulate an arm system using qemu or similar)
its the internet, they are. Putting it behind cloudflare and locking down the firewall to only allow their ips has filtered out pretty much everything. its free and pretty straight forward if you own your own domain.
check your nginx access logs, I’m sure they’re full of people poking it.
134.122.30.157 - - [22/Jul/2023:07:45:28 -0500] "\x00\x00\x00\xB2\x9A\xD6\x8E\xCF.\x22\x83\xA9\xBF2\xBA|ro\xAE_\x95\xEC\x80\xE4\xE9n\x82q\x9E\xC6\xA9\x8F\xF5" 400 157 "-" "-"
and all kinds of other obvious incorrect stuff when a normal request looks like
2001:19f0:5c01:dd3:5400:2ff:feba:75b - - [27/Jul/2023:07:21:25 -0500] "GET /comment/165203 HTTP/2.0" 200 953 "-" "Lemmy/unknown version; +https://lemmy.xcoolgroup.com"
GET/POST/WHATEVER /url …
They fixed it ( the 2fa bypass; now resetting password won’t log you in) looks like it’l be in 0.18.3 ( not out yet, but its up to release candidate 3, so soon)
It has the power to run a one user instance, I’m sure it would run into issues trying to squeeze a normal amount of people onto it, but a handful sure.
I run everything off an external hard drive
lemmy can run on a decent variety of hardware, just has to be some thing left on 24/7 and exposed to the internet (be careful, the internet is a hostile place… mine was getting scanned and poked constantly until I put it behind cloudflare and then locked the firewall down to just let in cloudflare), and of course more users take more powerful hardware.
For my personal just me instance though, I’m just running it on a Raspberry Pi 4 I run some other stuff on. Uses less than a gig of memory.
some communities themselves are tagged nsfw. That might cause what you’re seeing.
Just make sure any nsfw stuff you do post you manually check the box as well.
no man, that “shorthand” is exactly how you’re supposed to search for new communities. Its exactly how I’ve added every community to my personal instance
you should see kbin , I had a poke at that the other day and it needs php, postgres, nginx, mercure, rabbitmq, supervisord and also nodejs.
I got close, but I couldnt quite get things working the other day. Had it to the point I had an ugly unthemed version up some of the time.
I recommend avoiding political communities in general. too many extremists on either side of the political spectrum.