tal

joined 2 years ago
[–] tal@lemmy.today 6 points 1 week ago* (last edited 1 week ago)

uncensored

https://lemmyverse.net/communities?nsfw=true

reposts

If you're browsing "All" instead of "Subscribed"


I recommend building a subscription list of interest


there's a bot, @bot@lemmit.online that mirrors posts to Reddit to communities on lemmit.online. You can either block the bot or block the instance if you don't want that.

[–] tal@lemmy.today 8 points 1 week ago (1 children)

https://en.wikipedia.org/wiki/Romani_people_in_Slovenia

According to the 2002 census, there were 3,246 Romani individuals living in Slovenia.[1] They constitute 0.5 percent of the total population.[2] The Slovenia Roma speak Balkan Romani and Italian.[3] The Roma have been living in Slovenia since the 15th century.[4]

So did they just now become a threat, or was it for the past six centuries too?

[–] tal@lemmy.today 3 points 2 weeks ago* (last edited 2 weeks ago)

CloudFlare is going to have someone talking directly to a CloudFlare IP address, so it's going to be visible.

AWS or GCP provide servers which might be behind something like CloudFlare. If they were deployed like that, I don't believe that there'd be a straightforward way to determine that that's where the server is hosted.

If it's directly-accessible, and not using a CDN like CloudFlare, then it'd work the same way as if you were checking whether they're using CloudFlare, just do a whois query on its IP address. I don't know a real instance offhand directly-accessible on AWS, but to grab a random AWS hostname and Google Cloud Platform hostname:

$ host ec2-23-20-1-1.compute-1.amazonaws.com.
ec2-23-20-1-1.compute-1.amazonaws.com has address 23.20.1.1
$ whois 23.20.0.0|grep ^NetName
NetName:        AMAZON-EC2-USEAST-10
NetName:        AMAZON-IAD
$ host 3.192.170.108.bc.googleusercontent.com
3.192.170.108.bc.googleusercontent.com has address 108.170.192.3
$ whois 108.170.192.3|grep ^NetName
NetName:        GOOGLE
$

For a real host, we can just ad-hoc scrape lemmy.world's instance list:

$ curl -s https://lemmy.world/instances |tr '}' '\n'|grep -o 'domain":".[^"]*'|sed 's/domain":"//' >threadiverse-hosts.txt
$ xargs <threadiverse-hosts.txt -n1 host -- >threadiverse-hosts-resolved.txt
$ grep "has address" threadiverse-hosts-resolved.txt |cut -d" " -f4|xargs -n1 host -- >threadiverse-hosts-reverse-resolved.txt
$ grep amazonaws.com threadiverse-hosts-reverse-resolved.txt|head -n1
75.184.193.54.in-addr.arpa domain name pointer ec2-54-193-184-75.us-west-1.compute.amazonaws.com.
$ grep 54.193.184.75 threadiverse-hosts-resolved.txt|head -n1
c63b-77-100-144-83.ngrok-free.app has address 54.193.184.75
$

So there's the hostname of a real instance using AWS directly, c63b-77-100-144-83.ngrok-free.app.

$ host c63b-77-100-144-83.ngrok-free.app|head -n1
c63b-77-100-144-83.ngrok-free.app has address 184.72.44.51
$ whois 184.72.44.51|grep ^NetName
NetName:        AMAZON-EC2-7
NetName:        AMAZON-SFO
$
[–] tal@lemmy.today 2 points 2 weeks ago

You can monitor instance downtime at:

https://lestat.org/

[–] tal@lemmy.today 7 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

To repeat my comment here:

https://lemmy.today/post/41970730/20432766

I mean, it's easy to check whether a given instance is using CloudFlare.

$ host lemmy.world|head -n1
lemmy.world has address 104.26.9.209
$ whois 104.26.9.209|grep ^NetName
NetName:        CLOUDFLARENET
$

You can browse anonymously on any instance that permits doing so, so if you just want to browse during an outage, you can do that anywhere.

IMHO, having an account on a second Threadiverse instance isn't necessarily a terrible idea, not just because of CloudFlare outages, but because instances do have outages for various reasons. I have an account on olio.cafe (PieFed, not on CloudFlare) and on lemmy.today (Lemmy, not on CloudFlare) because I wanted to try out PieFed, and I have fallen back to that to post before if lemmy.today has issues.

That being said, I didn't intentionally try to avoid CloudFlare. I mean, they're used by a lot of major sites, and I don't expect them to have a lot of downtime. I mean, every Threadiverse instance has had downtime for some reason or another. I've had Internet outages, as well as electricity outages. Not all that common or usually an extended thing, but they happen.

[–] tal@lemmy.today 13 points 2 weeks ago* (last edited 2 weeks ago)

I mean, it's easy to check whether a given instance is using CloudFlare.

$ host lemmy.world|head -n1
lemmy.world has address 104.26.9.209
$ whois 104.26.9.209|grep ^NetName
NetName:        CLOUDFLARENET
$

You can browse anonymously on any instance that permits doing so, so if you just want to browse during an outage, you can do that anywhere.

IMHO, having an account on a second Threadiverse instance isn't necessarily a terrible idea, not just because of CloudFlare outages, but because instances do have outages for various reasons. I have an account on olio.cafe (PieFed, not on CloudFlare) and on lemmy.today (Lemmy, not on CloudFlare) because I wanted to try out PieFed, and I have fallen back to that to post before if lemmy.today has issues.

That being said, I didn't intentionally try to avoid CloudFlare. I mean, they're used by a lot of major sites, and I don't expect them to have a lot of downtime. I mean, every Threadiverse instance has had downtime for some reason or another. I've had Internet outages, as well as electricity outages. Not all that common or usually an extended thing, but they happen.

[–] tal@lemmy.today 4 points 2 weeks ago

Took down Framework's website, which I was using.

[–] tal@lemmy.today 15 points 2 weeks ago* (last edited 2 weeks ago)

So, there are a couple of reasons to use CloudFlare, but I suspect that the reason that a lot of people are doing so is to deal with DDoSes, which are hard to deal with otherwise.

Like, my home instance, lemmy.today, doesn't use CloudFlare, so it isn't affected by a CloudFlare outage. But...it was also knocked offline for a few days about a month back by a DDoS.

A lot of major sites do depend on CloudFlare, so they probably aren't going to have a horrendous amount of downtime


like, any issue that comes up is probably gonna have a lot of engineers banging on it pretty quickly.

[–] tal@lemmy.today 2 points 2 weeks ago

It's back up now.

[–] tal@lemmy.today 6 points 2 weeks ago

!actuallyinfuriating

Ah, yeah, thanks, though the community name is incorrect (needs an underscore) and is missing the instance name.

[–] tal@lemmy.today 30 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

Just keep in mind that the long run trend for storage prices is pretty strongly downwards; that's a log-scale graph.

[–] tal@lemmy.today 13 points 2 weeks ago* (last edited 2 weeks ago) (6 children)

Are we okay with the “mildly infuriating” community becoming a “news that really upset me” community?

Note that Reddit's /r/MildlyInfuriating spawned /r/ActuallyInfuriating for stuff that is more severe.

Searching on lemmyverse.net shows that we do have an /r/ActuallyInfuriating analog at !actually_infuriating@lemmy.world.

Maybe the community mods might consider putting it in the sidebar? @Aer@lemmy.world, @Striker@lemmy.world, @Tenthrow@lemmy.world?

view more: ‹ prev next ›