Search the Community

Showing results for tags '2741'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Official Buildings
    • GM Hall
    • City Hall
    • Game News
    • Public Test Board
  • Back Streets
    • Town Square
    • Community Assistance
    • Village Recruitment Center
    • Suggestions & Ideas
    • The Creative Commons
    • Wood Scraps
  • Northern Freedom Isles
    • Harmony
    • Melody
    • Cadence
    • Northern Freedom Isles Market
  • Southern Freedom Isles
    • Celebration
    • Deliverance
    • Exodus
    • Independence
    • Pristine
    • Release
    • Xanadu
    • Southern Freedom Isles Market
  • Maintenance Buildings
    • Technical Issues
    • Server Bugs
    • Client Bugs
    • Model and Sound Bugs
    • Other Bugs and Issues
    • Wurmpedia / Wiki Maintenance
  • Wurm Unlimited
    • Unlimited Discussion
    • Unlimited Modding
    • Server Listings & Advertisement
    • Technical Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Chaos


Independence


Deliverance


Exodus


Celebration


Xanadu


Release


Pristine


Epic


Cadence


Defiance


Harmony


Melody


Acc1


Acc2


Acc3

Found 1 result

  1. In one week, all of Wurm's Twitter integrations will stop working unless Wurm pays money for them. This means: No more deed founding/disbanding announcements unless you're online to see it No more rift time estimations No more unique death announcements since these features on fansites like Wurmnode are all powered by a) Wurm's access to the Twitter API (allowing for free posts to Twitter accounts) and b) free fansite access to the Twitter API (allowing for free scraping of tweets, a feature that they seem most bothered about monetising.) In addition, deed Twitter accounts will stop working. Free access to the Twitter API will end seven days from now on February 9th (this only got announced this morning, with one week of notice): It will become much harder to track things like rifts, deeds and uniques seven days from now unless another solution is put in place. This is bad. The new Twitter management has been known to reverse decisions just as quickly as they make them. However, given that they currently aren't even paying their rent properly for office spaces... I think it's safe to say that Twitter is very, very shaky right now, and it's probably not a good thing to have so much Wurm functionality tied in with this third party service. Suggested quick fix It would be possible to pay for Twitter API access, but that feels like a waste of money (especially given how many servers Wurm has = paying for it at least 17 times over), plus fansites would have to pay for the API too to be able to scrape tweets, which is a shame for people like @Drogoswho already put a lot of free time and effort into running them. As it stands, all Wurm servers already publish data to the web elsewhere. This data is tied in with the server graphs of things like player count and creature count. This goes to raw data pages that I (assume?) are hosted by the servers themselves given the subdomain, e.g. here's the one for Independence. Instead of sending tweets, a new "announcements.log" file could be made, where each line is simply a copy of the text that would have been sent in a tweet (with a timestamp too, please! The tweet timestamps are essential for calculating when rifts will happen next.) This announcements file would be easy to download as necessary to scrape the server information we traditionally got from Twitter. The code that sends tweets would just need an addition/replacement to append the string it would have sent to Twitter to the announcements log file instead. Could set a reasonable line limit on the announcements log file of e.g. 100 or 1000 lines so it doesn't get too big. As for deed Twitters, it's not easy to replace private Twitter accounts for now with a free feature. Long-term, if there's community demand for it, the best solution might be a Discord integration (since a lot of people use Discord now, it has a free API, very good bot support, and is much, much more stable than the current Twitter situation.)